dlmarion opened a new issue, #4839: URL: https://github.com/apache/accumulo/issues/4839
It appears that there are two different mechanisms being used for secondary processes to wait for lock acquisition. The Manager and Monitor use `ServiceLock.lock`, then wait on a `waitForChange` method on a Watcher implementation. The SimpleGarbageCollector calls `tryLock` in an endless loop. The Compactor, ScanServer, and TabletServer also use `tryLock`, but in a loop that has limits, they try some number of times then fail. I'm wondering if the SimpleGarbageCollector should follow the same pattern that the Manager and Monitor are using. Found while looking at #4838 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
