Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 12 Dec 2012 17:01:24 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12623585.1355331587465.23885.1355331684032@arcas>
In-Reply-To: <JIRA.12623585.1355331587465@arcas>
References: <JIRA.12623585.1355331587465@arcas>
Subject: [jira] [Created] (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

John Vines created ACCUMULO-902:
-----------------------------------

             Summary: 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