You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2019/11/12 15:10:03 UTC

[GitHub] [accumulo] jzgithub1 opened a new pull request #1422: Fixes #1225 - Created a single ZooNode that tracks changes for all table configs

jzgithub1 opened a new pull request #1422: Fixes #1225 - Created a single ZooNode that tracks changes for all table configs
URL: https://github.com/apache/accumulo/pull/1422
 
 
   @ivakegg  has reviewed this code and has recommended this pull request.  It is nearly an exact implementation of what @ctubbsii  has specified at the top of the Issue #1125. The solution has been tested in Fluo-uno and Fluo-muchos on EC-2.  It has been tested in the accumulo shell by using the 'config' command to change table properties and see the changes made effective. Other commands like 'createtable' and 'deletetable' and 'clonetable' have been tested to check that the system works as expected.  Accumulo-Testing 'cingest createtables' and 'cingest ingest' both run well.  It passes the  'mvn clean verify -Psunny' build.
   
   The non-existence of the watchers has been verified using the ZooKeeper 'wchp' four letter word command.   These four letter commands need to be whitelisted in your zoo.cfg file by adding this line:  
    4lw.commands.whitelist=*
   You need to stop and start Zookeeper to see the whitelisting commands come into effect. 
   You run the 'wchp' four letter command from the shell like so:
   echo wchp | nc localhost 2181 | grep 'conf/table\.
    
   The only watchers remaining for table configuration are the ones  under /accumulo/{InstanceID}/namespaces.  We no longer see accumulation of table configuration item watchers as tables are created and deleted.  
   
   This pull request should fix some system issues we have seen over the years in large systems. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services