Re: [jira] [Created] (YARN-443) allow OS scheduling priority of NM to be different then the containers it launches

2013-03-02 Thread kapoor
Just a thought,
This is can be achieved with the help of scripts in unix/linux but I guess we 
need to have jni calls for windows api to achieve the same.   
--Original Message--
From: Thomas Graves (JIRA)
To: yarn-dev@hadoop.apache.org
ReplyTo: yarn-dev@hadoop.apache.org
Subject: [jira] [Created] (YARN-443) allow OS scheduling priority of NM to be 
different then the containers it launches
Sent: Mar 2, 2013 2:33 AM

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

.
Thanks and Regards,
Kapoor
Phone: 9971061114

---
Sent from Blackberry

[jira] [Created] (YARN-443) allow OS scheduling priority of NM to be different then the containers it launches

2013-03-01 Thread Thomas Graves (JIRA)
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