[jira] [Updated] (YARN-3662) Federation StateStore APIs

[ https://issues.apache.org/jira/browse/YARN-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3662: - Attachment: YARN-3662-YARN-2915-v1.patch Attaching v1 of the Federation StateStore APIs. >

[jira] [Updated] (YARN-4862) Handle duplicate completed containers in RMNodeImpl

[ https://issues.apache.org/jira/browse/YARN-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4862: Attachment: 0003-YARN-4862.patch Updating the rebased patch fixing review comments from

[jira] [Commented] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc/findbugs build

[ https://issues.apache.org/jira/browse/YARN-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352401#comment-15352401 ] Subru Krishnan commented on YARN-5300: -- Thanks [~curino] for the review. The test case failure is

[jira] [Updated] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc/findbugs build

[ https://issues.apache.org/jira/browse/YARN-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-5300: - Summary: Exclude generated federation protobuf sources from YARN Javadoc/findbugs build (was:

[jira] [Commented] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc build

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

[jira] [Commented] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc build

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

[jira] [Commented] (YARN-2497) Changes for fair scheduler to support allocate resource respect labels

[ https://issues.apache.org/jira/browse/YARN-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352287#comment-15352287 ] stefanlee commented on YARN-2497: - 2.6 version does not support it. > Changes for fair scheduler to

[jira] [Updated] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-5300: - Attachment: YARN-5300-v2.patch Uploading v2 patch which fixes multiple package exclusion and adds

[jira] [Commented] (YARN-5036) RM crashed with NPE while handling CONTAINER_EXPIRED event

[ https://issues.apache.org/jira/browse/YARN-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352259#comment-15352259 ] GuangSheng Liu commented on YARN-5036: -- Need sync AsyncScheduleThread‘s schedule method? > RM crashed

[jira] [Commented] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc build

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

[jira] [Commented] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc build

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

[jira] [Commented] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

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

[jira] [Updated] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

[ https://issues.apache.org/jira/browse/YARN-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gergely Novák updated YARN-5227: Attachment: YARN-5227.002.patch > yarn logs command: no need to specify -applicationId when

[jira] [Commented] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

[ https://issues.apache.org/jira/browse/YARN-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352196#comment-15352196 ] Gergely Novák commented on YARN-5227: - Thanks for the comments, updated patch #2 with the suggested

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

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

[jira] [Commented] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352155#comment-15352155 ] Carlo Curino commented on YARN-5300: +1 for commit in the {{YARN-2915}} branch, as in YARN-5132 this

[jira] [Updated] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-5300: - Attachment: YARN-5300-v1.patch Attaching a simple patch that excludes generated federation

[jira] [Created] (YARN-5300) Exclude generated federation protobuf sources from YARN Javadoc build

Subru Krishnan created YARN-5300: Summary: Exclude generated federation protobuf sources from YARN Javadoc build Key: YARN-5300 URL: https://issues.apache.org/jira/browse/YARN-5300 Project: Hadoop

[jira] [Commented] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

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

[jira] [Comment Edited] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352107#comment-15352107 ] Yufei Gu edited comment on YARN-4212 at 6/28/16 12:15 AM: -- Thanks [~kasha] for the

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352107#comment-15352107 ] Yufei Gu commented on YARN-4212: I uploaded the patch 004 for all the comments. > FairScheduler: Parent

[jira] [Commented] (YARN-1042) add ability to specify affinity/anti-affinity in container requests

[ https://issues.apache.org/jira/browse/YARN-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352072#comment-15352072 ] Wangda Tan commented on YARN-1042: -- Hi [~cheersyang], thanks for the design doc, patch and ideas. I think

[jira] [Commented] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

[ https://issues.apache.org/jira/browse/YARN-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352066#comment-15352066 ] Xuan Gong commented on YARN-5227: - [~GergelyNovak] Thanks for working on this. The logic looks good to me.

[jira] [Assigned] (YARN-1042) add ability to specify affinity/anti-affinity in container requests

[ https://issues.apache.org/jira/browse/YARN-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reassigned YARN-1042: Assignee: Wangda Tan (was: Arun C Murthy) > add ability to specify affinity/anti-affinity in

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352032#comment-15352032 ] Junping Du commented on YARN-5296: -- Thanks [~templedf] for review and comments! I think

[jira] [Commented] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352026#comment-15352026 ] Jian He commented on YARN-5294: --- Uploaded a patch which pass in the remote address and forwarded address into

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294.3.patch > Pass remote ip address down to YarnAuthorizationProvider >

[jira] [Commented] (YARN-5262) Optimize sending RMNodeFinishedContainersPulledByAMEvent for every AM heartbeat

[ https://issues.apache.org/jira/browse/YARN-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351995#comment-15351995 ] Jian He commented on YARN-5262: --- lgtm, good findings ! > Optimize sending

[jira] [Updated] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5270: - Attachment: YARN-5270-branch-2.8.003.patch Attached patch for branch-2.8 > Solve miscellaneous issues

[jira] [Commented] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

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

[jira] [Updated] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5270: - Attachment: YARN-5270-branch-2.003.patch Thanks [~jianhe], attached ver.3 patch for branch-2. > Solve

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

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

[jira] [Commented] (YARN-5297) Avoid printing a stack trace when recovering an app after the RM restarts

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

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351894#comment-15351894 ] Daniel Templeton commented on YARN-5296: Thanks for the patch, [~djp]. Looks to me like that patch

[jira] [Updated] (YARN-5294) Pass remote ip address down to YarnAuthorizationProvider

[ https://issues.apache.org/jira/browse/YARN-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5294: -- Attachment: YARN-5294.2.patch > Pass remote ip address down to YarnAuthorizationProvider >

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351859#comment-15351859 ] Jian He commented on YARN-5296: --- lgtm > NMs going OutOfMemory because ContainerMetrics leak in

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351854#comment-15351854 ] Jian He commented on YARN-5270: --- QueueMetrics - the getters for availableVCores, pendingVCores ,

[jira] [Commented] (YARN-5227) yarn logs command: no need to specify -applicationId when specifying containerId

[ https://issues.apache.org/jira/browse/YARN-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351816#comment-15351816 ] Jian He commented on YARN-5227: --- i see, thanks for the explanation ! > yarn logs command: no need to specify

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351814#comment-15351814 ] Junping Du commented on YARN-5296: -- CC [~jianhe] > NMs going OutOfMemory because ContainerMetrics leak in

[jira] [Updated] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-5296: - Attachment: YARN-5296.patch Thanks [~karams] for reporting the issue. Upload a patch to fix this issue

[jira] [Updated] (YARN-5297) Avoid printing a stack trace when recovering an app after the RM restarts

[ https://issues.apache.org/jira/browse/YARN-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-5297: - Attachment: (was: YARN-5297.patch) > Avoid printing a stack trace when recovering an app after the RM

[jira] [Updated] (YARN-5297) Avoid printing a stack trace when recovering an app after the RM restarts

[ https://issues.apache.org/jira/browse/YARN-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-5297: - Attachment: YARN-5297.patch > Avoid printing a stack trace when recovering an app after the RM restarts >

[jira] [Commented] (YARN-5174) [documentation] several updates/corrections to timeline service documentation

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

[jira] [Commented] (YARN-5293) Disable preemption per queue per partition

[ https://issues.apache.org/jira/browse/YARN-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351650#comment-15351650 ] Jonathan Hung commented on YARN-5293: - Thanks for the comments, [~Naganarasimha] and [~sunilg]. My

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

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

[jira] [Updated] (YARN-5174) [documentation] several updates/corrections to timeline service documentation

[ https://issues.apache.org/jira/browse/YARN-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-5174: -- Attachment: YARN-5174-YARN-2928.09.patch Posted patch v.9 correcting the typo. > [documentation]

[jira] [Commented] (YARN-4280) CapacityScheduler reservations may not prevent indefinite postponement on a busy cluster

[ https://issues.apache.org/jira/browse/YARN-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351537#comment-15351537 ] Wangda Tan commented on YARN-4280: -- If I understand correctly, current logic is: For Application, if it

[jira] [Commented] (YARN-5298) Mount usercache and NM filecache directories into Docker container

[ https://issues.apache.org/jira/browse/YARN-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351517#comment-15351517 ] Sidharta Seethana commented on YARN-5298: - Thanks for filing this ticket, [~vvasudev] ! I'll take a

[jira] [Assigned] (YARN-5298) Mount usercache and NM filecache directories into Docker container

[ https://issues.apache.org/jira/browse/YARN-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana reassigned YARN-5298: --- Assignee: Sidharta Seethana > Mount usercache and NM filecache directories into

[jira] [Created] (YARN-5299) Log Docker run command when container fails

Varun Vasudev created YARN-5299: --- Summary: Log Docker run command when container fails Key: YARN-5299 URL: https://issues.apache.org/jira/browse/YARN-5299 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-5299) Log Docker run command when container fails

[ https://issues.apache.org/jira/browse/YARN-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reassigned YARN-5299: --- Assignee: Varun Vasudev > Log Docker run command when container fails >

[jira] [Created] (YARN-5298) Mount usercache and NM filecache directories into Docker container

Varun Vasudev created YARN-5298: --- Summary: Mount usercache and NM filecache directories into Docker container Key: YARN-5298 URL: https://issues.apache.org/jira/browse/YARN-5298 Project: Hadoop YARN

[jira] [Updated] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-5047: - Attachment: YARN-5047.005.patch Adding same patch for Jenkins run. > Refactor nodeUpdate across

[jira] [Comment Edited] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351488#comment-15351488 ] Daniel Zhi edited comment on YARN-4676 at 6/27/16 5:58 PM: --- Our team attended

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351488#comment-15351488 ] Daniel Zhi commented on YARN-4676: -- Our team attended Hadoop summit 2014 but there was no plan to attend

[jira] [Assigned] (YARN-5297) Avoid printing a stack trace when recovering an app after the RM restarts

[ https://issues.apache.org/jira/browse/YARN-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-5297: Assignee: Junping Du > Avoid printing a stack trace when recovering an app after the RM restarts >

[jira] [Created] (YARN-5297) Avoid printing a stack trace when recovering an app after the RM restarts

Siddharth Seth created YARN-5297: Summary: Avoid printing a stack trace when recovering an app after the RM restarts Key: YARN-5297 URL: https://issues.apache.org/jira/browse/YARN-5297 Project:

[jira] [Commented] (YARN-5295) YARN queue-mappings to check Queue is present before submitting job

[ https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351450#comment-15351450 ] Prabhu Joseph commented on YARN-5295: - Yes, doing Sanity Check 1 and 2 well before in getMappedQueue is

[jira] [Commented] (YARN-5295) YARN queue-mappings to check Queue is present before submitting job

[ https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351384#comment-15351384 ] Sunil G commented on YARN-5295: --- Thanks [~Prabhu Joseph] for the clarification. Yes, we select a queue and

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351356#comment-15351356 ] Rajesh Balamohan commented on YARN-5296: Based on offline conversation with [~karams], i have

[jira] [Comment Edited] (YARN-5295) YARN queue-mappings to check Queue is present before submitting job

[ https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351347#comment-15351347 ] Prabhu Joseph edited comment on YARN-5295 at 6/27/16 4:25 PM: -- Hi [~sunilg],

[jira] [Updated] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Balamohan updated YARN-5296: --- Assignee: Junping Du > NMs going OutOfMemory because ContainerMetrics leak in

[jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351351#comment-15351351 ] Karam Singh commented on YARN-5296: --- >From offline discussion with [~djp] Root cause is in YARN-4811

[jira] [Comment Edited] (YARN-5295) YARN queue-mappings to check Queue is present before submitting job

[ https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351347#comment-15351347 ] Prabhu Joseph edited comment on YARN-5295 at 6/27/16 4:23 PM: -- Hi [~sunilg],

[jira] [Created] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl

Karam Singh created YARN-5296: - Summary: NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl Key: YARN-5296 URL: https://issues.apache.org/jira/browse/YARN-5296 Project: Hadoop

[jira] [Commented] (YARN-5295) YARN queue-mappings to check Queue is present before submitting job

[ https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351347#comment-15351347 ] Prabhu Joseph commented on YARN-5295: - [~sunilg] Yes, if test queue is present, the application

[jira] [Commented] (YARN-5279) Potential Container leak in NM in preemption flow

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

[jira] [Commented] (YARN-5174) [documentation] several updates/corrections to timeline service documentation

[ https://issues.apache.org/jira/browse/YARN-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350891#comment-15350891 ] Varun Saxena commented on YARN-5174: There is a typo in the patch. {noformat} 92 Most

[jira] [Commented] (YARN-5293) Disable preemption per queue per partition

[ https://issues.apache.org/jira/browse/YARN-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350860#comment-15350860 ] Sunil G commented on YARN-5293: --- Adding to what [~Naganarasimha Garla] has mentioned and based on the

[jira] [Commented] (YARN-5293) Disable preemption per queue per partition

[ https://issues.apache.org/jira/browse/YARN-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350818#comment-15350818 ] Naganarasimha G R commented on YARN-5293: - [~jhung], Makes Sense to disable Per queue per partition

[jira] [Updated] (YARN-5279) Potential Container leak in NM in preemption flow

[ https://issues.apache.org/jira/browse/YARN-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5279: Attachment: 0001-YARN-5279.patch Updated the patch for informing RMNodeImple that untracked

[jira] [Commented] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

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

[jira] [Commented] (YARN-5295) YARN queue-mappings to check Queue is present before submitting job

[ https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350703#comment-15350703 ] Sunil G commented on YARN-5295: --- Hi [~Prabhu Joseph] Thanks for raising this issue. Couple of doubts here,

[jira] [Commented] (YARN-5261) Lease/Reclaim Extension to Yarn

[ https://issues.apache.org/jira/browse/YARN-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350660#comment-15350660 ] Sunil G commented on YARN-5261: --- Hi It will be better if you could share a more details about this work such

[jira] [Updated] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3933: -- Attachment: YARN-3933.004.patch Hi [~guoshiwei] I tried to update your patch with minor changes as we discussed

[jira] [Updated] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3933: -- Assignee: Shiwei Guo (was: Sunil G) > Race condition when calling AbstractYarnScheduler.completedContainer. >

[jira] [Assigned] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-3933: - Assignee: Sunil G (was: Shiwei Guo) > Race condition when calling