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

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

[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-tabpanel&focusedCommentId=14144076#comment-14144076 ] Anubhav Dhoot commented on YARN-1959: - The queue fair share for fifo and fair poli

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

[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-tabpanel&focusedCommentId=14152301#comment-14152301 ] Anubhav Dhoot commented on YARN-1879: - The patch needs to be updated &g

[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-tabpanel&focusedCommentId=14152483#comment-14152483 ] Anubhav Dhoot commented on YARN-1879: - Nit in ProtocolHATestBase > method wil

[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 secure cluster until nm are restarted

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2624: Component/s: nodemanager > Resource Localization fails on a secure cluster until nm are restar

[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-tabpanel&focusedCommentId=14153749#comment-14153749 ] Anubhav Dhoot commented on YARN-2624: - What we see is a bunch of preexisting l

[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

[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-tabpanel&focusedCommentId=14156073#comment-14156073 ] Anubhav Dhoot commented on YARN-2624: - Failure seems unrelated to changes and does

[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-tabpanel&focusedCommentId=14156079#comment-14156079 ] Anubhav Dhoot commented on YARN-2624: - The fix addresses the scenario moving from

[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-tabpanel&focusedCommentId=14156869#comment-14156869 ] Anubhav Dhoot commented on YARN-2624: - Thanks [~jlowe]! > Resource Localizatio

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

[jira] [Updated] (YARN-2574) Add support for FairScheduler to the ReservationSystem

[ https://issues.apache.org/jira/browse/YARN-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2574: Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-2572) > Add support

[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

[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

[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] [Created] (YARN-2738) Add FairReservationSystem for FairScheduler

Anubhav Dhoot created YARN-2738: --- Summary: Add FairReservationSystem for FairScheduler Key: YARN-2738 URL: https://issues.apache.org/jira/browse/YARN-2738 Project: Hadoop YARN Issue Type: Sub

[jira] [Assigned] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2738: --- Assignee: Anubhav Dhoot > Add FairReservationSystem for FairSchedu

[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.003.patch Added comments to ReservationSchedulerConfiguration. Prefer a getter

[jira] [Commented] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182685#comment-14182685 ] Anubhav Dhoot commented on YARN-2738: - Depends on the refactoring done in YARN-

[jira] [Updated] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2738: Attachment: YARN-2738.001.patch Adds support in FairScheduler xml for reading queue reservation

[jira] [Commented] (YARN-2712) Adding tests about FSQueue and headroom of FairScheduler to TestWorkPreservingRMRestart

[ https://issues.apache.org/jira/browse/YARN-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183598#comment-14183598 ] Anubhav Dhoot commented on YARN-2712: - Minor comments below. LGTM otherwise T

[jira] [Created] (YARN-2773) ReservationSystem's use of Queue names vs paths is inconsistent for CapacityReservationSystem and FairReservationSystem

Anubhav Dhoot created YARN-2773: --- Summary: ReservationSystem's use of Queue names vs paths is inconsistent for CapacityReservationSystem and FairReservationSystem Key: YARN-2773 URL: https://issues.apach

[jira] [Commented] (YARN-2383) Add ability to renew ClientToAMToken

[ https://issues.apache.org/jira/browse/YARN-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191121#comment-14191121 ] Anubhav Dhoot commented on YARN-2383: - Hi [~xgong] can you please rebase the p

[jira] [Commented] (YARN-2735) diskUtilizationPercentageCutoff and diskUtilizationSpaceCutoff are initialized twice in DirectoryCollection

[ https://issues.apache.org/jira/browse/YARN-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194893#comment-14194893 ] Anubhav Dhoot commented on YARN-2735: - This looks like a trivial patch that shoul

[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.004.patch Fixed the javadoc warning because of typo Re 1. The information

[jira] [Updated] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2738: Attachment: YARN-2738.002.patch Thanks [~kasha] for the review 1. Removed TODO and opened YARN-2773

[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.004.patch Fixed javac warning. That was some preexisting code unchanged by the

[jira] [Commented] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197038#comment-14197038 ] Anubhav Dhoot commented on YARN-2738: - I don't believe the implementation

[jira] [Commented] (YARN-2675) the containersKilled metrics is not updated when the container is killed during localization.

[ https://issues.apache.org/jira/browse/YARN-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213107#comment-14213107 ] Anubhav Dhoot commented on YARN-2675: - Minor: In ContainerImpl finished, it ma

[jira] [Commented] (YARN-2868) Add metric for initial container launch time

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215025#comment-14215025 ] Anubhav Dhoot commented on YARN-2868: - Seems like the QueueMetrics change ca

[jira] [Commented] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216246#comment-14216246 ] Anubhav Dhoot commented on YARN-2738: - The minimal configuration we need is abilit

[jira] [Commented] (YARN-2802) add AM container launch and register delay metrics in QueueMetrics to help diagnose performance issue.

[ https://issues.apache.org/jira/browse/YARN-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216635#comment-14216635 ] Anubhav Dhoot commented on YARN-2802: - This metric probably will not catch issues

[jira] [Commented] (YARN-2802) add AM container launch and register delay metrics in QueueMetrics to help diagnose performance issue.

[ https://issues.apache.org/jira/browse/YARN-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216915#comment-14216915 ] Anubhav Dhoot commented on YARN-2802: - LGTM > add AM container launch and r

[jira] [Updated] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2738: Attachment: YARN-2738.003.patch Removed configurability in fairscheduler configuration as per

[jira] [Created] (YARN-2881) Implement PlanFollower for FairScheduler

Anubhav Dhoot created YARN-2881: --- Summary: Implement PlanFollower for FairScheduler Key: YARN-2881 URL: https://issues.apache.org/jira/browse/YARN-2881 Project: Hadoop YARN Issue Type: Sub

[jira] [Commented] (YARN-2773) ReservationSystem's use of Queue names vs paths is inconsistent for CapacityReservationSystem and FairReservationSystem

[ https://issues.apache.org/jira/browse/YARN-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219769#comment-14219769 ] Anubhav Dhoot commented on YARN-2773: - getAdmissionPolicy uses the planQueue

[jira] [Commented] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219914#comment-14219914 ] Anubhav Dhoot commented on YARN-2738: - The issue is the only configuration in

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.prelim.patch Based on YARN-2738. FairSchedulerPlanFollower with unit tests

[jira] [Created] (YARN-2119) Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590

Anubhav Dhoot created YARN-2119: --- Summary: Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590 Key: YARN-2119 URL: https://issues.apache.org/jira/browse/YARN-2119 Project: Hadoop YARN

[jira] [Updated] (YARN-2119) Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590

[ https://issues.apache.org/jira/browse/YARN-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2119: Attachment: YARN-2119.patch Fix with unit tests. Ran

[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.003.patch Fixed failures after resolving with some interim changes that were

[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-tabpanel&focusedCommentId=14019832#comment-14019832 ] Anubhav Dhoot commented on YARN-1365: - I will fix it here. I will be posting a

[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.004.patch 1) Added a flag to AppAttemptAddedSchedulerEvent that tells

[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-tabpanel&focusedCommentId=14027118#comment-14027118 ] Anubhav Dhoot commented on YARN-1365: - >If an app did not register and do unr

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14030016#comment-14030016 ] Anubhav Dhoot commented on YARN-1367: - I will send an updated patch shortly >

[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.005.patch Addressed Jian's comments. updated finishApplicationMast

[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-tabpanel&focusedCommentId=14030874#comment-14030874 ] Anubhav Dhoot commented on YARN-1365: - Hi [~jianhe] I addressed all your comm

[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.005.patch > ApplicationMasterService to allow Register and Unregister of

[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-tabpanel&focusedCommentId=14031268#comment-14031268 ] Anubhav Dhoot commented on YARN-1365: - Agreed. I was trying to be consistent

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14034359#comment-14034359 ] Anubhav Dhoot commented on YARN-1367: - I am still working on it. Will have an up

[jira] [Created] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

Anubhav Dhoot created YARN-2175: --- Summary: Container localization has no timeouts and tasks can be stuck there for a long time Key: YARN-2175 URL: https://issues.apache.org/jira/browse/YARN-2175

[jira] [Updated] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2175: Affects Version/s: 2.4.0 > Container localization has no timeouts and tasks can be stuck there

[jira] [Assigned] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2175: --- Assignee: Anubhav Dhoot > Container localization has no timeouts and tasks can be stuck th

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14034405#comment-14034405 ] Anubhav Dhoot commented on YARN-1367: - I am still working on it and will have it r

[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.006.patch Addressed comments. Also includes changes for no duplicate events

[jira] [Updated] (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 updated YARN-1367: Attachment: YARN-1367.001.patch Adds RESYNC_KEEPING_CONTAINERS as nodeaction that will cause NM to

[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.007.patch Addressed all comments > ApplicationMasterService to al

[jira] [Commented] (YARN-2109) TestRM fails some tests when some tests run with CapacityScheduler and some with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040448#comment-14040448 ] Anubhav Dhoot commented on YARN-2109: - Hi [~airbots] did you get a fix working

[jira] [Assigned] (YARN-2192) TestRMHA fails when run with a mix of Schedulers

[ https://issues.apache.org/jira/browse/YARN-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2192: --- Assignee: Anubhav Dhoot > TestRMHA fails when run with a mix of Schedul

[jira] [Created] (YARN-2192) TestRMHA fails when run with a mix of Schedulers

Anubhav Dhoot created YARN-2192: --- Summary: TestRMHA fails when run with a mix of Schedulers Key: YARN-2192 URL: https://issues.apache.org/jira/browse/YARN-2192 Project: Hadoop YARN Issue Type

[jira] [Updated] (YARN-2192) TestRMHA fails when run with a mix of Schedulers

[ https://issues.apache.org/jira/browse/YARN-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2192: Description: If the test is run with FairSchedulers, some of the tests fail because the

[jira] [Updated] (YARN-2192) TestRMHA fails when run with a mix of Schedulers

[ https://issues.apache.org/jira/browse/YARN-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2192: Attachment: YARN-2192.patch Fix the cleanup of the metrics by removing the conditional that would

[jira] [Updated] (YARN-2109) TestRM fails some tests when some tests run with CapacityScheduler and some with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2109: Attachment: YARN-2109.001.patch > TestRM fails some tests when some tests run w

[jira] [Updated] (YARN-2109) TestRM fails some tests when some tests run with CapacityScheduler and some with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2109: Attachment: YARN-2109.001.patch Submitting the patch > TestRM fails some tests when some tests

[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.008.patch Addressed all comments > ApplicationMasterService to al

[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-tabpanel&focusedCommentId=14041355#comment-14041355 ] Anubhav Dhoot commented on YARN-1365: - The changes for addApplication caused

[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.008.patch Without the addApplication changes. Those will be covered in YARN

[jira] [Created] (YARN-2196) Add Application duplicate APP_ACCEPTED events can be prevented with a flag

Anubhav Dhoot created YARN-2196: --- Summary: Add Application duplicate APP_ACCEPTED events can be prevented with a flag Key: YARN-2196 URL: https://issues.apache.org/jira/browse/YARN-2196 Project

[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.009.patch Without the RMAppImpl changes > ApplicationMasterService to al

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate "long lived"

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042350#comment-14042350 ] Anubhav Dhoot commented on YARN-1039: - The tokens for long lived applications jir

[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-tabpanel&focusedCommentId=14042399#comment-14042399 ] Anubhav Dhoot commented on YARN-941: Let me try to summarize the different point

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14042879#comment-14042879 ] Anubhav Dhoot commented on YARN-1367: - [~jianhe] uploading a new patch that addre

[jira] [Updated] (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 updated YARN-1367: Attachment: YARN-1367.002.patch Addressed comments > After restart NM should resync with the

[jira] [Created] (YARN-2224) Let TestContainersMonitor#testContainerKillOnMemoryOverflow work irrespective of the default settings

Anubhav Dhoot created YARN-2224: --- Summary: Let TestContainersMonitor#testContainerKillOnMemoryOverflow work irrespective of the default settings Key: YARN-2224 URL: https://issues.apache.org/jira/browse/YARN-2224

[jira] [Updated] (YARN-2224) Let TestContainersMonitor#testContainerKillOnMemoryOverflow work irrespective of the default settings

[ https://issues.apache.org/jira/browse/YARN-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2224: Attachment: YARN-2224.patch Sets the flag to be true so that the test does not fail if the default

[jira] [Updated] (YARN-2224) Let TestContainersMonitor#testContainerKillOnMemoryOverflow work irrespective of the default settings

[ https://issues.apache.org/jira/browse/YARN-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2224: Description: If the default setting DEFAULT_NM_VMEM_CHECK_ENABLED is set to false the test will

[jira] [Created] (YARN-2225) Turn the virtual memory check to be off by default

Anubhav Dhoot created YARN-2225: --- Summary: Turn the virtual memory check to be off by default Key: YARN-2225 URL: https://issues.apache.org/jira/browse/YARN-2225 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2224) Let TestContainersMonitor#testContainerKillOnMemoryOverflow work irrespective of the default settings

[ https://issues.apache.org/jira/browse/YARN-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046446#comment-14046446 ] Anubhav Dhoot commented on YARN-2224: - Once the test is made resilient, we can de

[jira] [Updated] (YARN-2225) Turn the virtual memory check to be off by default

[ https://issues.apache.org/jira/browse/YARN-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2225: Description: The virtual memory check may not be the best way to isolate applications. Virtual

[jira] [Updated] (YARN-2225) Turn the virtual memory check to be off by default

[ https://issues.apache.org/jira/browse/YARN-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2225: Attachment: YARN-2225.patch > Turn the virtual memory check to be off by defa

[jira] [Assigned] (YARN-2225) Turn the virtual memory check to be off by default

[ https://issues.apache.org/jira/browse/YARN-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2225: --- Assignee: Anubhav Dhoot > Turn the virtual memory check to be off by defa

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14048208#comment-14048208 ] Anubhav Dhoot commented on YARN-1367: - I had it that way but after discussio

[jira] [Updated] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2175: Description: There are no timeouts that can be used to limit the time taken by various container

[jira] [Updated] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2175: Description: There are no timeouts that can be used to limit the time taken by various container

[jira] [Commented] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049223#comment-14049223 ] Anubhav Dhoot commented on YARN-2175: - I should clarify the AM can kill this conta

[jira] [Moved] (YARN-2244) FairScheduler missing fixes made in other schedulers in patch MAPREDUCE-3596

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot moved MAPREDUCE-5955 to YARN-2244: Component/s: (was: scheduler) fairscheduler

[jira] [Reopened] (YARN-2244) FairScheduler missing fixes made in other schedulers in patch MAPREDUCE-3596

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reopened YARN-2244: - You resolved the bug as duplicate with itself. Reopening it. > FairScheduler missing fixes made

[jira] [Commented] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050533#comment-14050533 ] Anubhav Dhoot commented on YARN-2175: - We have seen it happen when the source

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14051769#comment-14051769 ] Anubhav Dhoot commented on YARN-1367: - I was not seeing RM shoot unknown contai

[jira] [Updated] (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 updated YARN-1367: Attachment: YARN-1367.003.patch > After restart NM should resync with the RM without kill

[jira] [Updated] (YARN-2244) FairScheduler missing fixes made in other schedulers in patch MAPREDUCE-3596

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2224.patch > FairScheduler missing fixes made in other schedulers in pa

<    1   2   3   4   5   6   7   >