[jira] [Commented] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

[ https://issues.apache.org/jira/browse/YARN-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213295#comment-14213295 ] Jian He commented on YARN-2865: --- make sense, thanks for your explanation ! will review the pa

[jira] [Updated] (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:all-tabpanel ] Rohith updated YARN-1703: - Fix Version/s: 2.7.0 > Too many connections are opened for proxy server when applicationMaster UI is > accessed. >

[jira] [Commented] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

[ https://issues.apache.org/jira/browse/YARN-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213289#comment-14213289 ] Rohith commented on YARN-2865: -- bq. why does the rmContext still contain the application?If th

[jira] [Commented] (YARN-2414) RM web UI: app page will crash if app is failed before any attempt has been created

[ https://issues.apache.org/jira/browse/YARN-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213265#comment-14213265 ] Hadoop QA commented on YARN-2414: - {color:green}+1 overall{color}. Here are the results of

[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=14213255#comment-14213255 ] Hadoop QA commented on YARN-2675: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2432) RMStateStore should process the pending events before close

[ https://issues.apache.org/jira/browse/YARN-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213253#comment-14213253 ] Hudson commented on YARN-2432: -- FAILURE: Integrated in Hadoop-trunk-Commit #6553 (See [https:

[jira] [Commented] (YARN-2432) RMStateStore should process the pending events before close

[ https://issues.apache.org/jira/browse/YARN-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213222#comment-14213222 ] Hadoop QA commented on YARN-2432: - {color:red}-1 overall{color}. Here are the results of t

[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=14213207#comment-14213207 ] zhihai xu commented on YARN-2675: - Hi [~adhoot], Good suggestion. I uploaded a new patch Y

[jira] [Updated] (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:all-tabpanel ] zhihai xu updated YARN-2675: Attachment: YARN-2675.002.patch > the containersKilled metrics is not updated when the container is killed >

[jira] [Updated] (YARN-2414) RM web UI: app page will crash if app is failed before any attempt has been created

[ https://issues.apache.org/jira/browse/YARN-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2414: - Attachment: YARN-2414.20141104-2.patch Fixed release audit warnings. > RM web UI: app page will crash if a

[jira] [Commented] (YARN-2414) RM web UI: app page will crash if app is failed before any attempt has been created

[ https://issues.apache.org/jira/browse/YARN-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213151#comment-14213151 ] Hadoop QA commented on YARN-2414: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2816) NM fail to start with NPE during container recovery

[ https://issues.apache.org/jira/browse/YARN-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213133#comment-14213133 ] zhihai xu commented on YARN-2816: - thanks [~jlowe] for the review and commit. > NM fail to

[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 may be good

[jira] [Commented] (YARN-2869) CapacityScheduler should trim sub queue names when parse configuration

[ https://issues.apache.org/jira/browse/YARN-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213092#comment-14213092 ] Hadoop QA commented on YARN-2869: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2432) RMStateStore should process the pending events before close

[ https://issues.apache.org/jira/browse/YARN-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213090#comment-14213090 ] Hadoop QA commented on YARN-2432: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2811) In Fair Scheduler, reservation fulfillments shouldn't ignore max share

[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213066#comment-14213066 ] Hudson commented on YARN-2811: -- FAILURE: Integrated in Hadoop-trunk-Commit #6550 (See [https:

[jira] [Updated] (YARN-2869) CapacityScheduler should trim sub queue names when parse configuration

[ https://issues.apache.org/jira/browse/YARN-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2869: - Attachment: YARN-2869-1.patch Attached a fix for this issue. > CapacityScheduler should trim sub queue nam

[jira] [Created] (YARN-2869) CapacityScheduler should trim sub queue names when parse configuration

Wangda Tan created YARN-2869: Summary: CapacityScheduler should trim sub queue names when parse configuration Key: YARN-2869 URL: https://issues.apache.org/jira/browse/YARN-2869 Project: Hadoop YARN

[jira] [Updated] (YARN-2811) In Fair Scheduler, reservation fulfillments shouldn't ignore max share

[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-2811: - Summary: In Fair Scheduler, reservation fulfillments shouldn't ignore max share (was: Fair Scheduler is vi

[jira] [Commented] (YARN-2811) Fair Scheduler is violating max memory settings in 2.4

[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213045#comment-14213045 ] Sandy Ryza commented on YARN-2811: -- +1 > Fair Scheduler is violating max memory settings

[jira] [Commented] (YARN-2811) Fair Scheduler is violating max memory settings in 2.4

[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213036#comment-14213036 ] Siqi Li commented on YARN-2811: --- I have changed Resources.lessThanOrEqual to Resources.fitsIn

[jira] [Updated] (YARN-2414) RM web UI: app page will crash if app is failed before any attempt has been created

[ https://issues.apache.org/jira/browse/YARN-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2414: - Attachment: YARN-2414.20141104-1.patch Attached patch addressed [~jlowe]'s comment, added a test with mock

[jira] [Resolved] (YARN-2867) TimelineClient DT methods should check if the timeline service is enabled or not

[ https://issues.apache.org/jira/browse/YARN-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-2867. --- Resolution: Invalid Per discussion on [YARN-2375|https://issues.apache.org/jira/browse/YARN-2375?focus

[jira] [Commented] (YARN-2375) Allow enabling/disabling timeline server per framework

[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213002#comment-14213002 ] Zhijie Shen commented on YARN-2375: --- [~jeagles], thanks for the clarification. bq. I am

[jira] [Commented] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

[ https://issues.apache.org/jira/browse/YARN-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213001#comment-14213001 ] Hadoop QA commented on YARN-2865: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213006#comment-14213006 ] chang li commented on YARN-2556: I have run those failed tests on my local machine and they

[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=14212992#comment-14212992 ] zhihai xu commented on YARN-2802: - Hi [~jianhe] and [~vinodkv], Could you review the patch

[jira] [Commented] (YARN-2392) add more diags about app retry limits on AM failures

[ https://issues.apache.org/jira/browse/YARN-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212991#comment-14212991 ] Hadoop QA commented on YARN-2392: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2862) RM might not start if the machine was hard shutdown and FileSystemRMStateStore was used

[ https://issues.apache.org/jira/browse/YARN-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212989#comment-14212989 ] Zhijie Shen commented on YARN-2862: --- It is likely that the assumption we made in [YARN-1

[jira] [Commented] (YARN-2432) RMStateStore should process the pending events before close

[ https://issues.apache.org/jira/browse/YARN-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212984#comment-14212984 ] Hadoop QA commented on YARN-2432: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2432) RMStateStore should process the pending events before close

[ https://issues.apache.org/jira/browse/YARN-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212974#comment-14212974 ] Jian He commented on YARN-2432: --- looks good, kick jenkins manually > RMStateStore should pro

[jira] [Commented] (YARN-2392) add more diags about app retry limits on AM failures

[ https://issues.apache.org/jira/browse/YARN-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212970#comment-14212970 ] Jian He commented on YARN-2392: --- thanks Steve, patch not applying anymore, mind updating the

[jira] [Commented] (YARN-2375) Allow enabling/disabling timeline server per framework

[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212964#comment-14212964 ] Jonathan Eagles commented on YARN-2375: --- [~zjshen], you misunderstand my request. I a

[jira] [Commented] (YARN-2403) TestNodeManagerResync fails occasionally in trunk

[ https://issues.apache.org/jira/browse/YARN-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212961#comment-14212961 ] Hadoop QA commented on YARN-2403: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2396) RpcClientFactoryPBImpl.stopClient always throws due to missing close method

[ https://issues.apache.org/jira/browse/YARN-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212952#comment-14212952 ] Hadoop QA commented on YARN-2396: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2375) Allow enabling/disabling timeline server per framework

[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212951#comment-14212951 ] Mit Desai commented on YARN-2375: - And if the flag is turned off in yarn-site, DT API will

[jira] [Commented] (YARN-2811) Fair Scheduler is violating max memory settings in 2.4

[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212949#comment-14212949 ] Hadoop QA commented on YARN-2811: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2396) RpcClientFactoryPBImpl.stopClient always throws due to missing close method

[ https://issues.apache.org/jira/browse/YARN-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212948#comment-14212948 ] Jian He commented on YARN-2396: --- The protocol PB implementation actually has the close method

[jira] [Commented] (YARN-2375) Allow enabling/disabling timeline server per framework

[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212947#comment-14212947 ] Mit Desai commented on YARN-2375: - bq. DT related API methods doesn't check if isEnabled ==

[jira] [Commented] (YARN-2056) Disable preemption at Queue level

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212944#comment-14212944 ] Hadoop QA commented on YARN-2056: - {color:green}+1 overall{color}. Here are the results of

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

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-2868: - Attachment: YARN-2868-01.patch First attempt at implementation. Second upload. > Add metric for initial c

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

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-2868: - Attachment: (was: 20141114_FSQueueAllocationMetric-Up-04.patch) > Add metric for initial container laun

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

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-2868: - Attachment: 20141114_FSQueueAllocationMetric-Up-04.patch First attempt at implementation. > Add metric for

[jira] [Resolved] (YARN-2603) ApplicationConstants missing HADOOP_MAPRED_HOME

[ https://issues.apache.org/jira/browse/YARN-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-2603. --- Resolution: Invalid Thanks for the response Ray. Closing this as invalid. Repea

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

Ray Chiang created YARN-2868: Summary: Add metric for initial container launch time Key: YARN-2868 URL: https://issues.apache.org/jira/browse/YARN-2868 Project: Hadoop YARN Issue Type: Improvemen

[jira] [Commented] (YARN-2862) RM might not start if the machine was hard shutdown and FileSystemRMStateStore was used

[ https://issues.apache.org/jira/browse/YARN-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212935#comment-14212935 ] Gera Shegalov commented on YARN-2862: - [~jianhe], to add more details: we use 2.4+patch

[jira] [Commented] (YARN-2403) TestNodeManagerResync fails occasionally in trunk

[ https://issues.apache.org/jira/browse/YARN-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212934#comment-14212934 ] Jian He commented on YARN-2403: --- is this still happening? otherwise we can close this. if it'

[jira] [Commented] (YARN-2375) Allow enabling/disabling timeline server per framework

[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212932#comment-14212932 ] Zhijie Shen commented on YARN-2375: --- Filed YARN-2867 > Allow enabling/disabling timeline

[jira] [Created] (YARN-2867) TimelineClient DT methods should check if the timeline service is enabled or not

Zhijie Shen created YARN-2867: - Summary: TimelineClient DT methods should check if the timeline service is enabled or not Key: YARN-2867 URL: https://issues.apache.org/jira/browse/YARN-2867 Project: Hadoo

[jira] [Updated] (YARN-2404) Remove ApplicationAttemptState and ApplicationState class in RMStateStore class

[ https://issues.apache.org/jira/browse/YARN-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2404: -- Target Version/s: 2.7.0 > Remove ApplicationAttemptState and ApplicationState class in RMStateStore > class > -

[jira] [Commented] (YARN-2375) Allow enabling/disabling timeline server per framework

[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212928#comment-14212928 ] Zhijie Shen commented on YARN-2375: --- bq. While running secure timeline server with ats fl

[jira] [Updated] (YARN-2414) RM web UI: app page will crash if app is failed before any attempt has been created

[ https://issues.apache.org/jira/browse/YARN-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2414: -- Target Version/s: 2.7.0 > RM web UI: app page will crash if app is failed before any attempt has been > created

[jira] [Updated] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

[ https://issues.apache.org/jira/browse/YARN-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2865: -- Priority: Critical (was: Major) Target Version/s: 2.7.0 > Application recovery continuously fails wi

[jira] [Commented] (YARN-2056) Disable preemption at Queue level

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212899#comment-14212899 ] Wangda Tan commented on YARN-2056: -- [~eepayne], Thanks for update, bq. Would you please

[jira] [Commented] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

[ https://issues.apache.org/jira/browse/YARN-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212898#comment-14212898 ] Jian He commented on YARN-2865: --- hi Rohith, one question, why does the rmContext still contai

[jira] [Created] (YARN-2866) Capacity scheduler preemption policy should respect yarn.scheduler.minimum-allocation-mb when computing resource of queues

Wangda Tan created YARN-2866: Summary: Capacity scheduler preemption policy should respect yarn.scheduler.minimum-allocation-mb when computing resource of queues Key: YARN-2866 URL: https://issues.apache.org/jira/brow

[jira] [Updated] (YARN-2811) Fair Scheduler is violating max memory settings in 2.4

[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2811: -- Attachment: YARN-2811.v9.patch > Fair Scheduler is violating max memory settings in 2.4 > ---

[jira] [Updated] (YARN-2375) Allow enabling/disabling timeline server per framework

[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-2375: -- Description: This JIRA is to remove the ats enabled flag check within the TimelineClientImpl. Ex

[jira] [Commented] (YARN-2816) NM fail to start with NPE during container recovery

[ https://issues.apache.org/jira/browse/YARN-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212860#comment-14212860 ] Hudson commented on YARN-2816: -- FAILURE: Integrated in Hadoop-trunk-Commit #6549 (See [https:

[jira] [Commented] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

[ https://issues.apache.org/jira/browse/YARN-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212845#comment-14212845 ] Rohith commented on YARN-2865: -- Attaching the patch that clears rmcontext,cluster metric and q

[jira] [Updated] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

[ https://issues.apache.org/jira/browse/YARN-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-2865: - Attachment: YARN-2865.patch > Application recovery continuously fails with "Application with id already > present.

[jira] [Commented] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

[ https://issues.apache.org/jira/browse/YARN-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212842#comment-14212842 ] Rohith commented on YARN-2865: -- I encountered this scenario in my test cluster strange way!! c

[jira] [Commented] (YARN-2862) RM might not start if the machine was hard shutdown and FileSystemRMStateStore was used

[ https://issues.apache.org/jira/browse/YARN-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212836#comment-14212836 ] Jian He commented on YARN-2862: --- YARN-2010 may not solve this. YARN-1185 might have fixed thi

[jira] [Commented] (YARN-2816) NM fail to start with NPE during container recovery

[ https://issues.apache.org/jira/browse/YARN-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212838#comment-14212838 ] Jason Lowe commented on YARN-2816: -- +1 lgtm. Committing this. > NM fail to start with NP

[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-tabpanel&focusedCommentId=14212835#comment-14212835 ] Rohith commented on YARN-2588: -- Thanks Karthik!! I have raised YARN-2865 > Standby RM does no

[jira] [Created] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

Rohith created YARN-2865: Summary: Application recovery continuously fails with "Application with id already present. Cannot duplicate" Key: YARN-2865 URL: https://issues.apache.org/jira/browse/YARN-2865 Proj

[jira] [Updated] (YARN-2056) Disable preemption at Queue level

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-2056: - Attachment: YARN-2056.201411142002.txt [~leftnoteasy], Thank you for all of your help. Uploading new patch.

[jira] [Commented] (YARN-2857) ConcurrentModificationException in ContainerLogAppender

[ https://issues.apache.org/jira/browse/YARN-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212810#comment-14212810 ] Hudson commented on YARN-2857: -- FAILURE: Integrated in Hadoop-trunk-Commit #6545 (See [https:

[jira] [Commented] (YARN-2857) ConcurrentModificationException in ContainerLogAppender

[ https://issues.apache.org/jira/browse/YARN-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212792#comment-14212792 ] Jason Lowe commented on YARN-2857: -- +1 lgtm. Committing this. > ConcurrentModificationEx

[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-tabpanel&focusedCommentId=14212777#comment-14212777 ] Karthik Kambatla commented on YARN-2588: Let us do it on another JIRA, given this i

[jira] [Assigned] (YARN-2375) Allow enabling/disabling timeline server per framework

[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai reassigned YARN-2375: --- Assignee: Mit Desai > Allow enabling/disabling timeline server per framework > ---

[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-tabpanel&focusedCommentId=14212775#comment-14212775 ] Rohith commented on YARN-2588: -- There is another hidden similar issue after this patch. Shoul

[jira] [Updated] (YARN-1530) [Umbrella] Store, manage and serve per-framework application-timeline data

[ https://issues.apache.org/jira/browse/YARN-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-1530: Assignee: (was: Mit Desai) > [Umbrella] Store, manage and serve per-framework application-timeline data >

[jira] [Assigned] (YARN-1530) [Umbrella] Store, manage and serve per-framework application-timeline data

[ https://issues.apache.org/jira/browse/YARN-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai reassigned YARN-1530: --- Assignee: Mit Desai > [Umbrella] Store, manage and serve per-framework application-timeline data > ---

[jira] [Commented] (YARN-2811) Fair Scheduler is violating max memory settings in 2.4

[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212769#comment-14212769 ] Hadoop QA commented on YARN-2811: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212672#comment-14212672 ] Karthik Kambatla commented on YARN-2604: +1 to what Jason said. Reusing the configs

[jira] [Commented] (YARN-2862) RM might not start if the machine was hard shutdown and FileSystemRMStateStore was used

[ https://issues.apache.org/jira/browse/YARN-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212671#comment-14212671 ] Gera Shegalov commented on YARN-2862: - [~mingma], It's potentially already fixed by YAR

[jira] [Commented] (YARN-2862) RM might not start if the machine was hard shutdown and FileSystemRMStateStore was used

[ https://issues.apache.org/jira/browse/YARN-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212640#comment-14212640 ] Ming Ma commented on YARN-2862: --- Here are some possible ways to fix it. 1) Fix RMAppManager'

[jira] [Updated] (YARN-2811) Fair Scheduler is violating max memory settings in 2.4

[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2811: -- Attachment: YARN-2811.v8.patch > Fair Scheduler is violating max memory settings in 2.4 > ---

[jira] [Commented] (YARN-2166) Timelineserver should validate that yarn.timeline-service.leveldb-timeline-store.ttl-interval-ms is greater than zero when level db is for timeline store

[ https://issues.apache.org/jira/browse/YARN-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212600#comment-14212600 ] Zhijie Shen commented on YARN-2166: --- See the comments on [YARN-2165|https://issues.apach

[jira] [Commented] (YARN-2165) Timelineserver should validate that yarn.timeline-service.ttl-ms is greater than zero

[ https://issues.apache.org/jira/browse/YARN-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212595#comment-14212595 ] Zhijie Shen commented on YARN-2165: --- bq. should the check be (<= 0) instead of (< 0) ? Si

[jira] [Commented] (YARN-2745) YARN new pluggable scheduler which does multi-resource packing

[ https://issues.apache.org/jira/browse/YARN-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212586#comment-14212586 ] Srikanth Kandula commented on YARN-2745: Thanks Karthik, that is an interesting tho

[jira] [Commented] (YARN-2603) ApplicationConstants missing HADOOP_MAPRED_HOME

[ https://issues.apache.org/jira/browse/YARN-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212538#comment-14212538 ] Ray Chiang commented on YARN-2603: -- I had no real comments, but the feedback is good to kn

[jira] [Created] (YARN-2864) TestRMWebServicesAppsModification fails in trunk

Ted Yu created YARN-2864: Summary: TestRMWebServicesAppsModification fails in trunk Key: YARN-2864 URL: https://issues.apache.org/jira/browse/YARN-2864 Project: Hadoop YARN Issue Type: Test

[jira] [Commented] (YARN-2846) Incorrect persist exit code for running containers in reacquireContainer() that interrupted by NodeManager restart.

[ https://issues.apache.org/jira/browse/YARN-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212378#comment-14212378 ] Hudson commented on YARN-2846: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #5 (See [

[jira] [Commented] (YARN-2635) TestRM, TestRMRestart, TestClientToAMTokens should run with both CS and FS

[ https://issues.apache.org/jira/browse/YARN-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212381#comment-14212381 ] Hudson commented on YARN-2635: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #5 (See [

[jira] [Commented] (YARN-2603) ApplicationConstants missing HADOOP_MAPRED_HOME

[ https://issues.apache.org/jira/browse/YARN-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212385#comment-14212385 ] Hudson commented on YARN-2603: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #5 (See [

[jira] [Commented] (YARN-2853) Killing app may hang while AM is unregistering

[ https://issues.apache.org/jira/browse/YARN-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212389#comment-14212389 ] Hudson commented on YARN-2853: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #5 (See [

[jira] [Commented] (YARN-2766) ApplicationHistoryManager is expected to return a sorted list of apps/attempts/containers

[ https://issues.apache.org/jira/browse/YARN-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212390#comment-14212390 ] Hudson commented on YARN-2766: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #5 (See [

[jira] [Commented] (YARN-2856) Application recovery throw InvalidStateTransitonException: Invalid event: ATTEMPT_KILLED at ACCEPTED

[ https://issues.apache.org/jira/browse/YARN-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212379#comment-14212379 ] Hudson commented on YARN-2856: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #5 (See [

[jira] [Commented] (YARN-2635) TestRM, TestRMRestart, TestClientToAMTokens should run with both CS and FS

[ https://issues.apache.org/jira/browse/YARN-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212356#comment-14212356 ] Hudson commented on YARN-2635: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1957 (See [htt

[jira] [Commented] (YARN-2603) ApplicationConstants missing HADOOP_MAPRED_HOME

[ https://issues.apache.org/jira/browse/YARN-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212360#comment-14212360 ] Hudson commented on YARN-2603: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1957 (See [htt

[jira] [Commented] (YARN-2853) Killing app may hang while AM is unregistering

[ https://issues.apache.org/jira/browse/YARN-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212364#comment-14212364 ] Hudson commented on YARN-2853: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1957 (See [htt

[jira] [Commented] (YARN-2856) Application recovery throw InvalidStateTransitonException: Invalid event: ATTEMPT_KILLED at ACCEPTED

[ https://issues.apache.org/jira/browse/YARN-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212354#comment-14212354 ] Hudson commented on YARN-2856: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1957 (See [htt

[jira] [Commented] (YARN-2846) Incorrect persist exit code for running containers in reacquireContainer() that interrupted by NodeManager restart.

[ https://issues.apache.org/jira/browse/YARN-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212353#comment-14212353 ] Hudson commented on YARN-2846: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1957 (See [htt

[jira] [Commented] (YARN-2766) ApplicationHistoryManager is expected to return a sorted list of apps/attempts/containers

[ https://issues.apache.org/jira/browse/YARN-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212365#comment-14212365 ] Hudson commented on YARN-2766: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1957 (See [htt

[jira] [Commented] (YARN-2766) ApplicationHistoryManager is expected to return a sorted list of apps/attempts/containers

[ https://issues.apache.org/jira/browse/YARN-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212301#comment-14212301 ] Hudson commented on YARN-2766: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk-Java8 #5 (See [https

[jira] [Commented] (YARN-2856) Application recovery throw InvalidStateTransitonException: Invalid event: ATTEMPT_KILLED at ACCEPTED

[ https://issues.apache.org/jira/browse/YARN-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212291#comment-14212291 ] Hudson commented on YARN-2856: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk-Java8 #5 (See [https

[jira] [Commented] (YARN-2846) Incorrect persist exit code for running containers in reacquireContainer() that interrupted by NodeManager restart.

[ https://issues.apache.org/jira/browse/YARN-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212290#comment-14212290 ] Hudson commented on YARN-2846: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk-Java8 #5 (See [https

[jira] [Commented] (YARN-2853) Killing app may hang while AM is unregistering

[ https://issues.apache.org/jira/browse/YARN-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212300#comment-14212300 ] Hudson commented on YARN-2853: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk-Java8 #5 (See [https

  1   2   >