[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

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

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

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

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

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

[jira] [Assigned] (YARN-3484) Fix up yarn top shell code

[ https://issues.apache.org/jira/browse/YARN-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reassigned YARN-3484: --- Assignee: Varun Vasudev > Fix up yarn top shell code > -- > >

[jira] [Updated] (YARN-3484) Fix up yarn top shell code

[ https://issues.apache.org/jira/browse/YARN-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3484: Attachment: YARN-3484.001.patch Allen, I've uploaded a patch to address your comments. Can you please

[jira] [Commented] (YARN-3294) Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period

[ https://issues.apache.org/jira/browse/YARN-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504613#comment-14504613 ] Varun Vasudev commented on YARN-3294: - [~tgraves] - thanks for pointing out the admin i

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504617#comment-14504617 ] Varun Vasudev commented on YARN-3517: - Test failure is unrelated. > RM web ui for dump

[jira] [Commented] (YARN-3511) Add errors and warnings page to ATS

[ https://issues.apache.org/jira/browse/YARN-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504621#comment-14504621 ] Varun Vasudev commented on YARN-3511: - The eclipse target passes on my machine. I'm not

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

sandflee created YARN-3518: -- Summary: default rm/am expire interval should less than default resourcemanager connect wait time Key: YARN-3518 URL: https://issues.apache.org/jira/browse/YARN-3518 Project: Had

[jira] [Commented] (YARN-3484) Fix up yarn top shell code

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

[jira] [Created] (YARN-3519) registerApplicationMaster couldn't get all running containers if rm is rebuilding container info while am is relaunched

sandflee created YARN-3519: -- Summary: registerApplicationMaster couldn't get all running containers if rm is rebuilding container info while am is relaunched Key: YARN-3519 URL: https://issues.apache.org/jira/browse/YAR

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing MR events to v2 ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504712#comment-14504712 ] Junping Du commented on YARN-3046: -- Thanks [~zjshen] and [~sjlee0] for review and comments

[jira] [Updated] (YARN-3046) [Event producers] Implement MapReduce AM writing MR events to v2 ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3046: - Attachment: YARN-3046-v6.patch > [Event producers] Implement MapReduce AM writing MR events to v2 ATS > ---

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

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

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

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

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

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

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

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

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

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

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

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

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

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

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

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

[jira] [Updated] (YARN-3406) Add a Running Container for RM Web UI

[ https://issues.apache.org/jira/browse/YARN-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryu Kobayashi updated YARN-3406: Summary: Add a Running Container for RM Web UI (was: Add a numUsedContainer for RM Web UI and REST A

[jira] [Updated] (YARN-3406) Add a Running Container for RM Web UI

[ https://issues.apache.org/jira/browse/YARN-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryu Kobayashi updated YARN-3406: Attachment: screenshot2.png > Add a Running Container for RM Web UI > ---

[jira] [Updated] (YARN-3406) Add a Running Container for RM Web UI

[ https://issues.apache.org/jira/browse/YARN-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryu Kobayashi updated YARN-3406: Attachment: YARN-3406.2.patch [~ozawa] I fixed the conflict. And, I was changed to the label name "Ru

[jira] [Updated] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3445: - Summary: Cache runningApps in RMNode for getting running apps on given NodeId (was: NM notify RM on runnin

[jira] [Updated] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3445: - Description: Per discussion in YARN-3334, we need filter out unnecessary collectors info from RM in heartbe

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504828#comment-14504828 ] Junping Du commented on YARN-3445: -- I have updated the title and description. Hi [~vinodkv

[jira] [Updated] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3494: - Attachment: 0002-YARN-3494.patch > Expose AM resource limit and user limit in QueueMetrics > -

[jira] [Commented] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

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

[jira] [Commented] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504831#comment-14504831 ] Rohith commented on YARN-3494: -- Updated the patch fixing review comment, kindly review it. >

[jira] [Commented] (YARN-3437) convert load test driver to timeline service v.2

[ https://issues.apache.org/jira/browse/YARN-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504842#comment-14504842 ] Junping Du commented on YARN-3437: -- Filed a new JIRA to track fine-grained performance dat

[jira] [Updated] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3494: - Attachment: 0002-YARN-3494.patch > Expose AM resource limit and user limit in QueueMetrics > -

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504869#comment-14504869 ] john lilley commented on YARN-3514: --- Thank you! I am very impressed with the short time

[jira] [Commented] (YARN-3406) Add a Running Container for RM Web UI

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

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504954#comment-14504954 ] Thomas Graves commented on YARN-3517: - Thanks for following up on this. Could you also

[jira] [Commented] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

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

[jira] [Updated] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3517: Attachment: YARN-3517.002.patch Uploaded a new patch to address Thomas's comments. bq. Could you als

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

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

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

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

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

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

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

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

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

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

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505193#comment-14505193 ] Sunil G commented on YARN-3517: --- HI [~vvasudev] I have couple of comments on same.. 1. {co

[jira] [Created] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

Chang Li created YARN-3520: -- Summary: get rid of excessive stacktrace caused by expired cookie in timeline log Key: YARN-3520 URL: https://issues.apache.org/jira/browse/YARN-3520 Project: Hadoop YARN

[jira] [Updated] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

[ https://issues.apache.org/jira/browse/YARN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3520: --- Attachment: YARN-3520.patch > get rid of excessive stacktrace caused by expired cookie in timeline log > --

[jira] [Commented] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

[ https://issues.apache.org/jira/browse/YARN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505223#comment-14505223 ] Chang Li commented on YARN-3520: [~mitdesai], [~jeagles], could you please help review this

[jira] [Updated] (YARN-3319) Implement a FairOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3319: -- Attachment: YARN-3319.73.patch another findbugs > Implement a FairOrderingPolicy > -

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing MR events to v2 ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505259#comment-14505259 ] Zhijie Shen commented on YARN-3046: --- Will commit the last patch late today to give Sangji

[jira] [Updated] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3517: -- Priority: Blocker (was: Major) Target Version/s: 2.8.0 This should g

[jira] [Resolved] (YARN-3213) Respect labels in Capacity Scheduler when computing user-limit

[ https://issues.apache.org/jira/browse/YARN-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-3213. -- Resolution: Duplicate This issue is included by YARN-3361. So resolve this as duplicated. > Respect labe

[jira] [Commented] (YARN-3482) Report NM available resources in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505284#comment-14505284 ] Inigo Goiri commented on YARN-3482: --- [~kasha], the administration interface already has

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing MR events to v2 ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505286#comment-14505286 ] Sangjin Lee commented on YARN-3046: --- LGTM. Just to close on one point, at a later point

[jira] [Updated] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3517: Attachment: YARN-3517.003.patch bq. If adminACLsManager.areACLsEnabled() is false, do we need above c

[jira] [Updated] (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:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2268: -- Target Version/s: 2.8.0 > Disallow formatting the RMStateStore when there is an R

[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=14505293#comment-14505293 ] Vinod Kumar Vavilapalli commented on YARN-2268: --- At YARN-2131, I mentioned a

[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=14505296#comment-14505296 ] Vinod Kumar Vavilapalli commented on YARN-2268: --- Further, this should also ta

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505301#comment-14505301 ] Sunil G commented on YARN-3517: --- Thanks [~vvasudev] Patch looks good. > RM web ui for dumpi

[jira] [Commented] (YARN-3410) YARN admin should be able to remove individual application records from RMStateStore

[ https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505299#comment-14505299 ] Vinod Kumar Vavilapalli commented on YARN-3410: --- Seems like this is going in

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505300#comment-14505300 ] Sunil G commented on YARN-3517: --- Thanks [~vvasudev] Patch looks good. > RM web ui for dumpi

[jira] [Commented] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

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

[jira] [Updated] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

[ https://issues.apache.org/jira/browse/YARN-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3516: Attachment: (was: YARN-3516.000.patch) > killing ContainerLocalizer action doesn't take effect when priva

[jira] [Updated] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

[ https://issues.apache.org/jira/browse/YARN-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3516: Attachment: YARN-3516.000.patch > killing ContainerLocalizer action doesn't take effect when private localize

[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=14505322#comment-14505322 ] Xuan Gong commented on YARN-2268: - bq. If an active RM creates a "I am using the state-stor

[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

[ https://issues.apache.org/jira/browse/YARN-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505326#comment-14505326 ] Xuan Gong commented on YARN-3516: - [~zxu] Thanks for working on this jira. I will take a lo

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505333#comment-14505333 ] Vinod Kumar Vavilapalli commented on YARN-3445: --- Better than before, will com

[jira] [Commented] (YARN-3431) Sub resources of timeline entity needs to be passed to a separate endpoint.

[ https://issues.apache.org/jira/browse/YARN-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505334#comment-14505334 ] Sangjin Lee commented on YARN-3431: --- It looks good to me. One small suggestion (it's not

[jira] [Updated] (YARN-3413) Node label attributes (like exclusivity) should settable via addToClusterNodeLabels but shouldn't be changeable at runtime

[ https://issues.apache.org/jira/browse/YARN-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3413: -- Summary: Node label attributes (like exclusivity) should settable via addToCluste

[jira] [Commented] (YARN-3519) registerApplicationMaster couldn't get all running containers if rm is rebuilding container info while am is relaunched

[ https://issues.apache.org/jira/browse/YARN-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505378#comment-14505378 ] Jian He commented on YARN-3519: --- [~sandflee], is this the issue that AM could re-register w

[jira] [Commented] (YARN-3437) convert load test driver to timeline service v.2

[ https://issues.apache.org/jira/browse/YARN-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505382#comment-14505382 ] Sangjin Lee commented on YARN-3437: --- I think we need to make progress on this as this is

[jira] [Commented] (YARN-3482) Report NM available resources in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505396#comment-14505396 ] Karthik Kambatla commented on YARN-3482: I like 2 better. > Report NM available r

[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

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

[jira] [Commented] (YARN-3482) Report NM available resources in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505420#comment-14505420 ] Inigo Goiri commented on YARN-3482: --- I agree, 2 is more distributed and fits better the m

[jira] [Commented] (YARN-3319) Implement a FairOrderingPolicy

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

[jira] [Commented] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

[ https://issues.apache.org/jira/browse/YARN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505425#comment-14505425 ] Mit Desai commented on YARN-3520: - lgtm +1 (non-binding) This change is related to logging

[jira] [Created] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

Wangda Tan created YARN-3521: Summary: Support return structured NodeLabel objects in REST API when call getClusterNodeLabels Key: YARN-3521 URL: https://issues.apache.org/jira/browse/YARN-3521 Project: H

[jira] [Updated] (YARN-3413) Node label attributes (like exclusivity) should settable via addToClusterNodeLabels but shouldn't be changeable at runtime

[ https://issues.apache.org/jira/browse/YARN-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3413: - Attachment: YARN-3413.3.patch Thanks for review, [~vinodkv]: bq. We should simply force the labelName to fo

[jira] [Assigned] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-3521: - Assignee: Sunil G > Support return structured NodeLabel objects in REST API when call > getClusterNodeLab

[jira] [Commented] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505437#comment-14505437 ] Sunil G commented on YARN-3521: --- Recently have done few work in Rest. I wud like to take over

[jira] [Commented] (YARN-3482) Report NM available resources in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505440#comment-14505440 ] Lei Guo commented on YARN-3482: --- What's the relationship between this and 3332? They should b

[jira] [Updated] (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 updated YARN-3468: -- Attachment: YARN-3468.v2.patch > NM should not blindly rename usercache/filecache/nmPrivate on restart >

[jira] [Commented] (YARN-3482) Report NM available resources in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505476#comment-14505476 ] Inigo Goiri commented on YARN-3482: --- [~grey], the ultimate target of this task is to prov

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

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

[jira] [Commented] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505503#comment-14505503 ] Wangda Tan commented on YARN-3521: -- [~sunilg], thanks for taking this, it's yours :) > Su

[jira] [Commented] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

[ https://issues.apache.org/jira/browse/YARN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505522#comment-14505522 ] Jonathan Eagles commented on YARN-3520: --- +1. While this jira is regarding a custom Ke

[jira] [Commented] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

[ https://issues.apache.org/jira/browse/YARN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505549#comment-14505549 ] Chang Li commented on YARN-3520: [~jlowe] could you please help do a final review of this p

[jira] [Updated] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-3514: Attachment: YARN-3514.002.patch In the first patch, the new test passed for me locally but failed on

[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-tabpanel&focusedCommentId=14505561#comment-14505561 ] Hadoop QA commented on YARN-3468: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (YARN-3434) Interaction between reservations and userlimit can result in significant ULF violation

[ https://issues.apache.org/jira/browse/YARN-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-3434: Attachment: YARN-3434.patch updated based on review comments > Interaction between reservations and

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing MR events to v2 ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505580#comment-14505580 ] Junping Du commented on YARN-3046: -- bq. If that turns out to be the case, we could conceiv

[jira] [Updated] (YARN-3046) [Event producers] Implement MapReduce AM writing MR events/counters to v2 ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3046: - Summary: [Event producers] Implement MapReduce AM writing MR events/counters to v2 ATS (was: [Event produc

[jira] [Commented] (YARN-3437) convert load test driver to timeline service v.2

[ https://issues.apache.org/jira/browse/YARN-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505593#comment-14505593 ] Junping Du commented on YARN-3437: -- I agree too if we don't have clear plan for YARN-2556

[jira] [Commented] (YARN-3434) Interaction between reservations and userlimit can result in significant ULF violation

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

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505640#comment-14505640 ] john lilley commented on YARN-3514: --- Sadly, we aren't equipped to upgrade and patch, we a

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505644#comment-14505644 ] john lilley commented on YARN-3514: --- We did work around the issue by changing our usernam

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

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

[jira] [Commented] (YARN-3319) Implement a FairOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505678#comment-14505678 ] Wangda Tan commented on YARN-3319: -- Some minor comments about configuration part: 1) gett

[jira] [Commented] (YARN-2740) ResourceManager side should properly handle node label modifications when distributed node label configuration enabled

[ https://issues.apache.org/jira/browse/YARN-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505709#comment-14505709 ] Wangda Tan commented on YARN-2740: -- General LGTM, some minor comments. 1) Mark YarnConfig

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505711#comment-14505711 ] Chris Nauroth commented on YARN-3514: - [~john.lil...@redpoint.net], thank you for the c

[jira] [Commented] (YARN-3363) add localization and container launch time to ContainerMetrics at NM to show these timing information for each active container.

[ https://issues.apache.org/jira/browse/YARN-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505744#comment-14505744 ] Anubhav Dhoot commented on YARN-3363: - The duration do not seem to belong in a ProcessT

[jira] [Commented] (YARN-3495) Confusing log generated by FairScheduler

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

  1   2   >