[GitHub] [accumulo] EdColeman commented on issue #1809: ZK Watchers remain after table delete

[GitBox <gi...@apache.org>]

EdColeman commented on issue #1809:
URL: https://github.com/apache/accumulo/issues/1809#issuecomment-870961440


   One of the issues that blocks this as a specific fix is that currently, watchers are created with the expectation that the node might appear - and then code will receive notification on node creation.  If the property never set, the node never comes into existence and the watcher that was set remains even when the table is deleted.  To clear the watcher, it would be necessary to create the "missing" nodes and then delete them to trigger the watcher, which hopefully would not them be reset - while this might be a solution, the rework of the properties in 2.1 will make this unnecessary. 
   
   I explored a stand-alone utility that can gather the watchers using a zk four-letter work command (either wchp or wchc work) and then create / delete the nodes with watchers when a corresponding table id does not exist.  The four-letter commands can be disruptive and there was no interest in the utility.


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org