[jira] [Assigned] (YARN-363) yarn proxyserver fails to find webapps/proxy directory on startup

[ https://issues.apache.org/jira/browse/YARN-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenji Kikushima reassigned YARN-363: Assignee: Kenji Kikushima yarn proxyserver fails to find webapps/proxy directory on

[jira] [Commented] (YARN-363) yarn proxyserver fails to find webapps/proxy directory on startup

[ https://issues.apache.org/jira/browse/YARN-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641557#comment-13641557 ] Hadoop QA commented on YARN-363: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-576) RM should not allow registrations from NMs that do not satisfy minimum scheduler allocations

[ https://issues.apache.org/jira/browse/YARN-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641561#comment-13641561 ] Hadoop QA commented on YARN-576: {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-576) RM should not allow registrations from NMs that do not satisfy minimum scheduler allocations

[ https://issues.apache.org/jira/browse/YARN-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenji Kikushima updated YARN-576: - Attachment: YARN-576-3.patch In addition, changed to use BuilderUtils in TestRMNMRPCResponseId and

[jira] [Commented] (YARN-595) Refactor fair scheduler to use common Resources

[ https://issues.apache.org/jira/browse/YARN-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641647#comment-13641647 ] Hudson commented on YARN-595: - Integrated in Hadoop-Yarn-trunk #194 (See

[jira] [Commented] (YARN-289) Fair scheduler allows reservations that won't fit on node

[ https://issues.apache.org/jira/browse/YARN-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641648#comment-13641648 ] Hudson commented on YARN-289: - Integrated in Hadoop-Yarn-trunk #194 (See

[jira] [Commented] (YARN-605) Failing unit test in TestNMWebServices when using git for source control

[ https://issues.apache.org/jira/browse/YARN-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641653#comment-13641653 ] Hudson commented on YARN-605: - Integrated in Hadoop-Yarn-trunk #194 (See

[jira] [Commented] (YARN-579) Make ApplicationToken part of Container's token list to help RM-restart

[ https://issues.apache.org/jira/browse/YARN-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641655#comment-13641655 ] Hudson commented on YARN-579: - Integrated in Hadoop-Yarn-trunk #194 (See

[jira] [Commented] (YARN-289) Fair scheduler allows reservations that won't fit on node

[ https://issues.apache.org/jira/browse/YARN-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641746#comment-13641746 ] Hudson commented on YARN-289: - Integrated in Hadoop-Hdfs-trunk #1383 (See

[jira] [Commented] (YARN-577) ApplicationReport does not provide progress value of application

[ https://issues.apache.org/jira/browse/YARN-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641750#comment-13641750 ] Hudson commented on YARN-577: - Integrated in Hadoop-Hdfs-trunk #1383 (See

[jira] [Commented] (YARN-605) Failing unit test in TestNMWebServices when using git for source control

[ https://issues.apache.org/jira/browse/YARN-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641751#comment-13641751 ] Hudson commented on YARN-605: - Integrated in Hadoop-Hdfs-trunk #1383 (See

[jira] [Commented] (YARN-579) Make ApplicationToken part of Container's token list to help RM-restart

[ https://issues.apache.org/jira/browse/YARN-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641753#comment-13641753 ] Hudson commented on YARN-579: - Integrated in Hadoop-Hdfs-trunk #1383 (See

[jira] [Commented] (YARN-595) Refactor fair scheduler to use common Resources

[ https://issues.apache.org/jira/browse/YARN-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641821#comment-13641821 ] Hudson commented on YARN-595: - Integrated in Hadoop-Mapreduce-trunk #1410 (See

[jira] [Commented] (YARN-577) ApplicationReport does not provide progress value of application

[ https://issues.apache.org/jira/browse/YARN-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641826#comment-13641826 ] Hudson commented on YARN-577: - Integrated in Hadoop-Mapreduce-trunk #1410 (See

[jira] [Commented] (YARN-605) Failing unit test in TestNMWebServices when using git for source control

[ https://issues.apache.org/jira/browse/YARN-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641827#comment-13641827 ] Hudson commented on YARN-605: - Integrated in Hadoop-Mapreduce-trunk #1410 (See

[jira] [Commented] (YARN-579) Make ApplicationToken part of Container's token list to help RM-restart

[ https://issues.apache.org/jira/browse/YARN-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641829#comment-13641829 ] Hudson commented on YARN-579: - Integrated in Hadoop-Mapreduce-trunk #1410 (See

[jira] [Created] (YARN-609) Fix synchronization issues in APIs which take in lists

Vinod Kumar Vavilapalli created YARN-609: Summary: Fix synchronization issues in APIs which take in lists Key: YARN-609 URL: https://issues.apache.org/jira/browse/YARN-609 Project: Hadoop YARN

[jira] [Created] (YARN-610) ClientToken should not be set in the environment

Siddharth Seth created YARN-610: --- Summary: ClientToken should not be set in the environment Key: YARN-610 URL: https://issues.apache.org/jira/browse/YARN-610 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-422) Add AM-NM client library

[ https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642038#comment-13642038 ] Bikas Saha commented on YARN-422: - Overall the approach looks fine. The patch looks like

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: (was: YARN-326.patch) Add multi-resource scheduling to the fair scheduler

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: YARN-326.patch Add multi-resource scheduling to the fair scheduler

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642040#comment-13642040 ] Sandy Ryza commented on YARN-326: - Attached a design doc PDF and an initial patch. It still

[jira] [Created] (YARN-611) Add an AM retry count reset window to YARN RM

Chris Riccomini created YARN-611: Summary: Add an AM retry count reset window to YARN RM Key: YARN-611 URL: https://issues.apache.org/jira/browse/YARN-611 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-612) Cleanup BuilderUtils

Siddharth Seth created YARN-612: --- Summary: Cleanup BuilderUtils Key: YARN-612 URL: https://issues.apache.org/jira/browse/YARN-612 Project: Hadoop YARN Issue Type: Bug Reporter:

[jira] [Assigned] (YARN-386) [Umbrella] YARN API Changes

[ https://issues.apache.org/jira/browse/YARN-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth reassigned YARN-386: --- Assignee: Siddharth Seth [Umbrella] YARN API Changes ---

[jira] [Assigned] (YARN-610) ClientToken should not be set in the environment

[ https://issues.apache.org/jira/browse/YARN-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-610: Assignee: Vinod Kumar Vavilapalli ClientToken should not be set in the

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642059#comment-13642059 ] Hadoop QA commented on YARN-326: {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-612) Cleanup BuilderUtils

[ https://issues.apache.org/jira/browse/YARN-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-612: Issue Type: Sub-task (was: Bug) Parent: YARN-386 Cleanup BuilderUtils

[jira] [Commented] (YARN-542) Change the default global AM max-attempts value to be not one

[ https://issues.apache.org/jira/browse/YARN-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642067#comment-13642067 ] Bikas Saha commented on YARN-542: - I think that the global default should be one because an

[jira] [Created] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

Bikas Saha created YARN-614: --- Summary: Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1 Key: YARN-614 URL: https://issues.apache.org/jira/browse/YARN-614

[jira] [Commented] (YARN-611) Add an AM retry count reset window to YARN RM

[ https://issues.apache.org/jira/browse/YARN-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642086#comment-13642086 ] Zhijie Shen commented on YARN-611: -- Each Yarn application can specify its individual retry

[jira] [Created] (YARN-615) ContainerLaunchContext.containerTokens should simply be called tokens

Vinod Kumar Vavilapalli created YARN-615: Summary: ContainerLaunchContext.containerTokens should simply be called tokens Key: YARN-615 URL: https://issues.apache.org/jira/browse/YARN-615

[jira] [Commented] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642113#comment-13642113 ] Vinod Kumar Vavilapalli commented on YARN-614: -- We need to consolidate the

[jira] [Commented] (YARN-422) Add AM-NM client library

[ https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642119#comment-13642119 ] Vinod Kumar Vavilapalli commented on YARN-422: -- startContainer/stopContainer

[jira] [Commented] (YARN-611) Add an AM retry count reset window to YARN RM

[ https://issues.apache.org/jira/browse/YARN-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642132#comment-13642132 ] Sandy Ryza commented on YARN-611: - Not suggesting this as a complete solution to either

[jira] [Commented] (YARN-611) Add an AM retry count reset window to YARN RM

[ https://issues.apache.org/jira/browse/YARN-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642162#comment-13642162 ] Chris Riccomini commented on YARN-611: -- @zshen Simply bumping the retries to infinite

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642163#comment-13642163 ] Chris Douglas commented on YARN-45: --- If everyone's OK with the current patch as a base,

[jira] [Updated] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-528: Attachment: y528_AppIdPart_03_fixUsage.txt y528_AppIdPart_02_AppIdChanges.txt

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642286#comment-13642286 ] Andrew Ferguson commented on YARN-326: -- hi Sandy, I'm wondering if you want minimum

[jira] [Updated] (YARN-589) Expose a REST API for monitoring the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-589: Attachment: fairscheduler.xml Expose a REST API for monitoring the fair scheduler

[jira] [Commented] (YARN-589) Expose a REST API for monitoring the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642305#comment-13642305 ] Sandy Ryza commented on YARN-589: - Attached xml output from a first cut at this. Is it

[jira] [Moved] (YARN-617) [MR-279] In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-2744 to YARN-617: - Component/s: (was: mrv2)

[jira] [Updated] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-617: - Summary: In unsercure mode, AM can fake resource requirements (was: [MR-279] In

[jira] [Updated] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-617: - Issue Type: Sub-task (was: Bug) Parent: YARN-47 In unsercure mode,

[jira] [Assigned] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-617: Assignee: Vinod Kumar Vavilapalli In unsercure mode, AM can fake

[jira] [Resolved] (YARN-613) Create NM proxy per NM instead of per container

[ https://issues.apache.org/jira/browse/YARN-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-613. -- Resolution: Duplicate Just moved YARN-617 over from mapreduce. Closing this as

[jira] [Commented] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642354#comment-13642354 ] Karthik Kambatla commented on YARN-614: --- Will the hardware errors include IOException

[jira] [Commented] (YARN-616) Support guaranteed shares in the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642357#comment-13642357 ] Karthik Kambatla commented on YARN-616: --- Doesn't the min value address this?

[jira] [Commented] (YARN-616) Support guaranteed shares in the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642361#comment-13642361 ] Sandy Ryza commented on YARN-616: - Currently, minimum shares in the fair scheduler will go

[jira] [Commented] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642366#comment-13642366 ] Hadoop QA commented on YARN-528: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-616) Support guaranteed shares in the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642369#comment-13642369 ] Karthik Kambatla commented on YARN-616: --- Sure. I think the best way to achieve this

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642370#comment-13642370 ] Sandy Ryza commented on YARN-326: - Thanks for taking a look Andrew. Minimum shares

[jira] [Commented] (YARN-616) Support guaranteed shares in the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642371#comment-13642371 ] Sandy Ryza commented on YARN-616: - Agreed. Support guaranteed shares in

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: YARN-326.patch Add multi-resource scheduling to the fair scheduler

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642380#comment-13642380 ] Sandy Ryza commented on YARN-326: - Latest patch should fix the findbugs warning and adds in

[jira] [Commented] (YARN-613) Create NM proxy per NM instead of per container

[ https://issues.apache.org/jira/browse/YARN-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642387#comment-13642387 ] Bikas Saha commented on YARN-613: - Looks related to YARN-617 but not a duplicate. [~vinodkv]

[jira] [Commented] (YARN-591) RM recovery related records do not belong to the API

[ https://issues.apache.org/jira/browse/YARN-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642399#comment-13642399 ] Bikas Saha commented on YARN-591: - Its a clean move. Thanks! I should have done it correct

[jira] [Commented] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642401#comment-13642401 ] Bikas Saha commented on YARN-614: - 1) Node lost 2) ContainerExitStatus of AM denotes

[jira] [Commented] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642403#comment-13642403 ] Vinod Kumar Vavilapalli commented on YARN-617: -- Like I mentioned in the

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642405#comment-13642405 ] Hadoop QA commented on YARN-326: {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-562: - Attachment: YARN-562.11.patch New patch address above comments, and rename

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642425#comment-13642425 ] Hadoop QA commented on YARN-562: {color:red}-1 overall{color}. Here are the results of

[jira] [Reopened] (YARN-613) Create NM proxy per NM instead of per container

[ https://issues.apache.org/jira/browse/YARN-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened YARN-613: -- Assignee: Vinod Kumar Vavilapalli I wanted to do it all together at YARN-571,

[jira] [Commented] (YARN-613) Create NM proxy per NM instead of per container

[ https://issues.apache.org/jira/browse/YARN-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642435#comment-13642435 ] Vinod Kumar Vavilapalli commented on YARN-613: -- bq. I wanted to do it all

[jira] [Updated] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-562: - Attachment: YARN-562.12.patch new patch rebase.. NM should reject containers allocated by

[jira] [Commented] (YARN-575) ContainerManager APIs should be user accessible

[ https://issues.apache.org/jira/browse/YARN-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642445#comment-13642445 ] Vinod Kumar Vavilapalli commented on YARN-575: -- I don't think we really want

[jira] [Assigned] (YARN-575) ContainerManager APIs should be user accessible

[ https://issues.apache.org/jira/browse/YARN-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-575: Assignee: Vinod Kumar Vavilapalli ContainerManager APIs should be user

[jira] [Commented] (YARN-435) Make it easier to access cluster topology information in an AM

[ https://issues.apache.org/jira/browse/YARN-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642450#comment-13642450 ] Vinod Kumar Vavilapalli commented on YARN-435: -- I think that opening a new

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642475#comment-13642475 ] Hadoop QA commented on YARN-562: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642499#comment-13642499 ] Jian He commented on YARN-562: -- bq. RM_INVALID_IDENTIFIER set to 0 doesnt sound right as many

[jira] [Updated] (YARN-618) Modify RM_INVALID_IDENTIFIER to a -ve number

[ https://issues.apache.org/jira/browse/YARN-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-618: - Description: RM_INVALID_IDENTIFIER set to 0 doesnt sound right as many tests set it to 0. Probably a -ve number is

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

[ https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy closed YARN-443. -- allow OS scheduling priority of NM to be different than the containers it launches

[jira] [Closed] (YARN-470) Support a way to disable resource monitoring on the NodeManager

[ https://issues.apache.org/jira/browse/YARN-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy closed YARN-470. -- Support a way to disable resource monitoring on the NodeManager

[jira] [Closed] (YARN-449) HBase test failures when running against Hadoop 2

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy closed YARN-449. -- HBase test failures when running against Hadoop 2 -

[jira] [Closed] (YARN-429) capacity-scheduler config missing from yarn-test artifact

[ https://issues.apache.org/jira/browse/YARN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy closed YARN-429. -- capacity-scheduler config missing from yarn-test artifact

[jira] [Commented] (YARN-578) NodeManager should use SecureIOUtils for serving logs and intermediate outputs

[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642524#comment-13642524 ] Omkar Vinit Joshi commented on YARN-578: There are 3 issues related to symlink

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642554#comment-13642554 ] Vinod Kumar Vavilapalli commented on YARN-562: -- The latest patch looks good to

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642563#comment-13642563 ] Hudson commented on YARN-562: - Integrated in Hadoop-trunk-Commit #3668 (See

[jira] [Created] (YARN-619) Build break due to changes in YARN related to ApplicationConstants.Environment.

Tsuyoshi OZAWA created YARN-619: --- Summary: Build break due to changes in YARN related to ApplicationConstants.Environment. Key: YARN-619 URL: https://issues.apache.org/jira/browse/YARN-619 Project:

[jira] [Updated] (YARN-619) Build break due to changes in YARN related to ApplicationConstants.Environment.

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-619: Component/s: nodemanager Build break due to changes in YARN related to

[jira] [Updated] (YARN-619) Build break due to changes in YARN related to ApplicationConstants.Environment.

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-619: Description: YARN-562 doesn't take into account the changes

[jira] [Updated] (YARN-619) Build break due to changes in YARN-562

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-619: Summary: Build break due to changes in YARN-562 (was: Build break due to changes in YARN related to

[jira] [Updated] (YARN-619) Build break due to changes in YARN-562

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-619: Description: YARN-562 break the build in trunk, because ResourceManagerConstants is not included.

[jira] [Commented] (YARN-619) Build break due to changes in YARN-562

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642592#comment-13642592 ] Vinod Kumar Vavilapalli commented on YARN-619: -- Am looking at this. I committed

[jira] [Resolved] (YARN-619) Build break due to changes in YARN-562

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-619. -- Resolution: Fixed Assignee: Vinod Kumar Vavilapalli Okay, I originally

[jira] [Updated] (YARN-619) Build break due to changes in YARN-562

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-619: Description: YARN-562 break the build in trunk, because ResourceManagerConstants,

[jira] [Updated] (YARN-619) Build break due to changes in YARN-562

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-619: Attachment: YARN-619.patch Fixed build by adding forgotten files. Build break due

[jira] [Commented] (YARN-619) Build break due to changes in YARN-562

[ https://issues.apache.org/jira/browse/YARN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642600#comment-13642600 ] Tsuyoshi OZAWA commented on YARN-619: - NP! Build break due to changes

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642603#comment-13642603 ] Tsuyoshi OZAWA commented on YARN-562: - This build failure can be fixed by using the

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642610#comment-13642610 ] Vinod Kumar Vavilapalli commented on YARN-562: -- Jian, the patch isn't applying