accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-902) Have a common resource pool for minor and major compactions
Date Thu, 05 Sep 2013 00:34:51 GMT


Eric Newton commented on ACCUMULO-902:

Do you have a use case?

In the meantime, separate thread pools seem nearly ideal to handle a few fast minor compactions,
and a queue of slower major compactions.

> Have a common resource pool for minor and major compactions
> -----------------------------------------------------------
>                 Key: ACCUMULO-902
>                 URL:
>             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:

View raw message