[
https://issues.apache.org/jira/browse/ACCUMULO-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759106#comment-13759106
]
John Vines commented on ACCUMULO-902:
-------------------------------------
I mean, when you first start ingesting into a cluster you're going to have 0
major compactions and a lot of minor compactions. Why waste those major
compaction resources when minor compactions are necessary.
> 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
> Assignee: Keith Turner
> Fix For: 1.6.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
