ctubbsii commented on PR #3926: URL: https://github.com/apache/accumulo/pull/3926#issuecomment-1816611392
@dlmarion asked: > > @ctubbsii said, "Can we emit information..." > > When you say emit, I think metrics. Is that what you mean? Metrics, logging, some pluggable interface to collect state, it doesn't really matter to me. I was mostly describing the general idea of shifting away from focusing on providing a specific end-to-end solution to providing the bits for users to create their own end-to-end solution. So, instead of us tracking the last write/compaction, or the last assignment, in our metadata and providing specific config knobs for that behavior, and then wiring that up for users as an option to a pre-provisioned balancer, we should maybe focus our implementations on providing insights (metrics is one way) to users, and pluggable interfaces for users to make their own choices about how to use those insights. This is just a better overall strategy, because it gives users more flexibility to support a variety of use cases we haven't thought of in advance, rather than constraining user imagination by locking them in on our specific thoughts. It also has the potential to dramatically reduce baked-in comp lexity and code size that we need to maintain. How this idea comes into play here: don't bother changing the property options and behavior... just deprecate it and create an emitter (metrics, or whatever) that users can collect information from, that records things like details on assignment activity or details on compaction activity. Then, leave it to users to wire that information in to their own custom balancer, or wherever else they want to use it. -- 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]
