[
https://issues.apache.org/jira/browse/ACCUMULO-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-902.
----------------------------------------
Resolution: Abandoned
Closing this old issue. If this is still a problem, please open a new issue or
PR at https://github.com/apache/accumulo
With compaction strategies and external compactions and compaction queues, this
feature may not make sense anymore.
> Have a common resource pool for minor and major compactions
> -----------------------------------------------------------
>
> Key: ACCUMULO-902
> URL: https://issues.apache.org/jira/browse/ACCUMULO-902
> Project: Accumulo
> Issue Type: Improvement
> Components: tserver
> Reporter: John Vines
> Priority: Major
>
> Currently we have a defined threadpool for minor and major compactions,
> independent of one another. However, there are situations where a system may
> be minor compaction heavy with no major, or vice versa. I would like to see a
> common threadpool which is accessible to both operations for work to be done,
> with guarantees for certain resources to be available to the other type of
> work. That is, it should be a defined pool size with a (configurable) minimum
> of resources maintained for the other to maintain a certain QoS. Of course,
> major is heavier than minor, so some weighting of operations needs to be done
> to keep workloads reasonable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
