dlmarion opened a new issue, #4232: URL: https://github.com/apache/accumulo/issues/4232
I just had a discussion with @ddanielr about #3274. We went on a tangent and ended up taking about how logs are sorted by random tservers. Dan brought up that for the elasticity changes we may want to consider moving log sorting out of tservers into its own process that could be autoscaled and isolated from immediate scans. Update : an alternative to moving log sort to its own process would be to make it resource group aware. So make log sort happen within a specific resource group that makes sense for the particular WAL. Currently when sorting a log the entire set of tablet servers may be used. Ideally if tablet server A in resource group RG1 dies, the later when its logs are sorted it would be nice if that was done by tservers in RG1. -- 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]
