[jira] [Commented] (YARN-3534) Collect memory/cpu usage on the node

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

[jira] [Resolved] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena resolved YARN-4054. Resolution: Invalid Fix findbugs warnings in YARN-2928 branch

[jira] [Updated] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3045: Attachment: YARN-3045-YARN-2928.011.patch [~djp] [~sjlee0], Have avoided the findbugs

[jira] [Commented] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

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

[jira] [Reopened] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reopened YARN-4054: Fix findbugs warnings in YARN-2928 branch -

[jira] [Updated] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4054: --- Issue Type: Bug (was: Sub-task) Parent: (was: YARN-2928) Fix findbugs warnings in

[jira] [Resolved] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena resolved YARN-4054. Resolution: Invalid This is not an issue in branch. Earlier warnings I found might be due to a

[jira] [Commented] (YARN-3534) Collect memory/cpu usage on the node

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698162#comment-14698162 ] Karthik Kambatla commented on YARN-3534: The latest patches (v17) don't seem to

[jira] [Commented] (YARN-4043) Unnecessary warning message : an attempt to override final parameter:

[ https://issues.apache.org/jira/browse/YARN-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698187#comment-14698187 ] Karthik Kambatla commented on YARN-4043: Would like to understand better why the

[jira] [Updated] (YARN-4051) ContainerKillEvent is lost when container is In New State and is recovering

[ https://issues.apache.org/jira/browse/YARN-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-4051: --- Attachment: YARN-4051.02.patch fix check style errors ContainerKillEvent is lost when container is In New

[jira] [Commented] (YARN-4053) Change the way metric values are stored in HBase Storage

[ https://issues.apache.org/jira/browse/YARN-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698209#comment-14698209 ] Varun Saxena commented on YARN-4053: Naga, yes double can also be used. But the

[jira] [Commented] (YARN-4051) ContainerKillEvent is lost when container is In New State and is recovering

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

[jira] [Updated] (YARN-4051) ContainerKillEvent is lost when container is In New State and is recovering

[ https://issues.apache.org/jira/browse/YARN-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4051: --- Priority: Critical (was: Major) ContainerKillEvent is lost when container is In New State

[jira] [Commented] (YARN-4039) New AM instances waste resource by waiting only for resource availability when all available resources are already used

[ https://issues.apache.org/jira/browse/YARN-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698183#comment-14698183 ] Karthik Kambatla commented on YARN-4039: maxRunningApps and maxAMShare are configs

[jira] [Commented] (YARN-3924) Submitting an application to standby ResourceManager should respond better than Connection Refused

[ https://issues.apache.org/jira/browse/YARN-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698158#comment-14698158 ] Karthik Kambatla commented on YARN-3924: bq. not somehow making clear about two

[jira] [Commented] (YARN-2154) FairScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698178#comment-14698178 ] Karthik Kambatla commented on YARN-2154: [~bpodgursky] - I was only observing what

[jira] [Commented] (YARN-4039) New AM instances waste resource by waiting only for resource availability when all available resources are already used

[ https://issues.apache.org/jira/browse/YARN-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698185#comment-14698185 ] Karthik Kambatla commented on YARN-4039: Another simple way to handle this would be

[jira] [Commented] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698201#comment-14698201 ] Naganarasimha G R commented on YARN-3045: - Have run the findbugs manually most of

[jira] [Updated] (YARN-3986) getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

[ https://issues.apache.org/jira/browse/YARN-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3986: --- Attachment: YARN-3986.03.patch Rebased the patch as its no longer applying getTransferredContainers

[jira] [Resolved] (YARN-683) Class MiniYARNCluster not found when starting the minicluster

[ https://issues.apache.org/jira/browse/YARN-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gera Shegalov resolved YARN-683. Resolution: Duplicate Closing as a dup because HADOOP-9891 now documents this workaround Class

[jira] [Commented] (YARN-3986) getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

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

[jira] [Reopened] (YARN-3952) Fix new findbugs warnings in resourcemanager in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reopened YARN-3952: Fix new findbugs warnings in resourcemanager in YARN-2928 branch

[jira] [Resolved] (YARN-3952) Fix new findbugs warnings in resourcemanager in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena resolved YARN-3952. Resolution: Duplicate Fix new findbugs warnings in resourcemanager in YARN-2928 branch

[jira] [Commented] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698241#comment-14698241 ] Varun Saxena commented on YARN-4054: [~djp], I think we can create one JIRA for

[jira] [Updated] (YARN-3937) Introducing CANCEL_PREEMPTION event to notify Scheduler and AM when a container is no longer to be preempted

[ https://issues.apache.org/jira/browse/YARN-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3937: -- Summary: Introducing CANCEL_PREEMPTION event to notify Scheduler and AM when a container is no longer to be

[jira] [Created] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

Varun Saxena created YARN-4054: -- Summary: Fix findbugs warnings in YARN-2928 branch Key: YARN-4054 URL: https://issues.apache.org/jira/browse/YARN-4054 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698239#comment-14698239 ] Varun Saxena commented on YARN-4054: Found 2 findbugs warnings in timelineservice

[jira] [Updated] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4054: --- Issue Type: Sub-task (was: Bug) Parent: YARN-2928 Fix findbugs warnings in YARN-2928 branch

[jira] [Commented] (YARN-4054) Fix findbugs warnings in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698248#comment-14698248 ] Varun Saxena commented on YARN-4054: Or maybe reopen YARN-3952 and change title to

[jira] [Commented] (YARN-3534) Collect memory/cpu usage on the node

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698419#comment-14698419 ] Inigo Goiri commented on YARN-3534: --- I uploaded 17 twice instead of 18... sorry.

[jira] [Updated] (YARN-3534) Collect memory/cpu usage on the node

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Inigo Goiri updated YARN-3534: -- Attachment: YARN-3534-18.patch Fixed xml defaults. Collect memory/cpu usage on the node