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

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043844#comment-15043844 ] Naganarasimha G R commented on YARN-4411: - Hi [~yarntime], This issue is not related to the

[jira] [Commented] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043940#comment-15043940 ] Sunil G commented on YARN-4416: --- A typo Almost all api's exposed from LeafQueue is used with Lock from Queue

[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=15043921#comment-15043921 ] Sunil G commented on YARN-4293: --- Hi [~Naganarasimha Garla] Extremely sorry for the mixed up. I was trying to

[jira] [Commented] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043909#comment-15043909 ] Sunil G commented on YARN-4416: --- bq.i have added locks for the access of schedulableEntities in

[jira] [Commented] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043932#comment-15043932 ] Sunil G commented on YARN-4416: --- Sorry, I was not very clear in my earlier comments. Almost all api's

[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=15043953#comment-15043953 ] Naganarasimha G R commented on YARN-4304: - [~sunilg], Tested the latest patch on the trunk and

[jira] [Commented] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043941#comment-15043941 ] Naganarasimha G R commented on YARN-4416: - [~sunilg], bq. Hence with this new lock, we are getting

[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=15043919#comment-15043919 ] Naganarasimha G R commented on YARN-4293: - hi [~sunilg], Seems like you have handled scope of

[jira] [Resolved] (YARN-4291) ResourceUtilization should be a part of NodeReport API.

[ https://issues.apache.org/jira/browse/YARN-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R resolved YARN-4291. - Resolution: Done Scope of this jira has been handled as part of YARN-4293... Hence closing

[jira] [Commented] (YARN-4072) ApplicationHistoryServer, WebAppProxyServer, NodeManager and ResourceManager to support JvmPauseMonitor as a service

[ https://issues.apache.org/jira/browse/YARN-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043971#comment-15043971 ] Steve Loughran commented on YARN-4072: -- +1 > ApplicationHistoryServer, WebAppProxyServer, NodeManager

[jira] [Updated] (YARN-3367) Replace starting a separate thread for post entity with event loop in TimelineClient

[ https://issues.apache.org/jira/browse/YARN-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3367: Attachment: YARN-3367-feature-YARN-2928.v1.002.patch Thanks for the clarification [~djp], So

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

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043881#comment-15043881 ] yarntime commented on YARN-4411: ok, I get it, thank you for your help. > ResourceManager

[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=15043896#comment-15043896 ] Hadoop QA commented on YARN-2885: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

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

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043859#comment-15043859 ] yarntime commented on YARN-4411: Hi [~Naganarasimha] thanks for your reply, and I want to know is there any

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

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043835#comment-15043835 ] yarntime commented on YARN-4411: Hi [~djp], Would you please help me with this problem? Thank you very

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

[ https://issues.apache.org/jira/browse/YARN-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043878#comment-15043878 ] Naganarasimha G R commented on YARN-4411: - you cant avoid, as its caused by existing code. >

[jira] [Commented] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044307#comment-15044307 ] Sunil G commented on YARN-4416: --- I also agree that we need to make ordering policy independent. But a fail

[jira] [Commented] (YARN-3367) Replace starting a separate thread for post entity with event loop in TimelineClient

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

[jira] [Commented] (YARN-4381) Add container launchEvent and container localizeFailed metrics in container

[ https://issues.apache.org/jira/browse/YARN-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044261#comment-15044261 ] Lin Yiqun commented on YARN-4381: - [~djp], do you have some time to review my patch or what else can I do

[jira] [Commented] (YARN-4348) ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread

[ https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044258#comment-15044258 ] Tsuyoshi Ozawa commented on YARN-4348: -- [~jianhe] could you take a look? >

[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=15044310#comment-15044310 ] Sunil G commented on YARN-4304: --- Thank you [~Naganarasimha] for helping in verifying the patch. Yes, I will

[jira] [Created] (YARN-4426) unhealthy disk makes NM LOST

sandflee created YARN-4426: -- Summary: unhealthy disk makes NM LOST Key: YARN-4426 URL: https://issues.apache.org/jira/browse/YARN-4426 Project: Hadoop YARN Issue Type: Bug Reporter:

[jira] [Commented] (YARN-4424) YARN CLI command hangs

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

[jira] [Commented] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044316#comment-15044316 ] Naganarasimha G R commented on YARN-4416: - [~sunilg], Hmm true, but any other way to avoid sync

[jira] [Updated] (YARN-4424) YARN CLI command hangs

[ https://issues.apache.org/jira/browse/YARN-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4424: -- Attachment: YARN-4424.1.patch The patch removes the read lock in RMAppImpl#getFinalApplicationStatus as I think

[jira] [Commented] (YARN-4424) YARN CLI command hangs

[ https://issues.apache.org/jira/browse/YARN-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044141#comment-15044141 ] Jian He commented on YARN-4424: --- This is a similar problem to YARN-2594 Thread 1 {code} Thread 53785: (state

[jira] [Updated] (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:all-tabpanel ] Arun Suresh updated YARN-2885: -- Attachment: YARN-2885-yarn-2877.full-2.patch Updating patch: # The earlier patch had changed the

[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.007.patch Uploaded a new patch with clarifications on following symlinks 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=15044404#comment-15044404 ] Wangda Tan commented on YARN-4309: -- [~vvasudev], Thanks for reply, make sense to me. Few comments: -

[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=15044406#comment-15044406 ] Hadoop QA commented on YARN-4309: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044361#comment-15044361 ] Varun Vasudev commented on YARN-3542: - All the existing configurations will continue to work as is. The

[jira] [Commented] (YARN-4415) Scheduler Web Ui shows max capacity for the queue is 100% but when we submit application doesnt get assigned

[ https://issues.apache.org/jira/browse/YARN-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044498#comment-15044498 ] Xianyin Xin commented on YARN-4415: --- Sorry for the late, [~Naganarasimha]. I don't know i understand