keith-turner opened a new issue, #3547: URL: https://github.com/apache/accumulo/issues/3547
Compaction services and compactor groups form a graph which is hard to reason about from a resource allocation perspective. Originally when compaction services were introduced in 2.0 each service had a set of dedicated thread pools and this formed a tree. In 2.1 when external compaction were added, each external compaction queue could be associated with one or more services. So internal queues and executors formed a tree while exeternal queues and compactors formed a graph. Requiring the compaction service name in the compactor group name would make services and associated groups into a tree which is easier to reason about from a resource allocation perspective. For example when a user assigns a table to a compaction service they know what compactor groups are dedicated to that compaction service. Plan to flush this description out a bit more, this is a place holder. -- 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]
