EdColeman commented on pull request #1812: URL: https://github.com/apache/accumulo/pull/1812#issuecomment-735433224
Looking a 1.10 - the issue seems to be exists calls that set watchers for nodes that are not created and after table deletion, will never exist - so these watchers remain set until service restart. On createtable: In zookeeper there are 20 watchers. The following [instance]/tables/[table_id]/conf: nodes are created: ``` table.constraint.1 table.iterator.majc.vers table.iterator.majc.vers.opt.maxVersions table.iterator.minc.vers table.iterator.minc.vers.opt.maxVersions table.iterator.scan.vers table.iterator.scan.vers.opt.maxVersions ``` From the master debug log, these node have watchers set on exist calls without the node being present: ``` table.balancer table.classpath.context table.volume.chooser ``` From the tserver debug log: ``` table.classpath.context table.compaction.major.everything.idle table.compaction.minor.logs.threshold table.groups.enabled table.majc.compaction.strategy table.replication table.security.scan.visibility.default table.split.endrow.size.max table.split.threshold tserver.dir.memdump ``` After table delete, these watchers remain: ``` table.balancer table.classpath.context table.compaction.major.everything.idle table.compaction.minor.logs.threshold table.groups.enabled table.majc.compaction.strategy table.replication table.security.scan.visibility.default table.split.endrow.size.max table.split.threshold table.volume.chooser tserver.dir.memdump tserver.memory.maps.native.enabled ``` ---------------------------------------------------------------- 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: [email protected]
