You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "dlmarion (via GitHub)" <gi...@apache.org> on 2026/05/18 14:49:35 UTC
[I] Table Delete Fate contention [accumulo]
dlmarion opened a new issue, #6374:
URL: https://github.com/apache/accumulo/issues/6374
The CleanUp step of the Delete Fate operation configures the [MetaDataTableScanner](https://github.com/apache/accumulo/blob/rel/2.1.4/server/manager/src/main/java/org/apache/accumulo/manager/tableOps/delete/CleanUp.java#L95) so that it can compute each tablets location. When all tablets are unassigned, then it can move on to the next step in the operation.
However, [MetaDataTableScanner.configureScanner](https://github.com/apache/accumulo/blob/rel/2.1.4/server/base/src/main/java/org/apache/accumulo/server/manager/state/MetaDataTableScanner.java#L92) calls [Manager.merges](https://github.com/apache/accumulo/blob/rel/2.1.4/server/manager/src/main/java/org/apache/accumulo/manager/Manager.java#L1812) which iterates over every table to read its merge information from ZooKeeper. Manager.getMergeInfo is synchronized, causing Delete Fate Ops to block.
[MetaDataTableScanner.createTabletLocationState](https://github.com/apache/accumulo/blob/rel/2.1.4/server/base/src/main/java/org/apache/accumulo/server/manager/state/MetaDataTableScanner.java#L164), called by `CleanUp.isReady`, doesn't use the Merge information.
It's also possible that when CleanUp calls MetaDataTableScanner.configureScanner, `null` could be passed for the Manager state object.
--
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: notifications-unsubscribe@accumulo.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Table Delete Fate contention [accumulo]
Posted by "dlmarion (via GitHub)" <gi...@apache.org>.
dlmarion commented on issue #6374:
URL: https://github.com/apache/accumulo/issues/6374#issuecomment-4480993528
I created #6378 as a potential resolution to this issue. I looked at the code calling MetadataTableScanner.configureScanner and it appears the Manager is passed in all cases. I'm not sure the consequence of not passing it in this case.
--
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: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Table Delete Fate contention [accumulo]
Posted by "dlmarion (via GitHub)" <gi...@apache.org>.
dlmarion closed issue #6374: Table Delete Fate contention
URL: https://github.com/apache/accumulo/issues/6374
--
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: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org