ctubbsii commented on PR #3926: URL: https://github.com/apache/accumulo/pull/3926#issuecomment-1809180852
> Wondering it is would be better to remove the `tserver.last.location.mode` property and always set the last location on assignment. There would be less code to maintain and test (do not need to test the property or handle removing last when its set to none). For the case where a balancer plugin is not interested in the last location information, it can ignore it. Can we emit information, such as last assignment, last hosted location for write, etc. that users can use to empower their own pluggable balancer? It seems like historically we made assumptions about how users might want to balance, and then we had to add this property to handle some additional use cases that users preferred, but it'd probably better to just to emit data that the users might want to use, and leave the balancing strategy up to them. That would maximally empower users and minimize the code we need to maintain (except for the code to emit the requested info, which should be simpler, and generally useful enough to warrant any complexity it might require). -- 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]
