Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle TableOps exists() issues #768

milleruntime opened this issue Nov 14, 2018 · 1 comment


Copy link

commented Nov 14, 2018

This method has concurrency issues, mainly due to cacheing and the distributed environment of Accumulo. For example, one process could create a table and this method could return false for another process because it's zookeeper cache doesn't have the table ID yet. Another example... one process calls exists, gets true then performs an action on that table but the table is deleted before the process can perform the action on that table. We seem to have to explain this to users quite often. At the very least, we should document this in javadoc.


This comment has been minimized.

Copy link
Contributor Author

commented Feb 12, 2019

It appears that this could be a race condition with the changes made in 1.9. Specifically here.

milleruntime added a commit to milleruntime/accumulo that referenced this issue Feb 19, 2019

keith-turner added a commit to keith-turner/accumulo that referenced this issue Feb 20, 2019

@ctubbsii ctubbsii added this to Done in 2.0.0 Jun 14, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.