You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Logan Jones <lo...@codescratch.com> on 2022/08/26 17:09:17 UTC
Fate Zookeeper Cleanup
Hello:
As a result of issuing user compactions with a broken iterator, we have
around 70k locks that do not have associated FATE operations according to
the fate print command. I believe this number is slowing down new
compactions that we'd like to issue. Even if that is not the case, I
believe we should probably clean up these locks. What is the best way to
clean up these locks?
Thanks,
- Logan
RE: Fate Zookeeper Cleanup
Posted by dev1 <de...@etcoleman.com>.
I think that those can be deleted - if you make sure to identify the correct locks.
I don't think that the fate delete command will work to clean those up, and you will end up directly deleting the node from ZooKeeper.
-----Original Message-----
From: Logan Jones <lo...@codescratch.com>
Sent: Friday, August 26, 2022 1:09 PM
To: dev@accumulo.apache.org
Subject: Fate Zookeeper Cleanup
Hello:
As a result of issuing user compactions with a broken iterator, we have around 70k locks that do not have associated FATE operations according to the fate print command. I believe this number is slowing down new compactions that we'd like to issue. Even if that is not the case, I believe we should probably clean up these locks. What is the best way to clean up these locks?
Thanks,
- Logan