Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Fri, 1 Mar 2013 21:03:12 +0000 (UTC)
From: "Thomas Graves (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12634903.1362171729706.366999.1362171792398@arcas>
In-Reply-To: <JIRA.12634903.1362171729706@arcas>
References: <JIRA.12634903.1362171729706@arcas>
Subject: [jira] [Created] (YARN-443) allow OS scheduling priority of NM to
 be different then the containers it launches
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Thomas Graves created YARN-443:
----------------------------------

             Summary: allow OS scheduling priority of NM to be different then the containers it launches
                 Key: YARN-443
                 URL: https://issues.apache.org/jira/browse/YARN-443
             Project: Hadoop YARN
          Issue Type: Improvement
          Components: nodemanager
    Affects Versions: 0.23.6, 2.0.3-alpha
            Reporter: Thomas Graves
            Assignee: Thomas Graves


It would be nice if we could have the nodemanager run at a different OS scheduling priority then the containers so that you can still communicate with the nodemanager if the containers out of control.  

On linux we could launch the nodemanager at a higher priority, but then all the containers it launches would also be at that higher priority, so we need a way for the container executor to launch them at a lower priority.

I'm not sure how this applies to windows if at all.

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