[jira] [Updated] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3932: --- Attachment: 0005-YARN-3932.patch Attaching patch after whitespace fix > SchedulerApplicationAt

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634513#comment-14634513 ] Siqi Li commented on YARN-3944: --- [~zxu] Thanks for your quick response, I think the reason we

[jira] [Commented] (YARN-3026) Move application-specific container allocation logic from LeafQueue to FiCaSchedulerApp

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

[jira] [Commented] (YARN-3645) ResourceManager can't start success if attribute value of "aclSubmitApps" is null in fair-scheduler.xml

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

[jira] [Commented] (YARN-2003) Support for Application priority : Changes in RM and Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634483#comment-14634483 ] Jian He commented on YARN-2003: --- lgtm > Support for Application priority : Changes in RM and

[jira] [Commented] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634423#comment-14634423 ] Bibin A Chundatt commented on YARN-3932: Test is skipped for {{org.apache.hadoop.y

[jira] [Commented] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634417#comment-14634417 ] He Tianyi commented on YARN-3903: - Hi, I believe these whitespaces & codestyle errors are

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634416#comment-14634416 ] zhihai xu commented on YARN-3944: - Hi [~l201514], thanks for the information. I am not sure

[jira] [Commented] (YARN-3931) default-node-label-expression doesn’t apply when an application is submitted by RM rest api

[ https://issues.apache.org/jira/browse/YARN-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634406#comment-14634406 ] kyungwan nam commented on YARN-3931: "application-name", "application-type” are empty s

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634383#comment-14634383 ] Sangjin Lee commented on YARN-3908: --- I'd like to propose closing this issue with the curr

[jira] [Assigned] (YARN-3645) ResourceManager can't start success if attribute value of "aclSubmitApps" is null in fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Liptak reassigned YARN-3645: -- Assignee: Gabor Liptak > ResourceManager can't start success if attribute value of "aclSubmitAp

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634352#comment-14634352 ] Zhijie Shen commented on YARN-3049: --- [~sjlee0], yeah, for POC purpose, I temporally do fl

[jira] [Updated] (YARN-3645) ResourceManager can't start success if attribute value of "aclSubmitApps" is null in fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Liptak updated YARN-3645: --- Attachment: YARN-3645.4.patch Brought patch current > ResourceManager can't start success if attribut

[jira] [Assigned] (YARN-2019) Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-2019: - Assignee: Jian He > Retrospect on decision of making RM crashed if any exception throw in > ZKRMStateStor

[jira] [Commented] (YARN-2019) Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634333#comment-14634333 ] Jian He commented on YARN-2019: --- I agree that we should provide an option to not crash RM if

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634326#comment-14634326 ] Sangjin Lee commented on YARN-3049: --- I do see that you're adding a call to {{BufferedMuta

[jira] [Updated] (YARN-3026) Move application-specific container allocation logic from LeafQueue to FiCaSchedulerApp

[ https://issues.apache.org/jira/browse/YARN-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3026: - Attachment: YARN-3026.3.patch Attached ver.3 patch, reworked on the patch, since we have a lot of code cha

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634306#comment-14634306 ] Naganarasimha G R commented on YARN-3945: - Also typo in the documentation, it has 2

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634298#comment-14634298 ] Naganarasimha G R commented on YARN-3945: - As per the suggestion in the forum by [~

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634293#comment-14634293 ] Sangjin Lee commented on YARN-3908: --- Currently we're not calling {{BufferedMutator.flush(

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634286#comment-14634286 ] Siqi Li commented on YARN-3944: --- [~zxu], this is not a duplicate of YARN-3238(i.e. ConnectTim

[jira] [Created] (YARN-3945) maxApplicationsPerUser is wrongly calculated

Naganarasimha G R created YARN-3945: --- Summary: maxApplicationsPerUser is wrongly calculated Key: YARN-3945 URL: https://issues.apache.org/jira/browse/YARN-3945 Project: Hadoop YARN Issue Ty

[jira] [Updated] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: yARN-3920.001.patch Patch implements a threshold based on a ratio to the maximum sized co

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634234#comment-14634234 ] zhihai xu commented on YARN-3944: - Hi [~l201514], thanks for reporting this issue. Is this

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

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

[jira] [Commented] (YARN-3929) Uncleaning option for local app log files with log-aggregation feature

[ https://issues.apache.org/jira/browse/YARN-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634202#comment-14634202 ] Dongwook Kwon commented on YARN-3929: - The reason is we already had similar tool as log

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634200#comment-14634200 ] Zhijie Shen commented on YARN-3908: --- I set up hbase-1.0.1.1 as a single node cluster on l

[jira] [Updated] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3049: -- Attachment: YARN-3049-WIP.3.patch Upload a new WIP patch with some bug fixes, including the the two menti

[jira] [Commented] (YARN-3853) Add docker container runtime support to LinuxContainterExecutor

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

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3944: -- Attachment: YARN-3944.v1.patch > Connection refused to nodemanagers are retried at multiple levels >

[jira] [Assigned] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reassigned YARN-3944: - Assignee: Siqi Li > Connection refused to nodemanagers are retried at multiple levels > --

[jira] [Updated] (YARN-3816) [Aggregation] App-level Aggregation for YARN system metrics

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3816: - Attachment: YARN-3816-poc-v2.patch Update poc patch to v2 to address some important feedback from Vinod, Sa

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3944: -- Description: This is related to YARN-3238. When NM is down, ipc client will get ConnectException. Caused by: ja

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3944: -- Affects Version/s: 2.6.0 > Connection refused to nodemanagers are retried at multiple levels > --

[jira] [Created] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

Siqi Li created YARN-3944: - Summary: Connection refused to nodemanagers are retried at multiple levels Key: YARN-3944 URL: https://issues.apache.org/jira/browse/YARN-3944 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3814) REST API implementation for getting raw entities in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634128#comment-14634128 ] Sangjin Lee commented on YARN-3814: --- bq. 1. Cluster ID is mandatory in YARN-3049 whereas

[jira] [Updated] (YARN-3853) Add docker container runtime support to LinuxContainterExecutor

[ https://issues.apache.org/jira/browse/YARN-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-3853: Attachment: YARN-3853.002.patch Uploading a new version of the patch based on code review fee

[jira] [Commented] (YARN-3853) Add docker container runtime support to LinuxContainterExecutor

[ https://issues.apache.org/jira/browse/YARN-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634107#comment-14634107 ] Sidharta Seethana commented on YARN-3853: - [~vvasudev] , thanks for the review. Reg

[jira] [Commented] (YARN-3929) Uncleaning option for local app log files with log-aggregation feature

[ https://issues.apache.org/jira/browse/YARN-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634103#comment-14634103 ] Vinod Kumar Vavilapalli commented on YARN-3929: --- [~dongwook], how do you perf

[jira] [Created] (YARN-3943) Use separate threshold configurations for disk-full detection and disk-not-full detection.

zhihai xu created YARN-3943: --- Summary: Use separate threshold configurations for disk-full detection and disk-not-full detection. Key: YARN-3943 URL: https://issues.apache.org/jira/browse/YARN-3943 Project:

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634079#comment-14634079 ] Vinod Kumar Vavilapalli commented on YARN-3942: --- Tx for posting this [~jlowe]

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634071#comment-14634071 ] Jason Lowe commented on YARN-3942: -- To setup for the Tez UI, yarn.timeline-service.entity

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634058#comment-14634058 ] Jason Lowe commented on YARN-3942: -- TEZ-2628 has the corresponding changes to allow Tez jo

[jira] [Updated] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3942: - Attachment: YARN-3942.001.patch This provides a timeline store plugin that allows posting of entities via a

[jira] [Created] (YARN-3942) Timeline store to read events from HDFS

Jason Lowe created YARN-3942: Summary: Timeline store to read events from HDFS Key: YARN-3942 URL: https://issues.apache.org/jira/browse/YARN-3942 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

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

[jira] [Commented] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633995#comment-14633995 ] Bibin A Chundatt commented on YARN-3932: CheckStyle issue is related to number of l

[jira] [Commented] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

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

[jira] [Updated] (YARN-3055) The token is not renewed properly if it's shared by jobs (oozie) in DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3055: -- Labels: 2.6.1-candidate (was: ) > The token is not renewed properly if it's shar

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633937#comment-14633937 ] Sangjin Lee commented on YARN-3908: --- bq. 1. The events have been written into metrics col

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633936#comment-14633936 ] Sangjin Lee commented on YARN-3908: --- The JIRA site seems offline right now. bq. 1. The e

[jira] [Updated] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3932: --- Attachment: 0004-YARN-3932.patch Attaching patch with merge for YARN-3939 and testcase for the

[jira] [Created] (YARN-3941) Proportional Preemption policy should try to avoid sending duplicate PREEMPT_CONTAINER event to scheduler

Sunil G created YARN-3941: - Summary: Proportional Preemption policy should try to avoid sending duplicate PREEMPT_CONTAINER event to scheduler Key: YARN-3941 URL: https://issues.apache.org/jira/browse/YARN-3941

[jira] [Updated] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3932: --- Attachment: 0003-YARN-3932.patch Attaching patch after merging YARN-3939 > SchedulerApplicatio

[jira] [Commented] (YARN-3939) CS schedule Userlevel resource usage shown is zero for NodeLabel partition

[ https://issues.apache.org/jira/browse/YARN-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633894#comment-14633894 ] Bibin A Chundatt commented on YARN-3939: [~leftnoteasy] will add the fix in YARN-39

[jira] [Commented] (YARN-3940) Application moveToQueue should check NodeLabel permission

[ https://issues.apache.org/jira/browse/YARN-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633881#comment-14633881 ] Bibin A Chundatt commented on YARN-3940: [~leftnoteasy] Thnks for comment will uplo

[jira] [Commented] (YARN-3940) Application moveToQueue should check NodeLabel permission

[ https://issues.apache.org/jira/browse/YARN-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633876#comment-14633876 ] Wangda Tan commented on YARN-3940: -- [~bibinchundatt], I agree with you. One approach is in

[jira] [Commented] (YARN-3939) CS schedule Userlevel resource usage shown is zero for NodeLabel partition

[ https://issues.apache.org/jira/browse/YARN-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633873#comment-14633873 ] Bibin A Chundatt commented on YARN-3939: Hi [~leftnoteasy] The fix was in two diffe

[jira] [Commented] (YARN-3940) Application moveToQueue should check NodeLabel permission

[ https://issues.apache.org/jira/browse/YARN-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633870#comment-14633870 ] Bibin A Chundatt commented on YARN-3940: [~leftnoteasy] IMO ,Since the destination

[jira] [Commented] (YARN-2003) Support for Application priority : Changes in RM and Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633864#comment-14633864 ] Wangda Tan commented on YARN-2003: -- Patch looks good to me, thanks for update [~sunilg].

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633857#comment-14633857 ] Zhijie Shen commented on YARN-3908: --- I found two more issues upon debugging the reader PO

[jira] [Commented] (YARN-3939) CS schedule Userlevel resource usage shown is zero for NodeLabel partition

[ https://issues.apache.org/jira/browse/YARN-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633855#comment-14633855 ] Wangda Tan commented on YARN-3939: -- [~bibinchundatt], thanks for working on this patch, th

[jira] [Commented] (YARN-3940) Application moveToQueue should check NodeLabel permission

[ https://issues.apache.org/jira/browse/YARN-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633847#comment-14633847 ] Wangda Tan commented on YARN-3940: -- I just converted this to sub-task of YARN-2492 for bet

[jira] [Updated] (YARN-3940) Application moveToQueue should check NodeLabel permission

[ https://issues.apache.org/jira/browse/YARN-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3940: - Issue Type: Sub-task (was: Bug) Parent: YARN-2492 > Application moveToQueue should check NodeLabel

[jira] [Updated] (YARN-3940) Application moveToQueue should check NodeLabel permission

[ https://issues.apache.org/jira/browse/YARN-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3940: - Environment: (was: Suse 11 Sp3) > Application moveToQueue should check NodeLabel permission >

[jira] [Commented] (YARN-3852) Add docker container support to container-executor

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

[jira] [Updated] (YARN-3940) Application moveToQueue should check NodeLabel permission

[ https://issues.apache.org/jira/browse/YARN-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3940: --- Description: Configure capacity scheduler Configure node label an submit application {{queue=A

[jira] [Updated] (YARN-3852) Add docker container support to container-executor

[ https://issues.apache.org/jira/browse/YARN-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abin Shahab updated YARN-3852: -- Attachment: YARN-3852-1.patch Code review fixes and refactoring > Add docker container support to contai

[jira] [Commented] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633737#comment-14633737 ] Jun Gong commented on YARN-3896: Failed test cases are not related. > RMNode transitioned

[jira] [Commented] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

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

[jira] [Commented] (YARN-3814) REST API implementation for getting raw entities in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633690#comment-14633690 ] Varun Saxena commented on YARN-3814: [~zjshen], [~sjlee0] had a look at YARN-3049. The

[jira] [Created] (YARN-3940) Application moveToQueue should check NodeLabel permission

Bibin A Chundatt created YARN-3940: -- Summary: Application moveToQueue should check NodeLabel permission Key: YARN-3940 URL: https://issues.apache.org/jira/browse/YARN-3940 Project: Hadoop YARN

[jira] [Commented] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633640#comment-14633640 ] Jun Gong commented on YARN-3896: Thanks [~devaraj.k] for the review and comments. Update a

[jira] [Commented] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

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

[jira] [Updated] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.05.patch > RMNode transitioned from RUNNING to REBOOTED because its response id had not

[jira] [Updated] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] He Tianyi updated YARN-3903: Attachment: YARN-3093.2.patch > Disable preemption at Queue level for Fair Scheduler > --

[jira] [Commented] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633469#comment-14633469 ] Devaraj K commented on YARN-3896: - Thanks [~hex108] for the updated patch. There are some

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

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

[jira] [Commented] (YARN-3877) YarnClientImpl.submitApplication swallows exceptions

[ https://issues.apache.org/jira/browse/YARN-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633399#comment-14633399 ] Steve Loughran commented on YARN-3877: -- LGTM. Do you think the final client.close() sh

[jira] [Updated] (YARN-3939) CS schedule Userlevel resource usage shown is zero for NodeLabel partition

[ https://issues.apache.org/jira/browse/YARN-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3939: --- Attachment: 0001-YARN-3939.patch > CS schedule Userlevel resource usage shown is zero for NodeL

[jira] [Updated] (YARN-3939) CS schedule Userlevel resource usage shown is zero for NodeLabel partition

[ https://issues.apache.org/jira/browse/YARN-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3939: --- Attachment: (was: 0001-YARN-3939.patch) > CS schedule Userlevel resource usage shown is zer

[jira] [Updated] (YARN-3939) CS schedule Userlevel resource usage shown is zero for NodeLabel partition

[ https://issues.apache.org/jira/browse/YARN-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3939: --- Attachment: 0001-YARN-3939.patch > CS schedule Userlevel resource usage shown is zero for NodeL

[jira] [Updated] (YARN-3939) CS schedule Userlevel resource usage shown is zero for NodeLabel partition

[ https://issues.apache.org/jira/browse/YARN-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3939: --- Attachment: ResourceUsage.jpg > CS schedule Userlevel resource usage shown is zero for NodeLabe

[jira] [Created] (YARN-3939) CS schedule Userlevel resource usage shown is zero for NodeLabel partition

Bibin A Chundatt created YARN-3939: -- Summary: CS schedule Userlevel resource usage shown is zero for NodeLabel partition Key: YARN-3939 URL: https://issues.apache.org/jira/browse/YARN-3939 Project: H

[jira] [Updated] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3543: Attachment: 0005-YARN-3543.patch > ApplicationReport should be able to tell whether the Appli