Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: phrocker <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-199-accumulo@git.apache.org>
In-Reply-To: <git-pr-199-accumulo@git.apache.org>
Subject: [GitHub] accumulo issue #199: DO NOT MERGE: PROOF OF CONCEPT
Content-Type: text/plain
Message-Id: <20170110023600.BB6D4DFA22@git1-us-west.apache.org>
Date: Tue, 10 Jan 2017 02:36:00 +0000 (UTC)
archived-at: Tue, 10 Jan 2017 02:36:02 -0000

Github user phrocker commented on the issue:

    https://github.com/apache/accumulo/pull/199
  
    @dlmarion Some of these things aren't well defined in Property.java yet as I was worried about going in a direction and it being all wrong. I take your comment as a 'feature request' sort of. To better define pools resource queues will allow configurations to define thread priorities. We would rely on the operating system to do prioritization. 
    
    I think this was a question I have. Should the configuration allow users to select from a set of configured pools of resources or allow them to override and select any set of resources that are defined? @keith-turner  thoughts? 
    
    I'll try and better define some of these properties tomorrow so I can clarify this for the next person. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---