keith-turner commented on issue #3559:
URL: https://github.com/apache/accumulo/issues/3559#issuecomment-1756172061
The following are reasons why I think it makes sense to do this in
elasticity.
* With the adoption of using conditional mutations in elasticity we may be
able able to get rid if table locks. See #3823. If table locks are not
removed, then supporting FATE using the metadata table for storage would mean
table locks also need to support the metadata table. Table locks are currently
stored in zookeeper. So implementing this in main and merging to elasticity
may mean implementing tables locks in the metadata table and then throwing that
work away on merge.
* The needs for storing FATE operations in the metadata table is being able
to do per tablet operations in FATE like the compaction use case described in
this issue and #3560 and #3526. These use cases are not present in main.
--
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]
