[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035910#comment-15035910 ] Junping Du commented on YARN-4403: -- Agree. LivelinessMonitor is more critical as it affects all YARN

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035886#comment-15035886 ] Junping Du commented on YARN-4408: -- [~rkanter], do we see this happen in a real deployment? I don't quite

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: REST_and_UI.zip > AM max resource configuration per partition to be displayed/updated correctly >

[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035950#comment-15035950 ] Junping Du commented on YARN-4403: -- bq. For YARN/MR, I could also definitely help in getting it in shape

[jira] [Commented] (YARN-4411) ResourceManager IllegalArgumentException error

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035895#comment-15035895 ] Junping Du commented on YARN-4411: -- Hi [~yarntime], I just assign the JIRA to you. > ResourceManager

[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035871#comment-15035871 ] Sunil G commented on YARN-4403: --- Hi [~djp] Thanks for the patch. Yes, its better to use {{MonotonicClock}}

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: (was: REST_and_UI.zip) > AM max resource configuration per partition to be displayed/updated

[jira] [Commented] (YARN-4401) A failed app recovery should not prevent the RM from starting

[ https://issues.apache.org/jira/browse/YARN-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035892#comment-15035892 ] Daniel Templeton commented on YARN-4401: I suppose I posed my proposal a little naively. Let's try

[jira] [Updated] (YARN-4411) ResourceManager IllegalArgumentException error

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4411: - Assignee: yarntime > ResourceManager IllegalArgumentException error >

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.005.patch Uploaded a new version of the patch with Windows support. > Add

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: 0004-YARN-4304.patch Attaching an updated version of patch addressing the comments. Also attached

[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035923#comment-15035923 ] Sunil G commented on YARN-4403: --- Yes. That sounds good. +1 for the patch. For YARN/MR, I could also

[jira] [Commented] (YARN-4371) "yarn application -kill" should take multiple application ids

[ https://issues.apache.org/jira/browse/YARN-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036056#comment-15036056 ] Sunil G commented on YARN-4371: --- Hi [~ozawa] Could you pls help to review the patch. > "yarn application

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036136#comment-15036136 ] Sunil G commented on YARN-4304: --- Test case failures and findbugs are related. I will address these in next

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036203#comment-15036203 ] Daniel Templeton commented on YARN-4406: Now that I've had a chance to look at the web UI code, I

[jira] [Commented] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036317#comment-15036317 ] Wangda Tan commented on YARN-4225: -- [~eepayne], Thanks for working on the patch, few comments: 1) bq.

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036345#comment-15036345 ] Robert Kanter commented on YARN-4408: - I haven't been able to reproduce this issue, and I agree that

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036336#comment-15036336 ] Kuhu Shukla commented on YARN-4406: --- Yes that is right, the issue is present on trunk. We could during

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036186#comment-15036186 ] Kuhu Shukla commented on YARN-4406: --- Thank you [~Naganarasimha]. Asking [~rchiang] if its alright for me

[jira] [Resolved] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang resolved YARN-4406. -- Resolution: Duplicate > RM Web UI continues to show decommissioned nodes even after RM restart >

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036299#comment-15036299 ] Xuan Gong commented on YARN-4392: - Thanks for the comments, [~Naganarasimha] bq. So actually in the patch i

[jira] [Updated] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4389: -- Attachment: 0002-YARN-4389.patch Attaching an updated patch correcting test case failures. Also fixed few

[jira] [Updated] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-4311: -- Attachment: YARN-4311-v2.patch This patch addresses graceful and other versions of refreshNodes and also

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036214#comment-15036214 ] Ray Chiang commented on YARN-4406: -- Thanks [~Naganarasimha]. I'll close up this JIRA as a duplicate. As

[jira] [Commented] (YARN-3840) Resource Manager web ui issue when sorting application by id (with application having id > 9999)

[ https://issues.apache.org/jira/browse/YARN-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036257#comment-15036257 ] Varun Saxena commented on YARN-3840: [~jianhe], kindly review. [~mohdshahidkhan], probably you can have

[jira] [Updated] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-4225: - Attachment: (was: YARN-4225.002.patch) > Add preemption status to yarn queue -status for capacity

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

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

[jira] [Updated] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-4225: - Attachment: YARN-4225.002.patch Attaching {{YARN-4225.002.patch}}, which implements

[jira] [Created] (YARN-4412) Create ClusterManager to compute ordered list of preferred NMs for QUEUEABLE containers

Arun Suresh created YARN-4412: - Summary: Create ClusterManager to compute ordered list of preferred NMs for QUEUEABLE containers Key: YARN-4412 URL: https://issues.apache.org/jira/browse/YARN-4412

[jira] [Updated] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-4225: - Attachment: YARN-4225.003.patch Sorry, I mis-named the patch. Should have been {{YARN-4225.003.patch}} >

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

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

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036241#comment-15036241 ] Sunil G commented on YARN-4406: --- YARN-3226 which is a subtask of YARN-914 will be splitting cluster metrics

[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

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

[jira] [Updated] (YARN-3458) CPU resource monitoring in Windows

[ https://issues.apache.org/jira/browse/YARN-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Inigo Goiri updated YARN-3458: -- Attachment: YARN-3458-9.patch Rebased to trunk. > CPU resource monitoring in Windows >

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036381#comment-15036381 ] Jian He commented on YARN-4398: --- [~iceberg565], added you to the contributor list. Assigned this to you.

[jira] [Assigned] (YARN-3102) Decommisioned Nodes not listed in Web UI

[ https://issues.apache.org/jira/browse/YARN-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla reassigned YARN-3102: - Assignee: Kuhu Shukla (was: Naganarasimha G R) > Decommisioned Nodes not listed in Web UI >

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036410#comment-15036410 ] Daniel Templeton commented on YARN-4406: That's the simplest resolution, but I was actually leaning

[jira] [Updated] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4408: Attachment: YARN-4408.002.patch The 002 patch adds the debug message. > NodeManager still reports

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036367#comment-15036367 ] Junping Du commented on YARN-4408: -- Thanks Robert for reply. If we don't understand how it happens in the

[jira] [Updated] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-4406: - Assignee: Kuhu Shukla > RM Web UI continues to show decommissioned nodes even after RM restart >

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

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

[jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

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

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036557#comment-15036557 ] Junping Du commented on YARN-4408: -- +1 on 003 patch. Will commit it shortly if no further comments from

[jira] [Updated] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4398: -- Assignee: NING DING > Yarn recover functionality causes the cluster running slowly and the cluster > usage rate

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036485#comment-15036485 ] Junping Du commented on YARN-4408: -- Thanks Robert for updating the patch. Can we make log messages here in

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

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

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036580#comment-15036580 ] Xuan Gong commented on YARN-4392: - [~Naganarasimha] bq. there is no limit on number of running apps in

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036389#comment-15036389 ] Ray Chiang commented on YARN-4406: -- That looks good to me. > RM Web UI continues to show decommissioned

[jira] [Updated] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4408: Attachment: YARN-4408.003.patch Sure. The 003 patch uses warn level. > NodeManager still reports

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036530#comment-15036530 ] Naganarasimha G R commented on YARN-4392: - [~xgong], Yes you are right, it would not be good to

[jira] [Commented] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036560#comment-15036560 ] Eric Payne commented on YARN-4225: -- Thanks [~leftnoteasy], for your helpful comments. bq. Do you think is

[jira] [Created] (YARN-4410) hadoop

qeko created YARN-4410: -- Summary: hadoop Key: YARN-4410 URL: https://issues.apache.org/jira/browse/YARN-4410 Project: Hadoop YARN Issue Type: Bug Reporter: qeko -- This message was

[jira] [Commented] (YARN-4401) A failed app recovery should not prevent the RM from starting

[ https://issues.apache.org/jira/browse/YARN-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035492#comment-15035492 ] Sunil G commented on YARN-4401: --- Hi [~templedf] I am not very sure about the use case here. However I feel if

[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4309: Attachment: YARN-4309.004.patch Thanks for the review [~sidharta-s]. bq. Could you clarify why the

[jira] [Commented] (YARN-4410) hadoop

[ https://issues.apache.org/jira/browse/YARN-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035468#comment-15035468 ] Naganarasimha G R commented on YARN-4410: - Whats this jira for ? If its raised by mistake, please

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035471#comment-15035471 ] NING DING commented on YARN-4398: - I uploaded a new patch that removed useless whitespace. The current test

[jira] [Created] (YARN-4413) Nodes in the includes list should not be listed as decommissioned in the UI

Daniel Templeton created YARN-4413: -- Summary: Nodes in the includes list should not be listed as decommissioned in the UI Key: YARN-4413 URL: https://issues.apache.org/jira/browse/YARN-4413 Project:

[jira] [Commented] (YARN-4292) ResourceUtilization should be a part of NodeInfo REST API

[ https://issues.apache.org/jira/browse/YARN-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036619#comment-15036619 ] Wangda Tan commented on YARN-4292: -- Looks good, +1, will commit in a few days if no opposite opinions.

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036654#comment-15036654 ] Li Lu commented on YARN-3623: - Hi [~Naganarasimha] sorry for the late reply (just came back from a vacation).

[jira] [Updated] (YARN-4405) Support node label store in non-appendable file system

[ https://issues.apache.org/jira/browse/YARN-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4405: - Attachment: YARN-4405.2.patch Attached ver.2 patch fixed test failures and findbug warnings. > Support

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

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

[jira] [Commented] (YARN-4413) Nodes in the includes list should not be listed as decommissioned in the UI

[ https://issues.apache.org/jira/browse/YARN-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036643#comment-15036643 ] Kuhu Shukla commented on YARN-4413: --- Thanks for reporting this [~templedf]. Was a node refresh done after

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036616#comment-15036616 ] Kuhu Shukla commented on YARN-4406: --- I agree. I was thinking about that too. During {{registerwithRM()}}

[jira] [Commented] (YARN-4293) ResourceUtilization should be a part of yarn node CLI

[ https://issues.apache.org/jira/browse/YARN-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036630#comment-15036630 ] Wangda Tan commented on YARN-4293: -- Thanks [~sunilg]. [~kasha], I found the biggest change of this patch

[jira] [Commented] (YARN-4413) Nodes in the includes list should not be listed as decommissioned in the UI

[ https://issues.apache.org/jira/browse/YARN-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036645#comment-15036645 ] Daniel Templeton commented on YARN-4413: That's what I was thinking. > Nodes in the includes list

[jira] [Commented] (YARN-4293) ResourceUtilization should be a part of yarn node CLI

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

[jira] [Commented] (YARN-4413) Nodes in the includes list should not be listed as decommissioned in the UI

[ https://issues.apache.org/jira/browse/YARN-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036644#comment-15036644 ] Daniel Templeton commented on YARN-4413: Yes. The refresh marks nodes newly added to the excludes

[jira] [Commented] (YARN-3840) Resource Manager web ui issue when sorting application by id (with application having id > 9999)

[ https://issues.apache.org/jira/browse/YARN-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036708#comment-15036708 ] Jian He commented on YARN-3840: --- latest patch looks good to me, thanks [~varun_saxena], > Resource Manager

[jira] [Commented] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

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

[jira] [Updated] (YARN-2575) Consider creating separate ACLs for Reservation create/update/delete ops

[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-2575: - Assignee: Sean Po (was: Subru Krishnan) > Consider creating separate ACLs for Reservation

[jira] [Commented] (YARN-4411) ResourceManager IllegalArgumentException error

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037003#comment-15037003 ] yarntime commented on YARN-4411: Hi Naganarasimha G R, thank you very much. > ResourceManager

[jira] [Commented] (YARN-4411) ResourceManager IllegalArgumentException error

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037008#comment-15037008 ] yarntime commented on YARN-4411: OK, thank you very much. > ResourceManager IllegalArgumentException error

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036968#comment-15036968 ] Hudson commented on YARN-4398: -- ABORTED: Integrated in Hadoop-Hdfs-trunk-Java8 #658 (See

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036979#comment-15036979 ] Sidharta Seethana commented on YARN-4309: - hi [~vvasudev], I am using the find command that you

[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037185#comment-15037185 ] Xianyin Xin commented on YARN-4403: --- And will provide new patch of YARN-4177 once this is in. >

[jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037217#comment-15037217 ] Sunil G commented on YARN-4389: --- Test case failures are known ones. And has separate tickets to handle the

[jira] [Commented] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037424#comment-15037424 ] Konstantinos Karanasos commented on YARN-2885: -- Adding some more on point #2 (I agree with the

[jira] [Commented] (YARN-4361) Total resource count mistake:NodeRemovedSchedulerEvent in ReconnectNodeTransition will reduce the newNode.getTotalCapability() in Multi-thread model

[ https://issues.apache.org/jira/browse/YARN-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037226#comment-15037226 ] jialei weng commented on YARN-4361: --- yes, I check the patch, it can also the issue. Thanks. > Total

[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037284#comment-15037284 ] Xianyin Xin commented on YARN-4403: --- Thanks, [~sunilg]. > (AM/NM/Container)LivelinessMonitor should use

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037381#comment-15037381 ] NING DING commented on YARN-4398: - [~jianhe], thank you. > Yarn recover functionality causes the cluster

[jira] [Commented] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037404#comment-15037404 ] Konstantinos Karanasos commented on YARN-2885: -- Thank you for the patch, [~asuresh]. Adding

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037418#comment-15037418 ] Varun Vasudev commented on YARN-4309: - bq. do we need to worry about -L following links outside of the

[jira] [Commented] (YARN-4413) Nodes in the includes list should not be listed as decommissioned in the UI

[ https://issues.apache.org/jira/browse/YARN-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037232#comment-15037232 ] Sunil G commented on YARN-4413: --- Hi [~templedf] Thank you for raising this ticket. As you mentioned, I could

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037280#comment-15037280 ] Naganarasimha G R commented on YARN-4392: - [~xgong], bq, Will it cause any issue if the APP_CREATED

[jira] [Resolved] (YARN-4397) if this addAll() function`s params is fault? @NodeListManager#getUnusableNodes()

[ https://issues.apache.org/jira/browse/YARN-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Yuan resolved YARN-4397. - Resolution: Not A Problem > if this addAll() function`s params is fault? >

[jira] [Commented] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037386#comment-15037386 ] Arun Suresh commented on YARN-2885: --- Thank you for the review [~leftnoteasy] !! let me try to clarify

[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037180#comment-15037180 ] Xianyin Xin commented on YARN-4403: --- hi [~djp], this is a good suggestion, and YARN-4177 provides some

[jira] [Updated] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brook Zhou updated YARN-4002: - Attachment: YARN-4002-v0.patch Added a patch for this. > make ResourceTrackerService.nodeHeartbeat more

[jira] [Commented] (YARN-4405) Support node label store in non-appendable file system

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

[jira] [Commented] (YARN-2877) Extend YARN to support distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037335#comment-15037335 ] Konstantinos Karanasos commented on YARN-2877: -- Thank you for the detailed comments,

[jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037208#comment-15037208 ] Sunil G commented on YARN-4403: --- Thanks [~xinxianyin] for updating this, I missed this somehow. It seems like

[jira] [Resolved] (YARN-4361) Total resource count mistake:NodeRemovedSchedulerEvent in ReconnectNodeTransition will reduce the newNode.getTotalCapability() in Multi-thread model

[ https://issues.apache.org/jira/browse/YARN-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jialei weng resolved YARN-4361. --- Resolution: Duplicate > Total resource count mistake:NodeRemovedSchedulerEvent in >

[jira] [Commented] (YARN-4340) Add "list" API to reservation system

[ https://issues.apache.org/jira/browse/YARN-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036873#comment-15036873 ] Subru Krishnan commented on YARN-4340: -- Thinking more about it, I am not sure we should have user in

[jira] [Commented] (YARN-2877) Extend YARN to support distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036916#comment-15036916 ] Wangda Tan commented on YARN-2877: -- Thanks [~kkaranasos], [~asuresh], I just caught up with latest design

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036857#comment-15036857 ] Robert Kanter commented on YARN-4408: - Test failure looks unrelated. > NodeManager still reports

[jira] [Commented] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036864#comment-15036864 ] Wangda Tan commented on YARN-4225: -- Thanks [~eepayne], bq. The use case is a newer client is querying an

[jira] [Updated] (YARN-4409) Fix javadoc and checkstyle issues in timelineservice code

[ https://issues.apache.org/jira/browse/YARN-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4409: --- Description: There are a large number of javadoc and checkstyle issues currently open in

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

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

[jira] [Resolved] (YARN-4410) hadoop

[ https://issues.apache.org/jira/browse/YARN-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-4410. - Resolution: Invalid It looks to be created by mistake. Closing as invalid. > hadoop >

[jira] [Created] (YARN-4411) ResourceManager IllegalArgumentException error

yarntime created YARN-4411: -- Summary: ResourceManager IllegalArgumentException error Key: YARN-4411 URL: https://issues.apache.org/jira/browse/YARN-4411 Project: Hadoop YARN Issue Type: Bug

  1   2   >