DomGarguilo commented on PR #5949: URL: https://github.com/apache/accumulo/pull/5949#issuecomment-3706046867
#5949 mentioned that we should look into using a read lock here instead of a write lock. I looked into it and here is what I came up with: If I'm understanding things correctly, a read lock will allow concurrent setTabletAvailability() calls. I think this means if two ops run at the same time, there is no guarantee which order they will run in so if they act on overlapping tablets, the outcome will just be whichever op had its conditional mutations run last for each tablet (and the overlap could end up mixed between the two ops). So TLDR: we should keep a write lock if we need these calls to run serially, otherwise a read lock should be fine. -- 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]
