You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "cshannon (via GitHub)" <gi...@apache.org> on 2023/09/01 13:14:42 UTC

[GitHub] [accumulo] cshannon commented on issue #3709: Avoid storing split points in Zookeeper

cshannon commented on issue #3709:
URL: https://github.com/apache/accumulo/issues/3709#issuecomment-1702731996

   In general, I was thinking as we go to Elasticity it might be nice to see if we can get more things out of Zookeeper and store in Accumulo itself. Zookeeper can be a bottleneck and other projects are dropping it for performance reasons as clusters are getting larger (such as Kafka). In theory the changes in Elasticity will allow us to scale up with many more tablets since they are offline/ondemand which would require a lot more metadata tracking in ZK and I can see that could cause issues, like in this case.
   
   For example, for the split points here, I'm wondering if in the future it would be make sense to store the split points in Accumulo in another table. Anyways, just a thought, in this case the tmp file probably makes sense since it's already doing that elsewhere and code could be shared. There also might be reasons that isn't possible but again this is just more of a general comment that could be applied to other situations too.


-- 
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