[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862480#comment-13862480 ] Jian He commented on YARN-1490: --- Summarize the problem here: the basic assumption that contai

[jira] [Updated] (YARN-1560) TestYarnClient#testAMMRTokens fails with null AMRM token

[ https://issues.apache.org/jira/browse/YARN-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated YARN-1560: - Attachment: yarn-1560-v1.txt With patch v1, the test passes locally. > TestYarnClient#testAMMRTokens fails with n

[jira] [Commented] (YARN-1560) TestYarnClient#testAMMRTokens fails with null AMRM token

[ https://issues.apache.org/jira/browse/YARN-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862443#comment-13862443 ] Ted Yu commented on YARN-1560: -- In Eclipse, I placed a breakpoint on the line below: {code}

[jira] [Created] (YARN-1560) TestYarnClient#testAMMRTokens fails with null AMRM token

Ted Yu created YARN-1560: Summary: TestYarnClient#testAMMRTokens fails with null AMRM token Key: YARN-1560 URL: https://issues.apache.org/jira/browse/YARN-1560 Project: Hadoop YARN Issue Type: Test

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862436#comment-13862436 ] Bikas Saha commented on YARN-1490: -- Having more than 1 active attempt object will be have

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862419#comment-13862419 ] Jian He commented on YARN-1490: --- bq. We are better off changing the dispatcher related logic

[jira] [Commented] (YARN-1558) After apps are moved across queues, store new queue info in the RM state store

[ https://issues.apache.org/jira/browse/YARN-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862404#comment-13862404 ] Sandy Ryza commented on YARN-1558: -- Right. Updated the title and description with more in

[jira] [Updated] (YARN-1558) After apps are moved across queues, store new queue info in the RM state store

[ https://issues.apache.org/jira/browse/YARN-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1558: - Description: The result of moving an app to a new queue should persist across RM restarts. This will req

[jira] [Updated] (YARN-1558) After apps are moved across queues, store new queue info in the RM state store

[ https://issues.apache.org/jira/browse/YARN-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1558: - Summary: After apps are moved across queues, store new queue info in the RM state store (was: Persist app

[jira] [Commented] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

[ https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862359#comment-13862359 ] Bikas Saha commented on YARN-1489: -- Here is an idea: The RM allows the app to send it some

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862350#comment-13862350 ] Bikas Saha commented on YARN-1490: -- bq. The failed attempt is changed to still receive con

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862348#comment-13862348 ] Bikas Saha commented on YARN-1410: -- Clarification: The client can get a reject from the RM

[jira] [Commented] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.

[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862344#comment-13862344 ] Bikas Saha commented on YARN-1506: -- [~jianhe] Could you please review this. Thanks! > Rep

[jira] [Commented] (YARN-1029) Allow embedding leader election into the RM

[ https://issues.apache.org/jira/browse/YARN-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862341#comment-13862341 ] Bikas Saha commented on YARN-1029: -- The embedded elector was explicitly placed inside the

[jira] [Commented] (YARN-1558) Persist app queue changes in the RM state store

[ https://issues.apache.org/jira/browse/YARN-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862340#comment-13862340 ] Bikas Saha commented on YARN-1558: -- Looks like this was motivated from YARN-1495. In that

[jira] [Updated] (YARN-1559) Race between ServerRMProxy and ClientRMProxy setting RMProxy#INSTANCE

[ https://issues.apache.org/jira/browse/YARN-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1559: - Issue Type: Sub-task (was: Bug) Parent: YARN-149 > Race between ServerRMProxy and ClientRMProxy s

[jira] [Commented] (YARN-1558) Persist app queue changes in the RM state store

[ https://issues.apache.org/jira/browse/YARN-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862336#comment-13862336 ] Bikas Saha commented on YARN-1558: -- Motivation? Just a note : the RM state store is not de

[jira] [Commented] (YARN-1537) TestLocalResourcesTrackerImpl.testLocalResourceCache often failed

[ https://issues.apache.org/jira/browse/YARN-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862239#comment-13862239 ] haosdent commented on YARN-1537: I couldn't reproduce this error. Could you provide more de