[jira] [Commented] (YARN-3343) TestCapacitySchedulerNodeLabelUpdate.testNodeUpdate sometime fails in trunk

[ https://issues.apache.org/jira/browse/YARN-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527929#comment-14527929 ] Rohith commented on YARN-3343: -- [~jianhe] I was able to reproduce it. When I debug this issue,

[jira] [Updated] (YARN-3552) RM Web UI shows -1 running containers for completed apps

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3552: - Attachment: (was: 0001-YARN-3552.patch) > RM Web UI shows -1 running containers for completed apps > --

[jira] [Updated] (YARN-3552) RM Web UI shows -1 running containers for completed apps

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3552: - Attachment: 0002-YARN-3552.patch Updated the patch fixing indentation. > RM Web UI shows -1 running containers for

[jira] [Updated] (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 updated YARN-2442: - Priority: Major (was: Trivial) > ResourceManager JMX UI does not give HA State > -

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528194#comment-14528194 ] Rohith commented on YARN-3543: -- It would be good if it can be done in different JIRA since it

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: 0001-YARN-3543.patch Updated the patch fixing test failures. > ApplicationReport should be able to tel

[jira] [Commented] (YARN-2918) RM starts up fails if accessible-node-labels are configured to queue without cluster lables

[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528202#comment-14528202 ] Rohith commented on YARN-2918: -- Sure.. thank for your interest.. > RM starts up fails if acce

[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-tabpanel&focusedCommentId=14528230#comment-14528230 ] Rohith commented on YARN-2442: -- Apologies for looking back after very long time. IMHO, some c

[jira] [Updated] (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 updated YARN-2442: - Target Version/s: 2.8.0 Affects Version/s: 2.6.0 2.7.0 > ResourceManager JMX UI does no

[jira] [Commented] (YARN-2267) Auxiliary Service support in RM

[ https://issues.apache.org/jira/browse/YARN-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528248#comment-14528248 ] Rohith commented on YARN-2267: -- Thanks [~sunilg] for your views and [~zjshen] for your inputs.

[jira] [Resolved] (YARN-2267) Auxiliary Service support in RM

[ https://issues.apache.org/jira/browse/YARN-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-2267. -- Resolution: Won't Fix > Auxiliary Service support in RM > --- > > Key

[jira] [Commented] (YARN-3574) RM hangs on stopping MetricsSinkAdapter when transitioning to standby

[ https://issues.apache.org/jira/browse/YARN-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528350#comment-14528350 ] Rohith commented on YARN-3574: -- Very interesting bug!! Going back to Java basics, Thread.inte

[jira] [Commented] (YARN-3576) In Log - Container getting killed by AM even when work preserving is enabled

[ https://issues.apache.org/jira/browse/YARN-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528689#comment-14528689 ] Rohith commented on YARN-3576: -- What job and how many containers are running? If AM is killin

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: 0002-YARN-3543.patch > ApplicationReport should be able to tell whether the Application is AM > manage

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530292#comment-14530292 ] Rohith commented on YARN-3543: -- Updated the patch handling in ATS also. Kindly review the patc

[jira] [Commented] (YARN-3574) RM hangs on stopping MetricsSinkAdapter when transitioning to standby

[ https://issues.apache.org/jira/browse/YARN-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531078#comment-14531078 ] Rohith commented on YARN-3574: -- Done some more investigation on this modifying the above progr

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: 0002-YARN-3543.patch Updated the patch fixing test failure.. Kindly review the patch > ApplicationRep

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: YARN-3543-RM.PNG YARN-3543-AH.PNG > ApplicationReport should be able to tell whether th

[jira] [Updated] (YARN-2684) FairScheduler should tolerate queue configuration changes across RM restarts

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2684: - Attachment: 0002-YARN-2684.patch [~xgong] thanks for looking in the patch.. Rebased the patch and updated. Kindly r

[jira] [Created] (YARN-3589) RM and AH web UI display DOCTYPE

Rohith created YARN-3589: Summary: RM and AH web UI display DOCTYPE Key: YARN-3589 URL: https://issues.apache.org/jira/browse/YARN-3589 Project: Hadoop YARN Issue Type: Bug Components: weba

[jira] [Updated] (YARN-3589) RM and AH web UI display DOCTYPE

[ https://issues.apache.org/jira/browse/YARN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3589: - Attachment: YARN-3589.PNG > RM and AH web UI display DOCTYPE > > >

[jira] [Commented] (YARN-3589) RM and AH web UI display DOCTYPE

[ https://issues.apache.org/jira/browse/YARN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532323#comment-14532323 ] Rohith commented on YARN-3589: -- YARN-1993 escapes the content which are written with in the ht

[jira] [Updated] (YARN-3589) RM and AH web UI display DOCTYPE

[ https://issues.apache.org/jira/browse/YARN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3589: - Attachment: 0001-YARN-3589.patch Attached the patch fixing the issue. Kindly review the patch > RM and AH web UI d

[jira] [Updated] (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 updated YARN-2442: - Labels: BB2015-05-TBR (was: ) > ResourceManager JMX UI does not give HA State > --

[jira] [Updated] (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 updated YARN-2442: - Attachment: 0001-YARN-2442.patch Attached the patch without test. Verified the patch in cluster retriving HAState

[jira] [Updated] (YARN-2684) FairScheduler should tolerate queue configuration changes across RM restarts

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2684: - Labels: BB2015-05-TBR (was: ) > FairScheduler should tolerate queue configuration changes across RM restarts > ---

[jira] [Updated] (YARN-3589) RM and AH web UI display DOCTYPE

[ https://issues.apache.org/jira/browse/YARN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3589: - Labels: BB2015-05-TBR (was: ) > RM and AH web UI display DOCTYPE > > >

[jira] [Commented] (YARN-2784) Make POM project names consistent

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533869#comment-14533869 ] Rohith commented on YARN-2784: -- Hi [~jianhe], this is the change in pom.xml for project module

[jira] [Commented] (YARN-2784) Make POM project names consistent

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533871#comment-14533871 ] Rohith commented on YARN-2784: -- And this is to make sync with HDFS and Hadoop Common projects.

[jira] [Commented] (YARN-2784) Make POM project names consistent

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533882#comment-14533882 ] Rohith commented on YARN-2784: -- Failed test cases are not related to the this patch. > Make

[jira] [Updated] (YARN-2784) Make POM project names consistent

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2784: - Labels: BB2015-05-RFC (was: BB2015-05-TBR) > Make POM project names consistent > -

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533891#comment-14533891 ] Rohith commented on YARN-3543: -- Thanks Vinod for reviewing the patch. I will fix and update th

[jira] [Updated] (YARN-3476) Nodemanager can fail to delete local logs if log aggregation fails

[ https://issues.apache.org/jira/browse/YARN-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3476: - Attachment: 0002-YARN-3476.patch Updated the patch adding LOG on exception. Kindly review the updated patch > Node

[jira] [Updated] (YARN-3589) RM and AH web UI display DOCTYPE

[ https://issues.apache.org/jira/browse/YARN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3589: - Labels: BB2015-05-RFC (was: BB2015-05-TBR) > RM and AH web UI display DOCTYPE > >

[jira] [Updated] (YARN-2784) Make POM project names consistent

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2784: - Attachment: YARN-2784-branch-2.patch Updated the patch for branch-2 > Make POM project names consistent >

[jira] [Updated] (YARN-2784) Make POM project names consistent

[ 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-2784-branch-2.patch > Make POM project names consistent >

[jira] [Commented] (YARN-2784) Make POM project names consistent

[ https://issues.apache.org/jira/browse/YARN-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534181#comment-14534181 ] Rohith commented on YARN-2784: -- [~devaraj.k] thanks for the review, I updated the patch with {

[jira] [Resolved] (YARN-1432) Reduce phase is failing with shuffle error in kerberos enabled cluster

[ https://issues.apache.org/jira/browse/YARN-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-1432. -- Resolution: Not A Problem Hi [~ramgopalnaali] For the different users to run in the Kerberos set up, LinuxContai

[jira] [Commented] (YARN-1347) QueueMetrics.pendingContainers can become negative

[ https://issues.apache.org/jira/browse/YARN-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534245#comment-14534245 ] Rohith commented on YARN-1347: -- [~jlowe] Does this issue has occurring latest releases also? I

[jira] [Commented] (YARN-1263) Clean up unused imports in TestFairScheduler after YARN-899

[ https://issues.apache.org/jira/browse/YARN-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534268#comment-14534268 ] Rohith commented on YARN-1263: -- [~xgong] I see TestFairScheduler class, only 1 used import is

[jira] [Commented] (YARN-1252) Secure RM fails to start up in secure HA setup with Renewal request for unknown token exception

[ https://issues.apache.org/jira/browse/YARN-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534271#comment-14534271 ] Rohith commented on YARN-1252: -- As there no activities for long time and as per above analysis

[jira] [Resolved] (YARN-1252) Secure RM fails to start up in secure HA setup with Renewal request for unknown token exception

[ https://issues.apache.org/jira/browse/YARN-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-1252. -- Resolution: Duplicate > Secure RM fails to start up in secure HA setup with Renewal request for > unknown token

[jira] [Resolved] (YARN-1196) LocalDirsHandlerService never change failedDirs back to normal even when these disks turn good

[ https://issues.apache.org/jira/browse/YARN-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-1196. -- Resolution: Duplicate Closing as duplicate. > LocalDirsHandlerService never change failedDirs back to normal eve

[jira] [Commented] (YARN-1329) yarn-config.sh overwrites YARN_CONF_DIR indiscriminately

[ https://issues.apache.org/jira/browse/YARN-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534350#comment-14534350 ] Rohith commented on YARN-1329: -- Is the issue still exist in trunk? I don't see this in trunk.

[jira] [Commented] (YARN-306) FIFO scheduler doesn't respect changing job priority

[ https://issues.apache.org/jira/browse/YARN-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534381#comment-14534381 ] Rohith commented on YARN-306: - Linking to YARN-1963 as sub task > FIFO scheduler doesn't respec

[jira] [Assigned] (YARN-306) FIFO scheduler doesn't respect changing job priority

[ https://issues.apache.org/jira/browse/YARN-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-306: --- Assignee: Rohith > FIFO scheduler doesn't respect changing job priority > -

[jira] [Updated] (YARN-306) FIFO scheduler doesn't respect changing job priority

[ https://issues.apache.org/jira/browse/YARN-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-306: Issue Type: Sub-task (was: Bug) Parent: YARN-1963 > FIFO scheduler doesn't respect changing job priority > --

[jira] [Commented] (YARN-175) capacity scheduler web UI shows number active applications higher then actually using

[ https://issues.apache.org/jira/browse/YARN-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534391#comment-14534391 ] Rohith commented on YARN-175: - Hi [~tgraves], Do you think does this issue is still exist

[jira] [Updated] (YARN-1329) yarn-config.sh overwrites YARN_CONF_DIR indiscriminately

[ https://issues.apache.org/jira/browse/YARN-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1329: - Labels: (was: BB2015-05-TBR easyfix) > yarn-config.sh overwrites YARN_CONF_DIR indiscriminately > --

[jira] [Commented] (YARN-1209) Document applicationType is case-insensitive for submitApplication

[ https://issues.apache.org/jira/browse/YARN-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534831#comment-14534831 ] Rohith commented on YARN-1209: -- [~zjshen] Is it in REST api? Could you give some background ab

[jira] [Commented] (YARN-276) Capacity Scheduler can hang when submit many jobs concurrently

[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534835#comment-14534835 ] Rohith commented on YARN-276: - Any update on this issue? Is this problem still exists in trunk

[jira] [Commented] (YARN-172) AM logs link in RM ui redirects back to RM if AM not started

[ https://issues.apache.org/jira/browse/YARN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535035#comment-14535035 ] Rohith commented on YARN-172: - In a recent hadoop-2.7 release or in trunk , I did not face this

[jira] [Commented] (YARN-76) killApplication doesn't fully kill application master on Mac OS

[ https://issues.apache.org/jira/browse/YARN-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535046#comment-14535046 ] Rohith commented on YARN-76: [~xgong] Any update on this issue? Do you think issue is still exist

[jira] [Commented] (YARN-2684) FairScheduler: When failing an application due to changes in queue config or placement policy, indicate the cause.

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535225#comment-14535225 ] Rohith commented on YARN-2684: -- In CS, RM is brought down if queue configuration is changed. I

[jira] [Commented] (YARN-2684) FairScheduler: When failing an application due to changes in queue config or placement policy, indicate the cause.

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535328#comment-14535328 ] Rohith commented on YARN-2684: -- One scenario I am thinking for failling the RM instead of fail

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: 0003-YARN-3543.patch [~vinodkv] Tx for the review.. Updated the patch fixing all the comments. Kindly r

[jira] [Commented] (YARN-401) ClientRMService.getQueueInfo can return stale application reports

[ https://issues.apache.org/jira/browse/YARN-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536086#comment-14536086 ] Rohith commented on YARN-401: - [~jlowe] In trunk, I see that in schedulers(both CS and FS) crea

[jira] [Commented] (YARN-3614) FileSystemRMStateStore throw exception when failed to remove application, that cause resourcemanager to crash

[ https://issues.apache.org/jira/browse/YARN-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537558#comment-14537558 ] Rohith commented on YARN-3614: -- YARN-3410 try to remove the application from RMStateStore whic

[jira] [Commented] (YARN-3614) FileSystemRMStateStore throw exception when failed to remove application, that cause resourcemanager to crash

[ https://issues.apache.org/jira/browse/YARN-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537561#comment-14537561 ] Rohith commented on YARN-3614: -- [~lachisis] Would you be interest in providing patch? feel fre

[jira] [Commented] (YARN-3614) FileSystemRMStateStore throw exception when failed to remove application, that cause resourcemanager to crash

[ https://issues.apache.org/jira/browse/YARN-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537580#comment-14537580 ] Rohith commented on YARN-3614: -- Some methods does not check for existence of path like {{remo

[jira] [Resolved] (YARN-817) If input path does not exist application/job id is getting assigned.

[ https://issues.apache.org/jira/browse/YARN-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-817. - Resolution: Invalid > If input path does not exist application/job id is getting assigned. > ---

[jira] [Commented] (YARN-817) If input path does not exist application/job id is getting assigned.

[ https://issues.apache.org/jira/browse/YARN-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537817#comment-14537817 ] Rohith commented on YARN-817: - Input path is used by Application JVM. Application client should

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539069#comment-14539069 ] Rohith commented on YARN-3543: -- [~vinodkv] Kindly review the updated patch.. > ApplicationRep

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: 0003-YARN-3543.patch Updated the same patch fixing findbugs.. > ApplicationReport should be able to te

[jira] [Created] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

Rohith created YARN-3640: Summary: NodeManager JVM continues to run after SHUTDOWN event is triggered. Key: YARN-3640 URL: https://issues.apache.org/jira/browse/YARN-3640 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3640: - Attachment: nm_143.out nm_141.out Attaching the thread of 2 NM's. > NodeManager JVM continues to

[jira] [Updated] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3640: - Attachment: hadoop-rohith-nodemanager-test123.log Attached the nodemanager log file. It contains log from stopping

[jira] [Commented] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541742#comment-14541742 ] Rohith commented on YARN-3640: -- It looks similar, but I did not get how did you taken *jni lev

[jira] [Commented] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541743#comment-14541743 ] Rohith commented on YARN-3640: -- I missed this issue, thanks for pointing out. > NodeManager

[jira] [Resolved] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-3640. -- Resolution: Duplicate Closing as duplicate. > NodeManager JVM continues to run after SHUTDOWN event is triggered

[jira] [Commented] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541790#comment-14541790 ] Rohith commented on YARN-3640: -- I am able to reproduce this always..!!! > NodeManager JVM con

[jira] [Commented] (YARN-3585) Nodemanager cannot exit when decommission with NM recovery enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542857#comment-14542857 ] Rohith commented on YARN-3585: -- bq. Could you check the NM logs for the case where it hung and

[jira] [Commented] (YARN-3585) Nodemanager cannot exit when decommission with NM recovery enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542858#comment-14542858 ] Rohith commented on YARN-3585: -- I am able to reproduce it always, testing of any patch I will

[jira] [Updated] (YARN-3585) NodeManager cannot exit on SHUTDOWN event triggered and NM recovery is enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3585: - Summary: NodeManager cannot exit on SHUTDOWN event triggered and NM recovery is enabled (was: Nodemanager cannot e

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543198#comment-14543198 ] Rohith commented on YARN-3641: -- Apologies for coming late into this JIRA.. I think {{DefaultM

[jira] [Commented] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543551#comment-14543551 ] Rohith commented on YARN-3642: -- I think this is related to /etc/hosts mapping. Does /etc/hosts

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543739#comment-14543739 ] Rohith commented on YARN-3641: -- bq. so we probably should still call ExitUtil.terminate. I thi

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543776#comment-14543776 ] Rohith commented on YARN-3646: -- Which version of Hadoop are you using? I don't see this proble

[jira] [Commented] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544920#comment-14544920 ] Rohith commented on YARN-3642: -- How many nodemanagers are running? If it more than 1 then I am

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544938#comment-14544938 ] Rohith commented on YARN-3646: -- Thanks for the explanation.. I got the problem in my machines

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544947#comment-14544947 ] Rohith commented on YARN-3646: -- RetryPolicies.RETRY_FOREVER should also should use exceptionTo

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544959#comment-14544959 ] Rohith commented on YARN-3646: -- I was copied *yarn.resourcemanager.connect.wait-ms* from descr

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544988#comment-14544988 ] Rohith commented on YARN-3646: -- Setting RetryPolicies.RETRY_FOREVER for exceptionToPolicyMap a

[jira] [Resolved] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-3642. -- Resolution: Invalid Closing as Invalid. If there is any queries or basic environment problems , I suggest to use

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545916#comment-14545916 ] Rohith commented on YARN-3543: -- Need to kick off jenkins again to check test failure are regul

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546560#comment-14546560 ] Rohith commented on YARN-3543: -- bq. ApplicationReport.newInstance() is Private, so you should

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546562#comment-14546562 ] Rohith commented on YARN-3543: -- bq. But doesn't impact compatibility? I meant to say Applicati

[jira] [Commented] (YARN-3674) YARN application disappears from view

[ https://issues.apache.org/jira/browse/YARN-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549928#comment-14549928 ] Rohith commented on YARN-3674: -- Is this dup of YARN-2238? > YARN application disappears from

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550233#comment-14550233 ] Rohith commented on YARN-3646: -- bq. Seems we do not even require exceptionToPolicy for FOREVER

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550256#comment-14550256 ] Rohith commented on YARN-3646: -- Thanks for working on this issue.. The patch overall looks goo

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550258#comment-14550258 ] Rohith commented on YARN-3646: -- And I verified in one node cluster by enabling and disabling r

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: 0004-YARN-3543.patch > ApplicationReport should be able to tell whether the Application is AM > manage

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550854#comment-14550854 ] Rohith commented on YARN-3543: -- About the -1's from QA, # Findbugs is YARN-3677 exists to tra

[jira] [Commented] (YARN-2268) Disallow formatting the RMStateStore when there is an RM running

[ https://issues.apache.org/jira/browse/YARN-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551826#comment-14551826 ] Rohith commented on YARN-2268: -- Thanks [~sunilg] [~jianhe] [~kasha] for sharing your thoughts.

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: (was: 0003-YARN-3543.patch) > ApplicationReport should be able to tell whether the Application is A

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3543: - Attachment: 0004-YARN-3543.patch Attached same patch to kick off Jenkins > ApplicationReport should be able to tel

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552091#comment-14552091 ] Rohith commented on YARN-3646: -- Thanks for updating the patch, some comments on tests # I thi

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552165#comment-14552165 ] Rohith commented on YARN-3543: -- Build machine is not able to run all those test at one shot. S

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552225#comment-14552225 ] Rohith commented on YARN-3646: -- +1 lgtm (non-binding).. wait for jenkins report!! > Applicat

[jira] [Assigned] (YARN-3692) Allow REST API to set a user generated message when killing an application

[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-3692: Assignee: Rohith > Allow REST API to set a user generated message when killing an application >

  1   2   3   4   5   6   7   8   9   10   >