[jira] [Commented] (YARN-2784) Yarn project module names in POM needs to consistent acros hadoop project

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194366#comment-14194366 ] Rohith commented on YARN-2784: -- There so many Random test failures in Yarn/MR projects!!

[jira] [Created] (YARN-2784) Yarn project module names in POM needs to consitent acros hadoop project

Rohith created YARN-2784: Summary: Yarn project module names in POM needs to consitent acros hadoop project Key: YARN-2784 URL: https://issues.apache.org/jira/browse/YARN-2784 Project: Hadoop YARN

[jira] [Updated] (YARN-2784) Yarn project module names in POM needs to consistent acros hadoop project

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2784: - Summary: Yarn project module names in POM needs to consistent acros hadoop project (was: Yarn project module

[jira] [Commented] (YARN-2784) Yarn project module names in POM needs to consistent acros hadoop project

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191511#comment-14191511 ] Rohith commented on YARN-2784: -- In the build, project name are as follows. These can be made

[jira] [Updated] (YARN-2784) Yarn project module names in POM needs to consistent acros hadoop project

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2784: - Attachment: YARN-2784.patch Yarn project module names in POM needs to consistent acros hadoop project

[jira] [Commented] (YARN-2784) Yarn project module names in POM needs to consistent acros hadoop project

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192007#comment-14192007 ] Rohith commented on YARN-2784: -- Attached patch changed as follows. {code} [INFO] Apache Hadoop

[jira] [Commented] (YARN-2784) Yarn project module names in POM needs to consistent acros hadoop project

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192011#comment-14192011 ] Rohith commented on YARN-2784: -- Please review the patch. Yarn project module names in POM

[jira] [Updated] (YARN-2762) Provide RMAdminCLI args validation for NodeLabelManager operations

[ https://issues.apache.org/jira/browse/YARN-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2762: - Issue Type: Sub-task (was: Improvement) Parent: YARN-2492 Provide RMAdminCLI args validation for

[jira] [Commented] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189583#comment-14189583 ] Rohith commented on YARN-2579: -- Thanks Karthink!! bq. (Service)Dispatcher.stop() wait for

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189600#comment-14189600 ] Rohith commented on YARN-2588: -- bq. but I would like for us to call transitionToStandby in the

[jira] [Updated] (YARN-2762) Provide RMAdminCLI args validation for NodeLabelManager operations

[ https://issues.apache.org/jira/browse/YARN-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2762: - Attachment: YARN-2762.patch Provide RMAdminCLI args validation for NodeLabelManager operations

[jira] [Commented] (YARN-2762) Provide RMAdminCLI args validation for NodeLabelManager operations

[ https://issues.apache.org/jira/browse/YARN-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186617#comment-14186617 ] Rohith commented on YARN-2762: -- Added sanity check at client that validate the arguments.

[jira] [Commented] (YARN-1813) Better error message for yarn logs when permission denied

[ https://issues.apache.org/jira/browse/YARN-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186688#comment-14186688 ] Rohith commented on YARN-1813: -- Thanks Tshuyosh for rebasing patch!! Some minor comments 1. I

[jira] [Commented] (YARN-2601) RMs(HA RMS) can't enter active state

[ https://issues.apache.org/jira/browse/YARN-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186695#comment-14186695 ] Rohith commented on YARN-2601: -- [~cindy2012] This will be fixing in YARN-2010. Please follow

[jira] [Commented] (YARN-2762) Provide RMAdminCLI args validation for NodeLabelManager operations

[ https://issues.apache.org/jira/browse/YARN-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186703#comment-14186703 ] Rohith commented on YARN-2762: -- test case falures are not related to this fix. Provide

[jira] [Assigned] (YARN-2737) Misleading msg in LogCLI when app is not successfully submitted

[ https://issues.apache.org/jira/browse/YARN-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-2737: Assignee: Rohith Misleading msg in LogCLI when app is not successfully submitted

[jira] [Created] (YARN-2762) Provide RMAdminCLI args validation for NodeLabelManager operations

Rohith created YARN-2762: Summary: Provide RMAdminCLI args validation for NodeLabelManager operations Key: YARN-2762 URL: https://issues.apache.org/jira/browse/YARN-2762 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2737) Misleading msg in LogCLI when app is not successfully submitted

[ https://issues.apache.org/jira/browse/YARN-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14186366#comment-14186366 ] Rohith commented on YARN-2737: -- One way is print all possible reasons that can cause this

[jira] [Updated] (YARN-2691) User level API support for priority label

[ https://issues.apache.org/jira/browse/YARN-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2691: - Attachment: YARN-2691.patch User level API support for priority label -

[jira] [Commented] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177886#comment-14177886 ] Rohith commented on YARN-2579: -- bq. Under what conditions, can resetDispatcher be called by

[jira] [Commented] (YARN-2398) TestResourceTrackerOnHA crashes

[ https://issues.apache.org/jira/browse/YARN-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14174943#comment-14174943 ] Rohith commented on YARN-2398: -- [~ozawa] The attached log and reported issue both are

[jira] [Resolved] (YARN-2702) TestResourceTrackerOnHA fails with NPE

[ https://issues.apache.org/jira/browse/YARN-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-2702. -- Resolution: Duplicate ok TestResourceTrackerOnHA fails with NPE --

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175329#comment-14175329 ] Rohith commented on YARN-2588: -- Thanks 'Jian He' for review and committing patch:-) Standby

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14174673#comment-14174673 ] Rohith commented on YARN-2588: -- In RMWebApp, we have code below where ApplicationACLManager

[jira] [Updated] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2588: - Attachment: YARN-2588.2.patch Standby RM does not transitionToActive if previous transitionToActive is failed

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14174748#comment-14174748 ] Rohith commented on YARN-2588: -- bq. But anyways, this doesn't matter too much? as these two

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14174749#comment-14174749 ] Rohith commented on YARN-2588: -- bq. add Assert.fail() after

[jira] [Updated] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2588: - Attachment: YARN-2588.1.patch Standby RM does not transitionToActive if previous transitionToActive is failed

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172284#comment-14172284 ] Rohith commented on YARN-2588: -- I updated the patch with above changes.Please review Standby

[jira] [Updated] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2579: - Attachment: YARN-2579.patch Both RM's state is Active , but 1 RM is not really active.

[jira] [Commented] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172369#comment-14172369 ] Rohith commented on YARN-2579: -- I updated the patch with test that simulates

[jira] [Commented] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173273#comment-14173273 ] Rohith commented on YARN-2579: -- Hi [~vinodkv], [~kasha], [~jianhe] Can this issue fix

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170587#comment-14170587 ] Rohith commented on YARN-2588: -- Hi [~jianhe] , could you please review the patch whenever you

[jira] [Commented] (YARN-2655) AllocatedGB/AvailableGB in nodemanager JMX showing only integer values

[ https://issues.apache.org/jira/browse/YARN-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14164679#comment-14164679 ] Rohith commented on YARN-2655: -- Keeping values in MB's is good approach that make consistency

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14164692#comment-14164692 ] Rohith commented on YARN-2010: -- Changing assignee to [~kasha] since he has done all the work.

[jira] [Assigned] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-2010: Assignee: Karthik Kambatla (was: Rohith) RM can't transition to active if it can't recover an app attempt

[jira] [Updated] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2579: - Attachment: YARN-2579.patch Both RM's state is Active , but 1 RM is not really active.

[jira] [Commented] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161774#comment-14161774 ] Rohith commented on YARN-2579: -- Considering 1 st approach as feasible, I attached patch.

[jira] [Commented] (YARN-2625) Problems with CLASSPATH in Job Submission REST API

[ https://issues.apache.org/jira/browse/YARN-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160170#comment-14160170 ] Rohith commented on YARN-2625: -- While submitting appliclaiton from REST api, it expects

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148636#comment-14148636 ] Rohith commented on YARN-2523: -- Thanks [~jianhe] and [~jlowe] for review and committing

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146083#comment-14146083 ] Rohith commented on YARN-2523: -- Thank you Jason Lowe for your suggestion. Considering your

[jira] [Updated] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2523: - Attachment: YARN-2523.1.patch Updated the patch for handling tests mentioned in my previous comment. Please

[jira] [Updated] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2588: - Attachment: YARN-2588.patch Updated the patch for fixing issue. Please review.. Standby RM does not

[jira] [Commented] (YARN-2601) RMs(HA RMS) can't enter active state

[ https://issues.apache.org/jira/browse/YARN-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147308#comment-14147308 ] Rohith commented on YARN-2601: -- Hi [~cindy2012], This looks to be similar of YARN-2588. In

[jira] [Commented] (YARN-2349) InvalidStateTransitonException after RM switch

[ https://issues.apache.org/jira/browse/YARN-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147325#comment-14147325 ] Rohith commented on YARN-2349: -- Hi [~nishan], would you confirm that this issue you are still

[jira] [Commented] (YARN-1703) Too many connections are opened for proxy server when applicationMaster UI is accessed.

[ https://issues.apache.org/jira/browse/YARN-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147329#comment-14147329 ] Rohith commented on YARN-1703: -- Hi all, Could anyone review the patch please? Too many

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147369#comment-14147369 ] Rohith commented on YARN-2523: -- Thanks Jian He for looking into patch. I will relook into test

[jira] [Assigned] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-2579: Assignee: Rohith Both RM's state is Active , but 1 RM is not really active.

[jira] [Commented] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144550#comment-14144550 ] Rohith commented on YARN-2579: -- For fixing this, approaches I can think of are 1. we can call

[jira] [Created] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

Rohith created YARN-2588: Summary: Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception. Key: YARN-2588 URL: https://issues.apache.org/jira/browse/YARN-2588

[jira] [Assigned] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-2588: Assignee: Rohith Standby RM does not transitionToActive if previous transitionToActive is failed with ZK

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144604#comment-14144604 ] Rohith commented on YARN-2588: -- Consider RM initially in standby. 1. StandBy RM 2. StandBy

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144612#comment-14144612 ] Rohith commented on YARN-2588: -- This is basically problem in not recreating active services if

[jira] [Commented] (YARN-2588) Standby RM does not transitionToActive if previous transitionToActive is failed with ZK exception.

[ https://issues.apache.org/jira/browse/YARN-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14145822#comment-14145822 ] Rohith commented on YARN-2588: -- [~cindy2012] RM zkClient got session expired. Immediately

[jira] [Created] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

Rohith created YARN-2579: Summary: Both RM's state is Active , but 1 RM is not really active. Key: YARN-2579 URL: https://issues.apache.org/jira/browse/YARN-2579 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-2579) Both RM's state is Active , but 1 RM is not really active.

[ https://issues.apache.org/jira/browse/YARN-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14143200#comment-14143200 ] Rohith commented on YARN-2579: -- This scenario could ocure if 2 thread trying to access

[jira] [Updated] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2523: - Attachment: YARN-2523.patch uploaded patch to fix this issue. Test details : 1. Recured using test, and applied

[jira] [Updated] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2523: - Attachment: YARN-2523.patch Verified the fix again, decommissioned nodes should not be decremented again

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14132688#comment-14132688 ] Rohith commented on YARN-2523: -- Attached udpated patch. Please review ResourceManager UI

[jira] [Created] (YARN-2550) TestAMRestart fails intermittently

Rohith created YARN-2550: Summary: TestAMRestart fails intermittently Key: YARN-2550 URL: https://issues.apache.org/jira/browse/YARN-2550 Project: Hadoop YARN Issue Type: Bug Components:

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14132773#comment-14132773 ] Rohith commented on YARN-2523: -- Test failure checked, it is not related to fix. I raised new

[jira] [Assigned] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-2523: Assignee: Rohith ResourceManager UI showing negative value for Decommissioned Nodes field

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126580#comment-14126580 ] Rohith commented on YARN-2523: -- Decommissioned Node metrics are set by NodeListManager. If

[jira] [Assigned] (YARN-2442) ResourceManager JMX UI does not give HA State

[ https://issues.apache.org/jira/browse/YARN-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-2442: Assignee: Rohith ResourceManager JMX UI does not give HA State

[jira] [Commented] (YARN-2442) ResourceManager JMX UI does not give HA State

[ https://issues.apache.org/jira/browse/YARN-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112134#comment-14112134 ] Rohith commented on YARN-2442: -- This can be taken as Improvement, not really a bug. In

[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=14105276#comment-14105276 ] Rohith commented on YARN-1879: -- Hi, Any update on this issue? Mark Idempotent/AtMostOnce

[jira] [Commented] (YARN-2409) Active to StandBy transition does not stop rmDispatcher that causes 1 AsyncDispatcher thread leak.

[ https://issues.apache.org/jira/browse/YARN-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103382#comment-14103382 ] Rohith commented on YARN-2409: -- Thanks [~eepayne] and [~jianhe] for review.:-) Active to

[jira] [Assigned] (YARN-2409) InvalidStateTransitonException in ResourceManager after job recovery

[ https://issues.apache.org/jira/browse/YARN-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-2409: Assignee: Rohith InvalidStateTransitonException in ResourceManager after job recovery

[jira] [Commented] (YARN-2409) InvalidStateTransitonException in ResourceManager after job recovery

[ https://issues.apache.org/jira/browse/YARN-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14095466#comment-14095466 ] Rohith commented on YARN-2409: -- I looked into issue (got logs from [~nishan] offline), there

[jira] [Updated] (YARN-2409) InvalidStateTransitonException in ResourceManager after job recovery

[ https://issues.apache.org/jira/browse/YARN-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2409: - Attachment: YARN-2409.patch Attached the patch. Please review.. I have verified patch for 1. Thread Leak :

[jira] [Updated] (YARN-2409) InvalidStateTransitonException in ResourceManager after job recovery

[ https://issues.apache.org/jira/browse/YARN-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2409: - Attachment: (was: YARN-2409.patch) InvalidStateTransitonException in ResourceManager after job recovery

[jira] [Updated] (YARN-2409) InvalidStateTransitonException in ResourceManager after job recovery

[ https://issues.apache.org/jira/browse/YARN-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2409: - Attachment: YARN-2409.patch InvalidStateTransitonException in ResourceManager after job recovery

[jira] [Updated] (YARN-2409) Active to StandBy transition does not stop rmDispatcher that causes 1 AsyncDispatcher thread leak.

[ https://issues.apache.org/jira/browse/YARN-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2409: - Priority: Critical (was: Major) Active to StandBy transition does not stop rmDispatcher that causes 1

[jira] [Updated] (YARN-2409) Active to StandBy transition does not stop rmDispatcher that causes 1 AsyncDispatcher thread leak.

[ https://issues.apache.org/jira/browse/YARN-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2409: - Summary: Active to StandBy transition does not stop rmDispatcher that causes 1 AsyncDispatcher thread leak.

[jira] [Commented] (YARN-2209) Replace AM resync/shutdown command with corresponding exceptions

[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075973#comment-14075973 ] Rohith commented on YARN-2209: -- +1 patch looks good to me Replace AM resync/shutdown command

[jira] [Commented] (YARN-2209) Replace allocate#resync command with ApplicationMasterNotRegisteredException to indicate AM to re-register on RM restart

[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075877#comment-14075877 ] Rohith commented on YARN-2209: -- Thanks Jian He for updating patch. It looks good overall to

[jira] [Commented] (YARN-2209) Replace allocate#resync command with ApplicationMasterNotRegisteredException to indicate AM to re-register on RM restart

[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074366#comment-14074366 ] Rohith commented on YARN-2209: -- Hi [~jianhe], I reviewed patch and found some comments 1.

[jira] [Commented] (YARN-2349) InvalidStateTransitonException after RM switch

[ https://issues.apache.org/jira/browse/YARN-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073158#comment-14073158 ] Rohith commented on YARN-2349: -- This is basically configurations in capacity-scheduler.xml of

[jira] [Assigned] (YARN-2349) InvalidStateTransitonException after RM switch

[ https://issues.apache.org/jira/browse/YARN-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-2349: Assignee: Rohith InvalidStateTransitonException after RM switch

[jira] [Commented] (YARN-2350) TestApplicationMasterServiceOnHA fails with InvalidToken exception

[ https://issues.apache.org/jira/browse/YARN-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073973#comment-14073973 ] Rohith commented on YARN-2350: -- This issue is because of YARN-2208 check in. As a wholse

[jira] [Commented] (YARN-1779) Handle AMRMTokens across RM failover

[ https://issues.apache.org/jira/browse/YARN-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071772#comment-14071772 ] Rohith commented on YARN-1779: -- This is critical issue for work preserving restart feature. AM

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.13.patch Thanks Jian He and Bikas Saha for reviewing patch. I updated patch with

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.12.patch Updating patch with below changes. 1. Making second allocate() call on resync

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14051013#comment-14051013 ] Rohith commented on YARN-1366: -- bq. can you add some documentation about this Shall I add in

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049563#comment-14049563 ] Rohith commented on YARN-1366: -- bq. These two synchronized block can be merged into one ?

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.10.patch I updated the patch with addressing comments. Please review.. AM should

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.11.patch Updated patch fix findbug warning. AM should implement Resync with the

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047412#comment-14047412 ] Rohith commented on YARN-1366: -- Thank you for reviewing patch. I will update patch soon. One

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.8.patch I updated the patch addressing comments. bq. isApplicationMasterRegistered is

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.9.patch Thank for reviewing patch.. I updated patch as per comments. Please review update

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: (was: YARN-1366.9.patch) AM should implement Resync with the ApplicationMasterService instead of

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.9.patch Update patch for test cases correction AM should implement Resync with the

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.7.patch AM should implement Resync with the ApplicationMasterService instead of shutting

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14046826#comment-14046826 ] Rohith commented on YARN-1366: -- Looking into fix findbug warning and test case. Will update

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.6.patch Attached updated the patch. Please review the patch AM should implement Resync

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.5.patch I updated the patch for following incremental change. 1. Reregister for AmRMClient

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043059#comment-14043059 ] Rohith commented on YARN-1366: -- Thank you [~jianhe] for looking into patch :-) In current

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013607#comment-14013607 ] Rohith commented on YARN-1366: -- Let this jira keep only for Yarn Client. I created

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.4.patch Attached updated patch that address Anubhav's all comments. This patch contains

[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=14013256#comment-14013256 ] Rohith commented on YARN-1366: -- Hi [~vinodkv], I agree that both issues title looks

<    3   4   5   6   7   8   9   >