[jira] [Commented] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064275#comment-14064275 ] Anubhav Dhoot commented on YARN-2244: - Fixed other issues except Can we use

[jira] [Commented] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064305#comment-14064305 ] Anubhav Dhoot commented on YARN-2244: - Uploading a new patch with code merged across

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.003.patch FairScheduler missing handling of containers for unknown

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.004.patch Merged code across schedulers FairScheduler missing handling of

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.005.patch Responded to feedback FairScheduler missing handling of

[jira] [Commented] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14066938#comment-14066938 ] Anubhav Dhoot commented on YARN-2244: - Seems unrelated . Most failures were with port

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.005.patch Retrigger test FairScheduler missing handling of containers for

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068879#comment-14068879 ] Anubhav Dhoot commented on YARN-1372: - Yes. Working on this now. Ensure all completed

[jira] [Commented] (YARN-2229) ContainerId can overflow with RM restart

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074635#comment-14074635 ] Anubhav Dhoot commented on YARN-2229: - We cannot simply add a field and have old code

[jira] [Updated] (YARN-556) RM Restart phase 2 - Work preserving restart

[ https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-556: --- Attachment: YARN-1372.prelim.patch NM does not remove completedContainers from its list until RM sends

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.prelim.patch NM does not remove completedContainers from its list until RM

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.prelim2.patch Second patch uploaded that adds expiration to the entries in NM

[jira] [Updated] (YARN-1370) Fair scheduler to re-populate container allocation state

[ https://issues.apache.org/jira/browse/YARN-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1370: Attachment: YARN-1370.001.patch Fair scheduler to re-populate container allocation state

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.001.patch Patch with tests Ensure all completed containers are reported to

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.001.patch Ensure all completed containers are reported to the AMs across RM

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102058#comment-14102058 ] Anubhav Dhoot commented on YARN-1372: - The tests that failed are all passing

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111713#comment-14111713 ] Anubhav Dhoot commented on YARN-1372: - bq. I meant is it possible for NM at

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.002_RMHandlesCompletedApp.patch Addresses feedback by having RM ack completed

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.002_NMHandlesCompletedApp.patch Addresses feedback by having NM remove

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.002_RMHandlesCompletedApp.patch Failure seems unrelated. Reuploading the same

[jira] [Commented] (YARN-2456) Possible deadlock in CapacityScheduler when RM is recovering apps

[ https://issues.apache.org/jira/browse/YARN-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127034#comment-14127034 ] Anubhav Dhoot commented on YARN-2456: - Can we sort the ApplicationStates based on

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.003.patch As per feedback, remove containers when the corresponding

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14130554#comment-14130554 ] Anubhav Dhoot commented on YARN-1372: - why adding context.getContainers().remove(cid);

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.004.patch Addressed all feedback Ensure all completed containers are

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.005.patch Fixed unit test failure Ensure all completed containers are

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.005.patch Rebased patch Ensure all completed containers are reported to the

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14132271#comment-14132271 ] Anubhav Dhoot commented on YARN-1372: - About the finishedContainersSentToAM in

[jira] [Assigned] (YARN-2331) Distinguish shutdown during supervision vs. shutdown for rolling upgrade

[ https://issues.apache.org/jira/browse/YARN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2331: --- Assignee: Anubhav Dhoot Distinguish shutdown during supervision vs. shutdown for rolling

[jira] [Updated] (YARN-2331) Distinguish shutdown during supervision vs. shutdown for rolling upgrade

[ https://issues.apache.org/jira/browse/YARN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2331: Assignee: (was: Anubhav Dhoot) Distinguish shutdown during supervision vs. shutdown for rolling

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14134762#comment-14134762 ] Anubhav Dhoot commented on YARN-1372: - A finishedContainer that was sent to previous AM

[jira] [Updated] (YARN-1959) Fix headroom calculation in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1959: Attachment: YARN-1959.prelim.patch Preliminary patch as per discussion - does min of

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.006.patch Addressed feedback except for 2 things (transferring all

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14141070#comment-14141070 ] Anubhav Dhoot commented on YARN-1372: - Addressed everything Regarding

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.007.patch Ensure all completed containers are reported to the AMs across RM

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.008.patch After offline discussion with Jian, remove containers from

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.009.patch Redo upload patch to kick jenkins. Removed unnecessary default

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.009.patch Rebased Ensure all completed containers are reported to the AMs

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.010.patch Fixed findbug warning and testcase failure Ensure all completed

[jira] [Updated] (YARN-1959) Fix headroom calculation in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1959: Attachment: YARN-1959.001.patch Addressed feedback Fix headroom calculation in Fair Scheduler

[jira] [Commented] (YARN-1959) Fix headroom calculation in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144076#comment-14144076 ] Anubhav Dhoot commented on YARN-1959: - The queue fair share for fifo and fair policies,

[jira] [Updated] (YARN-1959) Fix headroom calculation in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1959: Attachment: YARN-1959.002.patch Addressed feedback Fix headroom calculation in Fair Scheduler

[jira] [Commented] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152301#comment-14152301 ] Anubhav Dhoot commented on YARN-1879: - The patch needs to be updated Mark

[jira] [Commented] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152483#comment-14152483 ] Anubhav Dhoot commented on YARN-1879: - Nit in ProtocolHATestBase method will be

[jira] [Created] (YARN-2624) Resource Localization fails on a secure cluster until nm are restarted

Anubhav Dhoot created YARN-2624: --- Summary: Resource Localization fails on a secure cluster until nm are restarted Key: YARN-2624 URL: https://issues.apache.org/jira/browse/YARN-2624 Project: Hadoop

[jira] [Updated] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2624: Description: We have found resource localization fails on a cluster with following error in certain

[jira] [Commented] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153749#comment-14153749 ] Anubhav Dhoot commented on YARN-2624: - What we see is a bunch of preexisting local

[jira] [Updated] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1879: Attachment: YARN-1879.16.patch [~ozawa] I have updated your patch to compile with latest trunk.

[jira] [Updated] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2624: Attachment: YARN-2624.001.patch Attaching a patch that cleans up the local resource cache

[jira] [Updated] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2624: Attachment: YARN-2624.001.patch No apparent failure in jenkins output. Uploading it again Resource

[jira] [Commented] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156073#comment-14156073 ] Anubhav Dhoot commented on YARN-2624: - Failure seems unrelated to changes and does not

[jira] [Commented] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156079#comment-14156079 ] Anubhav Dhoot commented on YARN-2624: - The fix addresses the scenario moving from pre

[jira] [Commented] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156869#comment-14156869 ] Anubhav Dhoot commented on YARN-2624: - Thanks [~jlowe]! Resource Localization fails

[jira] [Created] (YARN-2661) Container Localization is not resource limited

Anubhav Dhoot created YARN-2661: --- Summary: Container Localization is not resource limited Key: YARN-2661 URL: https://issues.apache.org/jira/browse/YARN-2661 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-2661) Container Localization is not resource limited

[ https://issues.apache.org/jira/browse/YARN-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2661: --- Assignee: Anubhav Dhoot Container Localization is not resource limited

[jira] [Created] (YARN-2690) Make ReservationSystem and its dependent classes independent of Scheduler type

Anubhav Dhoot created YARN-2690: --- Summary: Make ReservationSystem and its dependent classes independent of Scheduler type Key: YARN-2690 URL: https://issues.apache.org/jira/browse/YARN-2690 Project:

[jira] [Assigned] (YARN-2690) Make ReservationSystem and its dependent classes independent of Scheduler type

[ https://issues.apache.org/jira/browse/YARN-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2690: --- Assignee: Anubhav Dhoot Make ReservationSystem and its dependent classes independent of

[jira] [Updated] (YARN-2690) Make ReservationSystem and its dependent classes independent of Scheduler type

[ https://issues.apache.org/jira/browse/YARN-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2690: Attachment: YARN-2690.001.patch Make ReservationSystem and its dependent classes independent of

[jira] [Updated] (YARN-2690) Make ReservationSystem and its dependent classes independent of Scheduler type

[ https://issues.apache.org/jira/browse/YARN-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2690: Attachment: YARN-2690.002.patch Done. I had kept it that way to make it easier to review and was

[jira] [Updated] (YARN-2690) Make ReservationSystem and its dependent classes independent of Scheduler type

[ https://issues.apache.org/jira/browse/YARN-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2690: Attachment: YARN-2690.002.patch Uploading again to kick jenkins. The previous failure were bind

[jira] [Commented] (YARN-1774) FS: Submitting to non-leaf queue throws NPE

[ https://issues.apache.org/jira/browse/YARN-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918786#comment-13918786 ] Anubhav Dhoot commented on YARN-1774: - Manual test consisted of a) Configure yarn to

[jira] [Commented] (YARN-1370) Fair scheduler to re-populate container allocation state

[ https://issues.apache.org/jira/browse/YARN-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932175#comment-13932175 ] Anubhav Dhoot commented on YARN-1370: - Ack. Will dig deeper on this On Wed, Mar 12,

[jira] [Assigned] (YARN-1536) Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead

[ https://issues.apache.org/jira/browse/YARN-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1536: --- Assignee: Anubhav Dhoot (was: Karthik Kambatla) Cleanup: Get rid of

[jira] [Updated] (YARN-1536) Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead

[ https://issues.apache.org/jira/browse/YARN-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1536: Attachment: yarn-1536.patch Cleanup: Get rid of ResourceManager#get*SecretManager() methods and

[jira] [Commented] (YARN-1536) Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead

[ https://issues.apache.org/jira/browse/YARN-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13935803#comment-13935803 ] Anubhav Dhoot commented on YARN-1536: - The test failures are unrelated. The change only

[jira] [Assigned] (YARN-1367) After restart NM should resync with the RM without killing containers

[ https://issues.apache.org/jira/browse/YARN-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1367: --- Assignee: Anubhav Dhoot After restart NM should resync with the RM without killing

[jira] [Updated] (YARN-1536) Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead

[ https://issues.apache.org/jira/browse/YARN-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1536: Attachment: yarn-1536.002.patch Addressed feedback Cleanup: Get rid of

[jira] [Assigned] (YARN-1368) RM should populate running container allocation information from NM resync

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1368: --- Assignee: Anubhav Dhoot RM should populate running container allocation information from NM

[jira] [Updated] (YARN-1536) Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead

[ https://issues.apache.org/jira/browse/YARN-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1536: Attachment: yarn-1536.003.patch Cleanup: Get rid of ResourceManager#get*SecretManager() methods

[jira] [Assigned] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1372: --- Assignee: Anubhav Dhoot Ensure all completed containers are reported to the AMs across RM

[jira] [Assigned] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1365: --- Assignee: Anubhav Dhoot ApplicationMasterService to allow Register and Unregister of an app

[jira] [Assigned] (YARN-1373) Transition RMApp and RMAppAttempt state to RUNNING after restart for recovered running apps

[ https://issues.apache.org/jira/browse/YARN-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1373: --- Assignee: Anubhav Dhoot Transition RMApp and RMAppAttempt state to RUNNING after restart for

[jira] [Assigned] (YARN-1823) Recover Unmanaged AMs

[ https://issues.apache.org/jira/browse/YARN-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1823: --- Assignee: Anubhav Dhoot Recover Unmanaged AMs - Key:

[jira] [Assigned] (YARN-1369) Capacity scheduler to re-populate container allocation state

[ https://issues.apache.org/jira/browse/YARN-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1369: --- Assignee: Anubhav Dhoot Capacity scheduler to re-populate container allocation state

[jira] [Assigned] (YARN-1371) FIFO scheduler to re-populate container allocation state

[ https://issues.apache.org/jira/browse/YARN-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1371: --- Assignee: Anubhav Dhoot FIFO scheduler to re-populate container allocation state

[jira] [Created] (YARN-1909) FairScheduler isStartvedForFairShare does not work when fairShare == 1

Anubhav Dhoot created YARN-1909: --- Summary: FairScheduler isStartvedForFairShare does not work when fairShare == 1 Key: YARN-1909 URL: https://issues.apache.org/jira/browse/YARN-1909 Project: Hadoop

[jira] [Created] (YARN-1923) Make FairScheduler resource ratio calculations terminate faster

Anubhav Dhoot created YARN-1923: --- Summary: Make FairScheduler resource ratio calculations terminate faster Key: YARN-1923 URL: https://issues.apache.org/jira/browse/YARN-1923 Project: Hadoop YARN

[jira] [Updated] (YARN-1923) Make FairScheduler resource ratio calculations terminate faster

[ https://issues.apache.org/jira/browse/YARN-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1923: Attachment: YARN-1923.patch Make FairScheduler resource ratio calculations terminate faster

[jira] [Commented] (YARN-1923) Make FairScheduler resource ratio calculations terminate faster

[ https://issues.apache.org/jira/browse/YARN-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965988#comment-13965988 ] Anubhav Dhoot commented on YARN-1923: - Would plannedResourceUsed or

[jira] [Updated] (YARN-1923) Make FairScheduler resource ratio calculations terminate faster

[ https://issues.apache.org/jira/browse/YARN-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1923: Attachment: YARN-1923.002.patch Addressed feedback Make FairScheduler resource ratio calculations

[jira] [Assigned] (YARN-1959) Fix headroom calculation in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1959: --- Assignee: Anubhav Dhoot (was: Sandy Ryza) Fix headroom calculation in Fair Scheduler

[jira] [Updated] (YARN-556) RM Restart phase 2 - Work preserving restart

[ https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-556: --- Attachment: WorkPreservingRestartPrototype.001.patch This prototype is a way to understand the overall

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986222#comment-13986222 ] Anubhav Dhoot commented on YARN-1368: - Hi [~jianhe], I have spent a bunch time of time

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988299#comment-13988299 ] Anubhav Dhoot commented on YARN-941: One option is we make the token expiration time

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13991272#comment-13991272 ] Anubhav Dhoot commented on YARN-2001: - The prototype attached to

[jira] [Updated] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1366: Attachment: YARN-1366.prototype.patch Added resync and refactored [~rohithsharma]'s changes

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995290#comment-13995290 ] Anubhav Dhoot commented on YARN-2001: - Won't killing the containers on RM restart/fail

[jira] [Commented] (YARN-556) RM Restart phase 2 - Work preserving restart

[ https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995328#comment-13995328 ] Anubhav Dhoot commented on YARN-556: bq. clustertimestamp is added to containerId so

[jira] [Updated] (YARN-1368) Common work to re-populate containers’ state into scheduler

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1368: Attachment: YARN-1368.combined.001.patch Thanks [~jianhe] for making the scheduler changes generic.

[jira] [Updated] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1365: Attachment: YARN-1365.initial.patch This is change from the prototype that allows applications to

[jira] [Commented] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999451#comment-13999451 ] Anubhav Dhoot commented on YARN-1366: - Seems like we are going with no resync api for

[jira] [Updated] (YARN-1569) For handle(SchedulerEvent) in FifoScheduler and CapacityScheduler, SchedulerEvent should get checked (instanceof) for appropriate type before casting

[ https://issues.apache.org/jira/browse/YARN-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1569: Assignee: (was: Anubhav Dhoot) For handle(SchedulerEvent) in FifoScheduler and

[jira] [Updated] (YARN-1550) NPE in FairSchedulerAppsBlock#render

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1550: Attachment: YARN-1550.001.patch Updated caolong's patch NPE in FairSchedulerAppsBlock#render

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998979#comment-13998979 ] Anubhav Dhoot commented on YARN-1365: - Hi [~ozawa] just saw your comment after i had it

[jira] [Assigned] (YARN-1569) For handle(SchedulerEvent) in FifoScheduler and CapacityScheduler, SchedulerEvent should get checked (instanceof) for appropriate type before casting

[ https://issues.apache.org/jira/browse/YARN-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1569: --- Assignee: Anubhav Dhoot For handle(SchedulerEvent) in FifoScheduler and CapacityScheduler,

[jira] [Commented] (YARN-1550) NPE in FairSchedulerAppsBlock#render

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002406#comment-14002406 ] Anubhav Dhoot commented on YARN-1550: - Manually tested by commenting out the line that

[jira] [Commented] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002438#comment-14002438 ] Anubhav Dhoot commented on YARN-1366: - I have a patch uploaded to

[jira] [Commented] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002499#comment-14002499 ] Anubhav Dhoot commented on YARN-1366: - To summarize along with current changes in

[jira] [Updated] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1365: Attachment: YARN-1365.002.patch Added ApplicationMasterService changes to send SHUTDOWN for attempt

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004900#comment-14004900 ] Anubhav Dhoot commented on YARN-1365: - The failed test has race conditions that i am

[jira] [Created] (YARN-2096) testQueueMetricsOnRMRestart has race condition

Anubhav Dhoot created YARN-2096: --- Summary: testQueueMetricsOnRMRestart has race condition Key: YARN-2096 URL: https://issues.apache.org/jira/browse/YARN-2096 Project: Hadoop YARN Issue Type:

  1   2   3   4   5   6   >