[jira] [Commented] (YARN-3575) Job using 2.5 jars fails on a 2.6 cluster whose RM has been restarted

[ https://issues.apache.org/jira/browse/YARN-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548118#comment-14548118 ] Jason Lowe commented on YARN-3575: -- The only way to support compatibility would be to

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548130#comment-14548130 ] Jason Lowe commented on YARN-41: Looking at the table above, I'm wondering about the case

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548102#comment-14548102 ] Tsuyoshi Ozawa commented on YARN-2336: -- [~ajisakaa] thank you for updating. We're

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548141#comment-14548141 ] Junping Du commented on YARN-41: Thanks [~devaraj.k] for providing truth table above.

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548145#comment-14548145 ] Junping Du commented on YARN-41: bq. Jason Lowe, any comments here? Sorry. I didn't see

[jira] [Commented] (YARN-3668) Long run service shouldn't be killed even if Yarn crashed

[ https://issues.apache.org/jira/browse/YARN-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548123#comment-14548123 ] sandflee commented on YARN-3668: thanks [~stevel], we're using our own AM not slider, and

[jira] [Commented] (YARN-2821) Distributed shell app master becomes unresponsive sometimes

[ https://issues.apache.org/jira/browse/YARN-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547966#comment-14547966 ] Hadoop QA commented on YARN-2821: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-1922) Process group remains alive after container process is killed externally

[ https://issues.apache.org/jira/browse/YARN-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547997#comment-14547997 ] gu-chi commented on YARN-1922: -- Hi, I see you comment here to check in YARN-1922.5.patch, but

[jira] [Commented] (YARN-3670) Add JobConf XML link in Yarn RM UI

[ https://issues.apache.org/jira/browse/YARN-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548047#comment-14548047 ] Jason Lowe commented on YARN-3670: -- Sure, we could solve this by adding APIs for

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547990#comment-14547990 ] Tsuyoshi Ozawa commented on YARN-2336: -- OK, I'm checking it. Fair scheduler REST api

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547959#comment-14547959 ] Hadoop QA commented on YARN-3411: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Updated] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-2336: - Affects Version/s: 2.6.0 Fair scheduler REST api returns a missing '[' bracket JSON for deep

[jira] [Created] (YARN-3670) Add JobConf XML link in Yarn RM UI

Hari Sekhon created YARN-3670: - Summary: Add JobConf XML link in Yarn RM UI Key: YARN-3670 URL: https://issues.apache.org/jira/browse/YARN-3670 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-3670) Add JobConf XML link in Yarn RM UI

[ https://issues.apache.org/jira/browse/YARN-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548039#comment-14548039 ] Hari Sekhon commented on YARN-3670: --- I understand (you can't imagine how often I've had

[jira] [Commented] (YARN-3670) Add JobConf XML link in Yarn RM UI

[ https://issues.apache.org/jira/browse/YARN-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548020#comment-14548020 ] Jason Lowe commented on YARN-3670: -- This is not easily implementable in the general case,

[jira] [Updated] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3411: - Attachment: YARN-3411-YARN-2928.004.patch Uploading YARN-3411-YARN-2928.004.patch. The earlier patch had

[jira] [Updated] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3411: - Attachment: YARN-3411-YARN-2928.003.patch Attaching new patch YARN-3411-YARN-2928.003.patch with code

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547730#comment-14547730 ] Hadoop QA commented on YARN-3411: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3645) ResourceManager can't start success if attribute value of aclSubmitApps is null in fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547601#comment-14547601 ] Mohammad Shahid Khan commented on YARN-3645: Loading with invalid node

[jira] [Commented] (YARN-126) yarn rmadmin help message contains reference to hadoop cli and JT

[ https://issues.apache.org/jira/browse/YARN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547669#comment-14547669 ] Akira AJISAKA commented on YARN-126: Thanks [~rémy] for updating the patch. Some

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.001.patch FairScheduler: potential livelock due to maxAMShare limitation and

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547687#comment-14547687 ] zhihai xu commented on YARN-3655: - I uploaded a new patch YARN-3655.001.patch, which added

[jira] [Updated] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3583: -- Attachment: 0003-YARN-3583.patch Thank you [~leftnoteasy] for the comments. Updated a patch addressing the

[jira] [Updated] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-2336: Attachment: YARN-2336.009.patch Thanks [~ozawa] for comments! Updated the patch. Fair scheduler

[jira] [Commented] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548239#comment-14548239 ] Siqi Li commented on YARN-3468: --- Agreed. setting yarn.nodemanager.delete.debug-delay-sec to

[jira] [Resolved] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-3468. --- Resolution: Won't Fix NM should not blindly rename usercache/filecache/nmPrivate on restart

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v2.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Updated] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1945: -- Attachment: YARN-1945.v6.patch Adding description for each pool in Fair Scheduler Page from

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v2.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548335#comment-14548335 ] Junping Du commented on YARN-3411: -- bq. No, we will never drop the last value.

[jira] [Updated] (YARN-3605) _ as method name may not be supported much longer

[ https://issues.apache.org/jira/browse/YARN-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3605: --- Hadoop Flags: Incompatible change _ as method name may not be supported much longer

[jira] [Updated] (YARN-3579) CommonNodeLabelsManager should support NodeLabel instead of string label name when getting node-to-label/label-to-label mappings

[ https://issues.apache.org/jira/browse/YARN-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3579: - Fix Version/s: 2.8.0 CommonNodeLabelsManager should support NodeLabel instead of string label name when

[jira] [Updated] (YARN-3669) Attempt-failures validatiy interval should have a global admin configurable lower limit

[ https://issues.apache.org/jira/browse/YARN-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3669: Labels: newbie (was: ) Attempt-failures validatiy interval should have a global admin configurable lower

[jira] [Updated] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Attachment: YARN-1735.v2.patch For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[jira] [Commented] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548350#comment-14548350 ] Hadoop QA commented on YARN-2876: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Updated] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-41: -- Labels: (was: BB2015-05-TBR) The RM should handle the graceful shutdown of the NM.

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548410#comment-14548410 ] Hadoop QA commented on YARN-2336: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548356#comment-14548356 ] Hadoop QA commented on YARN-1945: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Updated] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-3069: - Attachment: YARN-3069.009.patch - Move yarn.client.app-submission.poll-interval to DeprecatedProperties.md

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: (was: YARN-2876.v2.patch) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource

[jira] [Commented] (YARN-3605) _ as method name may not be supported much longer

[ https://issues.apache.org/jira/browse/YARN-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548375#comment-14548375 ] Robert Joseph Evans commented on YARN-3605: --- This is not a newbie issue. The

[jira] [Updated] (YARN-3605) _ as method name may not be supported much longer

[ https://issues.apache.org/jira/browse/YARN-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated YARN-3605: -- Labels: (was: newbie) _ as method name may not be supported much longer

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548379#comment-14548379 ] Vrushali C commented on YARN-3411: -- Hi [~djp] Thanks for the initial quick feedback! Some

[jira] [Commented] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548378#comment-14548378 ] Hadoop QA commented on YARN-1735: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548383#comment-14548383 ] Vrushali C commented on YARN-3411: -- The patch has an overall -1 due to a couple of

[jira] [Commented] (YARN-1896) For FairScheduler expose MinimumQueueResource of each queue in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548265#comment-14548265 ] Siqi Li commented on YARN-1896: --- As I said in the description, it would be good to have

[jira] [Commented] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548271#comment-14548271 ] Hadoop QA commented on YARN-2876: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Updated] (YARN-3302) TestDockerContainerExecutor should run automatically if it can detect docker in the usual place

[ https://issues.apache.org/jira/browse/YARN-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra Kumar Naik updated YARN-3302: -- Attachment: YARN-3302-trunk.002.patch Updated patch to address Ravi' s comments

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548261#comment-14548261 ] Devaraj K commented on YARN-41: --- Thanks a lot [~jlowe] and [~djp] for your comments. I will

[jira] [Commented] (YARN-3302) TestDockerContainerExecutor should run automatically if it can detect docker in the usual place

[ https://issues.apache.org/jira/browse/YARN-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548274#comment-14548274 ] Hadoop QA commented on YARN-3302: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3489) RMServerUtils.validateResourceRequests should only obtain queue info once

[ https://issues.apache.org/jira/browse/YARN-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548460#comment-14548460 ] Wangda Tan commented on YARN-3489: -- [~varun_saxena], Tx for updating, I tried to run RM

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v2.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: (was: YARN-2876.v2.patch) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource

[jira] [Commented] (YARN-3565) NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object instead of String

[ https://issues.apache.org/jira/browse/YARN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548485#comment-14548485 ] Wangda Tan commented on YARN-3565: -- [~Naganarasimha], thanks for updating, mostly looks

[jira] [Commented] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548492#comment-14548492 ] Bikas Saha commented on YARN-1902: -- An alternate approach that we tried in Apache Tez is

[jira] [Commented] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548496#comment-14548496 ] Hadoop QA commented on YARN-3069: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548480#comment-14548480 ] MENG DING commented on YARN-1902: - Thanks [~bikassaha] and [~vinodkv] for the education and

[jira] [Commented] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548510#comment-14548510 ] Wangda Tan commented on YARN-3583: -- [~sunilg], Thanks updating, mostly looks good, 2 nits:

[jira] [Commented] (YARN-3645) ResourceManager can't start success if attribute value of aclSubmitApps is null in fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548516#comment-14548516 ] Gabor Liptak commented on YARN-3645: Maybe we are to extract the functionality into a

[jira] [Updated] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1945: -- Attachment: YARN-1945.v6.patch Adding description for each pool in Fair Scheduler Page from

[jira] [Updated] (YARN-2884) Proxying all AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-2884: - Assignee: Kishore Chaliparambil (was: Subru Krishnan) Proxying all AM-RM communications

[jira] [Created] (YARN-3671) Integrate Federation services with ResourceManager

Subru Krishnan created YARN-3671: Summary: Integrate Federation services with ResourceManager Key: YARN-3671 URL: https://issues.apache.org/jira/browse/YARN-3671 Project: Hadoop YARN Issue

[jira] [Created] (YARN-3673) Create a FailoverProxy for Federation services

Subru Krishnan created YARN-3673: Summary: Create a FailoverProxy for Federation services Key: YARN-3673 URL: https://issues.apache.org/jira/browse/YARN-3673 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1945: -- Attachment: (was: YARN-1945.v6.patch) Adding description for each pool in Fair Scheduler Page from

[jira] [Updated] (YARN-3302) TestDockerContainerExecutor should run automatically if it can detect docker in the usual place

[ https://issues.apache.org/jira/browse/YARN-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra Kumar Naik updated YARN-3302: -- Attachment: YARN-3302-trunk.003.patch fixed whitespaces in patch

[jira] [Assigned] (YARN-2884) Proxying all AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan reassigned YARN-2884: Assignee: Subru Krishnan Proxying all AM-RM communications

[jira] [Created] (YARN-3672) Create Facade for Federation State and Policy Store

Subru Krishnan created YARN-3672: Summary: Create Facade for Federation State and Policy Store Key: YARN-3672 URL: https://issues.apache.org/jira/browse/YARN-3672 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-3673) Create a FailoverProxy for Federation services

[ https://issues.apache.org/jira/browse/YARN-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3673: - Description: This JIRA proposes creating a failover proxy for Federation based on the cluster

[jira] [Commented] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548623#comment-14548623 ] Hadoop QA commented on YARN-3583: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-2821) Distributed shell app master becomes unresponsive sometimes

[ https://issues.apache.org/jira/browse/YARN-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549099#comment-14549099 ] Jian He commented on YARN-2821: --- thanks Varun ! looks good overall. test case - for below, we

[jira] [Commented] (YARN-3541) Add version info on timeline service / generic history web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549116#comment-14549116 ] Xuan Gong commented on YARN-3541: - +1 LGTM. Will commit Add version info on timeline

[jira] [Commented] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549238#comment-14549238 ] Hadoop QA commented on YARN-2876: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3647) RMWebServices api's should use updated api from CommonNodeLabelsManager to get NodeLabel object

[ https://issues.apache.org/jira/browse/YARN-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549378#comment-14549378 ] Wangda Tan commented on YARN-3647: -- [~sunilg], thanks for working on this: 1)

[jira] [Commented] (YARN-3541) Add version info on timeline service / generic history web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549152#comment-14549152 ] Hudson commented on YARN-3541: -- FAILURE: Integrated in Hadoop-trunk-Commit #7856 (See

[jira] [Updated] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-3069: - Attachment: YARN-3069.010.patch - Fix whitespace and deprecation warnings Document missing properties in

[jira] [Updated] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-3069: - Attachment: (was: YARN-3069.010.patch) Document missing properties in yarn-default.xml

[jira] [Commented] (YARN-3668) Long run service shouldn't be killed even if Yarn crashed

[ https://issues.apache.org/jira/browse/YARN-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549218#comment-14549218 ] Steve Loughran commented on YARN-3668: -- [~sandflee] : I know you are using something

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v3.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Created] (YARN-3675) FairScheduler: RM quits when node removal races with continousscheduling on the same node

Anubhav Dhoot created YARN-3675: --- Summary: FairScheduler: RM quits when node removal races with continousscheduling on the same node Key: YARN-3675 URL: https://issues.apache.org/jira/browse/YARN-3675

[jira] [Commented] (YARN-3302) TestDockerContainerExecutor should run automatically if it can detect docker in the usual place

[ https://issues.apache.org/jira/browse/YARN-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549127#comment-14549127 ] Hadoop QA commented on YARN-3302: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3541) Add version info on timeline service / generic history web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549138#comment-14549138 ] Xuan Gong commented on YARN-3541: - Committed into trunk/branch-2. Thanks, zhijie Add

[jira] [Updated] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Attachment: YARN-1735.v3.patch For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[jira] [Commented] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549314#comment-14549314 ] Hadoop QA commented on YARN-3069: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Updated] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-3069: - Attachment: YARN-3069.010.patch - Leave out MR bits from previous patch. Document missing properties in

[jira] [Commented] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549417#comment-14549417 ] Hadoop QA commented on YARN-1735: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549249#comment-14549249 ] Hadoop QA commented on YARN-1945: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549459#comment-14549459 ] Hadoop QA commented on YARN-2876: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

[ https://issues.apache.org/jira/browse/YARN-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549460#comment-14549460 ] Jian He commented on YARN-3632: --- - the current reorder implementation in containerReleased

[jira] [Updated] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Attachment: YARN-1735.v4.patch For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[jira] [Updated] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1945: -- Attachment: YARN-1945.v7.patch Adding description for each pool in Fair Scheduler Page from

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549725#comment-14549725 ] Hadoop QA commented on YARN-3411: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549692#comment-14549692 ] Sangjin Lee commented on YARN-3411: --- It seems like the line that adds the hbase

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549776#comment-14549776 ] Sangjin Lee commented on YARN-3411: --- Or, better: {code} Configuration hbaseConf =

[jira] [Updated] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3411: - Attachment: YARN-3411-YARN-2928.005.patch [Storage implementation] explore the native HBase write schema

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549601#comment-14549601 ] Hadoop QA commented on YARN-3411: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Created] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

Arun Suresh created YARN-3676: - Summary: Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests Key: YARN-3676 URL: https://issues.apache.org/jira/browse/YARN-3676

[jira] [Commented] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549614#comment-14549614 ] Hadoop QA commented on YARN-1735: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549631#comment-14549631 ] Vrushali C commented on YARN-3411: -- Updating the code now to fix the javadoc warning and

[jira] [Updated] (YARN-3518) default rm/am expire interval should not less than default resourcemanager connect wait time

[ https://issues.apache.org/jira/browse/YARN-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-3518: --- Attachment: YARN-3518.002.patch replace RESOURCEMANAGER_CONNECT_MAX_WAIT_MS with

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

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549505#comment-14549505 ] Chris Douglas commented on YARN-1039: - The semantics of a boolean flag are opaque. The

  1   2   >