[jira] [Commented] (YARN-3930) FileSystemNodeLabelsStore should make sure edit log file closed when exception is thrown

[ https://issues.apache.org/jira/browse/YARN-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631400#comment-14631400 ] Hudson commented on YARN-3930: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #248 (See

[jira] [Commented] (YARN-3885) ProportionalCapacityPreemptionPolicy doesn't preempt if queue is more than 2 level

[ https://issues.apache.org/jira/browse/YARN-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631401#comment-14631401 ] Hudson commented on YARN-3885: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #248 (See

[jira] [Updated] (YARN-2681) Support bandwidth enforcement for containers while reading from HDFS

[ https://issues.apache.org/jira/browse/YARN-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nam H. Do updated YARN-2681: Attachment: YARN-2681.005.patch fixed javadoc warnings Support bandwidth enforcement for containers while

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

[jira] [Commented] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

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

[jira] [Commented] (YARN-3885) ProportionalCapacityPreemptionPolicy doesn't preempt if queue is more than 2 level

[ https://issues.apache.org/jira/browse/YARN-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631230#comment-14631230 ] Hudson commented on YARN-3885: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #259 (See

[jira] [Commented] (YARN-3930) FileSystemNodeLabelsStore should make sure edit log file closed when exception is thrown

[ https://issues.apache.org/jira/browse/YARN-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631229#comment-14631229 ] Hudson commented on YARN-3930: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #259 (See

[jira] [Commented] (YARN-3930) FileSystemNodeLabelsStore should make sure edit log file closed when exception is thrown

[ https://issues.apache.org/jira/browse/YARN-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631239#comment-14631239 ] Hudson commented on YARN-3930: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #989 (See

[jira] [Commented] (YARN-3885) ProportionalCapacityPreemptionPolicy doesn't preempt if queue is more than 2 level

[ https://issues.apache.org/jira/browse/YARN-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631240#comment-14631240 ] Hudson commented on YARN-3885: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #989 (See

[jira] [Commented] (YARN-3885) ProportionalCapacityPreemptionPolicy doesn't preempt if queue is more than 2 level

[ https://issues.apache.org/jira/browse/YARN-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631390#comment-14631390 ] Hudson commented on YARN-3885: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2186 (See

[jira] [Commented] (YARN-3930) FileSystemNodeLabelsStore should make sure edit log file closed when exception is thrown

[ https://issues.apache.org/jira/browse/YARN-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631389#comment-14631389 ] Hudson commented on YARN-3930: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2186 (See

[jira] [Commented] (YARN-3905) Application History Server UI NPEs when accessing apps run after RM restart

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

[jira] [Updated] (YARN-3905) Application History Server UI NPEs when accessing apps run after RM restart

[ https://issues.apache.org/jira/browse/YARN-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-3905: - Attachment: YARN-3905.002.patch Fixing checkstyle bug. I forgot to remove the now-unused {{ContainerID}}

[jira] [Commented] (YARN-3174) Consolidate the NodeManager and NodeManagerRestart documentation into one

[ https://issues.apache.org/jira/browse/YARN-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631298#comment-14631298 ] Hudson commented on YARN-3174: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #256 (See

[jira] [Commented] (YARN-3885) ProportionalCapacityPreemptionPolicy doesn't preempt if queue is more than 2 level

[ https://issues.apache.org/jira/browse/YARN-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631304#comment-14631304 ] Hudson commented on YARN-3885: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #256 (See

[jira] [Commented] (YARN-3805) Update the documentation of Disk Checker based on YARN-90

[ https://issues.apache.org/jira/browse/YARN-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631297#comment-14631297 ] Hudson commented on YARN-3805: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #256 (See

[jira] [Commented] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631300#comment-14631300 ] Hudson commented on YARN-3535: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #256 (See

[jira] [Commented] (YARN-90) NodeManager should identify failed disks becoming good again

[ https://issues.apache.org/jira/browse/YARN-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631302#comment-14631302 ] Hudson commented on YARN-90: FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #256 (See

[jira] [Commented] (YARN-3930) FileSystemNodeLabelsStore should make sure edit log file closed when exception is thrown

[ https://issues.apache.org/jira/browse/YARN-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631301#comment-14631301 ] Hudson commented on YARN-3930: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #256 (See

[jira] [Commented] (YARN-3938) AM Resources for leaf queues zero when DEFAULT PARTITION resource is zero with NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631317#comment-14631317 ] Bibin A Chundatt commented on YARN-3938: Hi [~leftnoteasy] .As i understand {{

[jira] [Commented] (YARN-3930) FileSystemNodeLabelsStore should make sure edit log file closed when exception is thrown

[ https://issues.apache.org/jira/browse/YARN-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631455#comment-14631455 ] Hudson commented on YARN-3930: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2205 (See

[jira] [Commented] (YARN-3885) ProportionalCapacityPreemptionPolicy doesn't preempt if queue is more than 2 level

[ https://issues.apache.org/jira/browse/YARN-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631456#comment-14631456 ] Hudson commented on YARN-3885: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2205 (See

[jira] [Commented] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631454#comment-14631454 ] Hudson commented on YARN-3535: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2205 (See

[jira] [Commented] (YARN-2306) leak of reservation metrics (fair scheduler)

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

[jira] [Updated] (YARN-3933) Resources(both core and memory) are being negative

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lavkesh Lahngir updated YARN-3933: -- Summary: Resources(both core and memory) are being negative (was: Resources(bothe core and

[jira] [Created] (YARN-3936) Add metrics for RMStateStore

Ming Ma created YARN-3936: - Summary: Add metrics for RMStateStore Key: YARN-3936 URL: https://issues.apache.org/jira/browse/YARN-3936 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-3845) [YARN] YARN status in web ui does not show correctly in IE 11

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

[jira] [Commented] (YARN-3934) Application with large ApplicationSubmissionContext can cause RM to exit when ZK store is used

[ https://issues.apache.org/jira/browse/YARN-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14630884#comment-14630884 ] Sunil G commented on YARN-3934: --- As of now there are no checks for the size of

[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-tabpanelfocusedCommentId=14630860#comment-14630860 ] Rohith Sharma K S commented on YARN-3543: - Discussed with [~xgong] offline, as per

[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: TestResult.jpg SchedulerApplicationAttempt#getResourceUsageReport should be based

[jira] [Created] (YARN-3934) Application with large ApplicationSubmissionContext can cause RM to exit when ZK store is used

Ming Ma created YARN-3934: - Summary: Application with large ApplicationSubmissionContext can cause RM to exit when ZK store is used Key: YARN-3934 URL: https://issues.apache.org/jira/browse/YARN-3934

[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: 0001-YARN-3932.patch SchedulerApplicationAttempt#getResourceUsageReport should be

[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-tabpanelfocusedCommentId=14630867#comment-14630867 ] Varun Saxena commented on YARN-3049: [~zjshen], should cluster ID be mandatory in REST

[jira] [Commented] (YARN-3936) Add metrics for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14630878#comment-14630878 ] Sunil G commented on YARN-3936: --- Hi [~mingma] I would like to work on this. Please let me

[jira] [Created] (YARN-3935) Support compression for RM HA ApplicationStateData

Ming Ma created YARN-3935: - Summary: Support compression for RM HA ApplicationStateData Key: YARN-3935 URL: https://issues.apache.org/jira/browse/YARN-3935 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

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

[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-tabpanelfocusedCommentId=14630877#comment-14630877 ] Bibin A Chundatt commented on YARN-3932: [~leftnoteasy] used

[jira] [Commented] (YARN-3905) Application History Server UI NPEs when accessing apps run after RM restart

[ https://issues.apache.org/jira/browse/YARN-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631501#comment-14631501 ] Jonathan Eagles commented on YARN-3905: --- +1. Committing this patch [~eepayne].

[jira] [Commented] (YARN-3905) Application History Server UI NPEs when accessing apps run after RM restart

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

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

Sunil G created YARN-3937: - Summary: Introducing REMOVE_CONTAINER_FROM_PREEMPTION event to notify Scheduler and AM when a container is no longer to be preempted Key: YARN-3937 URL:

[jira] [Updated] (YARN-3938) AM Resources for leaf queues zero when DEFAULT PARTITION resource is zero with NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3938: --- Summary: AM Resources for leaf queues zero when DEFAULT PARTITION resource is zero with

[jira] [Updated] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3535: -- Component/s: resourcemanager fairscheduler capacityscheduler

[jira] [Updated] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3535: -- Fix Version/s: 2.8.0 ResourceRequest should be restored back to scheduler when RMContainer is killed

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631205#comment-14631205 ] Arun Suresh commented on YARN-3535: --- +1, Committing this shortly. Thanks to everyone

[jira] [Created] (YARN-3938) AM Resources for leaf queues zero when DEFAULT PARTITION resource is zero

Bibin A Chundatt created YARN-3938: -- Summary: AM Resources for leaf queues zero when DEFAULT PARTITION resource is zero Key: YARN-3938 URL: https://issues.apache.org/jira/browse/YARN-3938 Project:

[jira] [Updated] (YARN-3938) AM Resources for leaf queues zero when DEFAULT PARTITION resource is zero

[ https://issues.apache.org/jira/browse/YARN-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3938: --- Attachment: Am limit for subqueue.jpg AM Resources for leaf queues zero when DEFAULT

[jira] [Updated] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3535: -- Summary: Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to

[jira] [Updated] (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:all-tabpanel ] Sunil G updated YARN-2003: -- Attachment: 0023-YARN-2003.patch Thank you [~leftnoteasy] for the comments. Uploading a new patch addressing

[jira] [Updated] (YARN-3937) Introducing REMOVE_CONTAINER_FROM_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: -- Issue Type: Sub-task (was: Bug) Parent: YARN-45 Introducing REMOVE_CONTAINER_FROM_PREEMPTION event to

[jira] [Updated] (YARN-3453) Fair Scheduler: Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3453: -- Fix Version/s: 2.8.0 Fair Scheduler: Parts of preemption logic uses DefaultResourceCalculator even in

[jira] [Commented] (YARN-3938) AM Resources for leaf queues zero when DEFAULT PARTITION resource is zero with NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631652#comment-14631652 ] Wangda Tan commented on YARN-3938: -- Hi [~bibinchundatt], Thanks for reporting this issue,

[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-tabpanelfocusedCommentId=14631623#comment-14631623 ] Wangda Tan commented on YARN-2003: -- Latest patch looks good, [~sunilg], could you take a

[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-tabpanelfocusedCommentId=14631656#comment-14631656 ] Wangda Tan commented on YARN-3932: -- Thanks for update [~bibinchundatt], could you add a

[jira] [Updated] (YARN-3905) Application History Server UI NPEs when accessing apps run after RM restart

[ https://issues.apache.org/jira/browse/YARN-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-3905: -- Fix Version/s: 3.0.0 2.7.2 2.8.0 Application History

[jira] [Commented] (YARN-2681) Support bandwidth enforcement for containers while reading from HDFS

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

[jira] [Commented] (YARN-1645) ContainerManager implementation to support container resizing

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

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

[jira] [Updated] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

[ https://issues.apache.org/jira/browse/YARN-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3878: Attachment: YARN-3878.09_reprorace.pat_h Attaching a patch just to demonstrate the race. Since its

[jira] [Commented] (YARN-3937) Introducing REMOVE_CONTAINER_FROM_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:comment-tabpanelfocusedCommentId=14631677#comment-14631677 ] Wangda Tan commented on YARN-3937: -- [~sunilg], I agree to have a separated event add to

[jira] [Commented] (YARN-3844) Make hadoop-yarn-project Native code -Wall-clean

[ https://issues.apache.org/jira/browse/YARN-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631720#comment-14631720 ] Colin Patrick McCabe commented on YARN-3844: +1. Thanks, Alan. Make

[jira] [Commented] (YARN-3784) Indicate preemption timout along with the list of containers to AM (preemption message)

[ https://issues.apache.org/jira/browse/YARN-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631671#comment-14631671 ] Wangda Tan commented on YARN-3784: -- Hi [~sunilg], Thanks for your comments, I will post

[jira] [Commented] (YARN-3784) Indicate preemption timout along with the list of containers to AM (preemption message)

[ https://issues.apache.org/jira/browse/YARN-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631691#comment-14631691 ] Wangda Tan commented on YARN-3784: -- And also about this patch, same as commented by

[jira] [Commented] (YARN-3934) Application with large ApplicationSubmissionContext can cause RM to exit when ZK store is used

[ https://issues.apache.org/jira/browse/YARN-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631783#comment-14631783 ] Karthik Kambatla commented on YARN-3934: Are we sure this is because of the size of

[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-tabpanelfocusedCommentId=14632026#comment-14632026 ] Varun Vasudev commented on YARN-3853: - Thanks for the patch [~sidharta-s]. One question

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

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

[jira] [Updated] (YARN-2964) RM prematurely cancels tokens for jobs that submit jobs (oozie)

[ https://issues.apache.org/jira/browse/YARN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2964: -- Labels: 2.6.1-candidate (was: ) RM prematurely cancels tokens for jobs that

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632280#comment-14632280 ] zhihai xu commented on YARN-3798: - Thanks for the new patch [~ozawa]! the patch looks good

[jira] [Updated] (YARN-2890) MiniYarnCluster should turn on timeline service if configured to do so

[ https://issues.apache.org/jira/browse/YARN-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-2890: -- Labels: 2.6.1-candidate (was: ) MiniYarnCluster should turn on timeline service if configured to do so

[jira] [Updated] (YARN-2859) ApplicationHistoryServer binds to default port 8188 in MiniYARNCluster

[ https://issues.apache.org/jira/browse/YARN-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-2859: -- Labels: 2.6.1-candidate (was: ) ApplicationHistoryServer binds to default port 8188 in MiniYARNCluster

[jira] [Commented] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631832#comment-14631832 ] Jason Lowe commented on YARN-3535: -- Should this go in to 2.7.2? It's been seen by

[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-tabpanelfocusedCommentId=14631911#comment-14631911 ] Wangda Tan commented on YARN-2003: -- It seems latest tests are all passed. But [~sunilg],

[jira] [Commented] (YARN-3934) Application with large ApplicationSubmissionContext can cause RM to exit when ZK store is used

[ https://issues.apache.org/jira/browse/YARN-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632017#comment-14632017 ] Ming Ma commented on YARN-3934: --- This is due to a single ASC object size. You can repro this

[jira] [Updated] (YARN-3700) ATS Web Performance issue at load time when large number of jobs

[ https://issues.apache.org/jira/browse/YARN-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3700: -- Labels: 2.6.1-candidate 2.7.2-candidate (was: ) ATS Web Performance issue at

[jira] [Updated] (YARN-2816) NM fail to start with NPE during container recovery

[ https://issues.apache.org/jira/browse/YARN-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2816: -- Labels: 2.6.1-candidate (was: ) NM fail to start with NPE during container

[jira] [Commented] (YARN-1645) ContainerManager implementation to support container resizing

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

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

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-3908: -- Attachment: YARN-3908-YARN-2928.005.patch v.5 patch posted The {{readTimeseriesResults()}} method has

[jira] [Updated] (YARN-3654) ContainerLogsPage web UI should not have meta-refresh

[ https://issues.apache.org/jira/browse/YARN-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3654: -- Labels: 2.7.2-candidate (was: ) ContainerLogsPage web UI should not have

[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-tabpanelfocusedCommentId=14632079#comment-14632079 ] Sunil G commented on YARN-2003: --- Hi Wangda. This issue in MockRM was intermittent issue we

[jira] [Updated] (YARN-2340) NPE thrown when RM restart after queue is STOPPED. There after RM can not recovery application's and remain in standby

[ https://issues.apache.org/jira/browse/YARN-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2340: -- Labels: 2.6.1-candidate (was: ) NPE thrown when RM restart after queue is

[jira] [Updated] (YARN-2414) RM web UI: app page will crash if app is failed before any attempt has been created

[ https://issues.apache.org/jira/browse/YARN-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2414: -- Labels: 2.6.1-candidate (was: ) RM web UI: app page will crash if app is

[jira] [Updated] (YARN-3227) Timeline renew delegation token fails when RM user's TGT is expired

[ https://issues.apache.org/jira/browse/YARN-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3227: -- Labels: 2.6.1-candidate (was: ) Timeline renew delegation token fails when RM

[jira] [Updated] (YARN-3393) Getting application(s) goes wrong when app finishes before starting the attempt

[ https://issues.apache.org/jira/browse/YARN-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3393: -- Labels: 2.6.1-candidate (was: ) Getting application(s) goes wrong when app

[jira] [Commented] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

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

[jira] [Updated] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3216: - Description: Currently, max-am-resource-percentage considers default_partition only. When a queue can

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632125#comment-14632125 ] Jian He commented on YARN-2005: --- Seems the patch will blacklist a node immediately once the

[jira] [Updated] (YARN-1645) ContainerManager implementation to support container resizing

[ https://issues.apache.org/jira/browse/YARN-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1645: Attachment: YARN-1645-YARN-1197.5.patch I think you are right that these functions don't need to be

[jira] [Commented] (YARN-1645) ContainerManager implementation to support container resizing

[ https://issues.apache.org/jira/browse/YARN-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632037#comment-14632037 ] Jian He commented on YARN-1645: --- looks good overall, one question is: - why is this changed

[jira] [Commented] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632042#comment-14632042 ] Jian He commented on YARN-3900: --- lgtm Protobuf layout of yarn_security_token causes errors

[jira] [Commented] (YARN-1645) ContainerManager implementation to support container resizing

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

[jira] [Resolved] (YARN-3938) AM Resources for leaf queues zero when DEFAULT PARTITION resource is zero with NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-3938. -- Resolution: Duplicate I just found I filed one JIRA for this issue before, which is YARN-3216. Closing

[jira] [Updated] (YARN-2246) Job History Link in RM UI is redirecting to the URL which contains Job Id twice

[ https://issues.apache.org/jira/browse/YARN-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2246: -- Labels: 2.6.1-candidate (was: ) Job History Link in RM UI is redirecting to

[jira] [Updated] (YARN-3239) WebAppProxy does not support a final tracking url which has query fragments and params

[ https://issues.apache.org/jira/browse/YARN-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3239: -- Labels: 2.6.1-candidate (was: ) WebAppProxy does not support a final tracking

[jira] [Updated] (YARN-3207) secondary filter matches entites which do not have the key being filtered for.

[ https://issues.apache.org/jira/browse/YARN-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3207: -- Labels: 2.6.1-candidate (was: ) secondary filter matches entites which do not

[jira] [Assigned] (YARN-3936) Add metrics for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-3936: - Assignee: Sunil G Add metrics for RMStateStore Key:

[jira] [Updated] (YARN-1645) ContainerManager implementation to support container resizing

[ https://issues.apache.org/jira/browse/YARN-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1645: Attachment: YARN-1645-YARN-1197.4.patch The {{testChangeContainerResource}} has dependency on YARN-3867 and

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631928#comment-14631928 ] Wangda Tan commented on YARN-3216: -- There're two approaches of doing that, - Make

[jira] [Updated] (YARN-2905) AggregatedLogsBlock page can infinitely loop if the aggregated log file is corrupted

[ https://issues.apache.org/jira/browse/YARN-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2905: -- Labels: 2.6.1-candidate (was: ) AggregatedLogsBlock page can infinitely loop

[jira] [Updated] (YARN-2917) Potential deadlock in AsyncDispatcher when system.exit called in AsyncDispatcher#dispatch and AsyscDispatcher#serviceStop from shutdown hook

[ https://issues.apache.org/jira/browse/YARN-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2917: -- Labels: 2.6.1-candidate (was: ) Potential deadlock in AsyncDispatcher when

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

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631826#comment-14631826 ] Sangjin Lee commented on YARN-3908: --- Thanks for the comment [~gtCarrera9]. I agree the

[jira] [Commented] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

[ https://issues.apache.org/jira/browse/YARN-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631849#comment-14631849 ] Jian He commented on YARN-3878: --- Anubhav, thanks for reviewing the patch. I think given that

  1   2   >