Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 30 Oct 2013 14:17:25 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12623585.1355331587465.5325.1383142645551@arcas>
In-Reply-To: <JIRA.12623585.1355331587465@arcas>
References: <JIRA.12623585.1355331587465@arcas>
Subject: [jira] [Updated] (ACCUMULO-902) Have a common resource pool for
 minor and major compactions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Turner updated ACCUMULO-902:
----------------------------------

    Assignee:     (was: Keith Turner)

> 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
>             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 was sent by Atlassian JIRA
(v6.1#6144)