RE: [Vote] Merge branch-trunk-win to trunk

2013-03-01 Thread Bikas Saha
That's sounds like a reasonable approach. Like you say below, we need to ensure is that the Java side of OS specific optimizations is generic and wont need drastic surgery when that optimization is ported to another platform. Bikas -Original Message- From: Uma Maheswara Rao G

[jira] [Created] (YARN-439) Flatten NodeHeartbeatResponse

2013-03-01 Thread Siddharth Seth (JIRA)
Siddharth Seth created YARN-439: --- Summary: Flatten NodeHeartbeatResponse Key: YARN-439 URL: https://issues.apache.org/jira/browse/YARN-439 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-440) Flatten RegisterNodeManagerResponse

2013-03-01 Thread Siddharth Seth (JIRA)
Siddharth Seth created YARN-440: --- Summary: Flatten RegisterNodeManagerResponse Key: YARN-440 URL: https://issues.apache.org/jira/browse/YARN-440 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-441) Clean up unused collection methods in various APIs

2013-03-01 Thread Siddharth Seth (JIRA)
Siddharth Seth created YARN-441: --- Summary: Clean up unused collection methods in various APIs Key: YARN-441 URL: https://issues.apache.org/jira/browse/YARN-441 Project: Hadoop YARN Issue Type:

Success: YARN-380 PreCommit Build #452

2013-03-01 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/YARN-380 Build: https://builds.apache.org/job/PreCommit-YARN-Build/452/ ### ## LAST 60 LINES OF THE CONSOLE ###

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

[jira] [Created] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-03-01 Thread Sandy Ryza (JIRA)
Sandy Ryza created YARN-444: --- Summary: Move special container exit codes from YarnConfiguration to API Key: YARN-444 URL: https://issues.apache.org/jira/browse/YARN-444 Project: Hadoop YARN Issue

Failed: YARN-417 PreCommit Build #453

2013-03-01 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/YARN-417 Build: https://builds.apache.org/job/PreCommit-YARN-Build/453/ ### ## LAST 60 LINES OF THE CONSOLE ###

Re: [Vote] Merge branch-trunk-win to trunk

2013-03-01 Thread Konstantin Shvachko
Commitment is a good thing. I think the two builds that I proposed are a prerequisite for Win support. If we commit windows patch people will start breaking it the next day. Which we wont know without the nightly build and wont be able to fix without the on-demand one. Making two builds is less

Re: [Vote] Merge branch-trunk-win to trunk

2013-03-01 Thread Chris Douglas
On Fri, Mar 1, 2013 at 1:57 PM, Konstantin Shvachko shv.had...@gmail.com wrote: Commitment is a good thing. I think the two builds that I proposed are a prerequisite for Win support. If we commit windows patch people will start breaking it the next day. Which we wont know without the nightly

Failed: YARN-198 PreCommit Build #455

2013-03-01 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/YARN-198 Build: https://builds.apache.org/job/PreCommit-YARN-Build/455/ ### ## LAST 60 LINES OF THE CONSOLE ###

Re: [Vote] Merge branch-trunk-win to trunk

2013-03-01 Thread sanjay Radia
On Mar 1, 2013, at 1:57 PM, Konstantin Shvachko wrote: Commitment is a good thing. I think the two builds that I proposed are a prerequisite for Win support. If we commit windows patch people will start breaking it the next day. Which we wont know without the nightly build and wont be able