[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624282#comment-14624282 ] Varun Saxena commented on YARN-3916: I thought of this first. But issue here is that Li

[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=14624272#comment-14624272 ] Jian He commented on YARN-2003: --- [~sunilg], thanks for updating the patch!. newest patch look

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624271#comment-14624271 ] Rohith Sharma K S commented on YARN-3916: - How about keeping earlier variable *drai

[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-tabpanel&focusedCommentId=14624269#comment-14624269 ] Hadoop QA commented on YARN-3535: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Updated] (YARN-3381) A typographical error in "InvalidStateTransitonException"

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3381: --- Attachment: YARN-3381-011.patch > A typographical error in "InvalidStateTransitonExcept

[jira] [Commented] (YARN-3381) A typographical error in "InvalidStateTransitonException"

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624263#comment-14624263 ] Brahma Reddy Battula commented on YARN-3381: hmm.. [~ajisakaa] addressed the ab

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624259#comment-14624259 ] Karthik Kambatla commented on YARN-3916: Skimmed through the patch. Would it be sim

[jira] [Commented] (YARN-3381) A typographical error in "InvalidStateTransitonException"

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624255#comment-14624255 ] Akira AJISAKA commented on YARN-3381: - Thank you for updating the patch. I have 2 comme

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624250#comment-14624250 ] Bibin A Chundatt commented on YARN-3894: [~sunilg] and [~leftnoteasy] thanks a lot

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624246#comment-14624246 ] Bibin A Chundatt commented on YARN-3893: Thanks [~varun_saxena] and [~sunilg] first

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624233#comment-14624233 ] Varun Saxena commented on YARN-3893: Yeah lets go with first option I suggested then i.

[jira] [Commented] (YARN-3381) A typographical error in "InvalidStateTransitonException"

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624208#comment-14624208 ] Brahma Reddy Battula commented on YARN-3381: [~ajisakaa] did not notice v9 patc

[jira] [Updated] (YARN-3381) A typographical error in "InvalidStateTransitonException"

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3381: --- Attachment: YARN-3381-010.patch > A typographical error in "InvalidStateTransitonExcept

[jira] [Updated] (YARN-3381) A typographical error in "InvalidStateTransitonException"

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3381: --- Attachment: (was: YARN-3381-009.patch) > A typographical error in "InvalidStateTran

[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-tabpanel&focusedCommentId=14624202#comment-14624202 ] Rohith Sharma K S commented on YARN-3535: - [~peng.zhang] I rebased the patch to tru

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624201#comment-14624201 ] Hudson commented on YARN-3894: -- FAILURE: Integrated in Hadoop-trunk-Commit #8154 (See [https:

[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 ] Rohith Sharma K S updated YARN-3535: Attachment: 0003-YARN-3535.patch > ResourceRequest should be restored back to scheduler when

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

[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-tabpanel&focusedCommentId=14624187#comment-14624187 ] Hadoop QA commented on YARN-3535: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (YARN-3913) TestResourceTrackerService#testReconnectNode fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624185#comment-14624185 ] Rohith Sharma K S commented on YARN-3913: - [~varun_saxena] can you add trace or lin

[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 ] Rohith Sharma K S updated YARN-3535: Labels: (was: BB2015-05-TBR) > ResourceRequest should be restored back to scheduler when R

[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 ] Rohith Sharma K S updated YARN-3535: Target Version/s: 2.8.0 > ResourceRequest should be restored back to scheduler when RMContai

[jira] [Commented] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624178#comment-14624178 ] Ray Chiang commented on YARN-3069: -- Thanks for the sharp eye on the review and the commit!

[jira] [Commented] (YARN-3381) A typographical error in "InvalidStateTransitonException"

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624177#comment-14624177 ] Akira AJISAKA commented on YARN-3381: - v9 patch is missing the new class. Would you {{g

[jira] [Updated] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-3069: Labels: supportability (was: BB2015-05-TBR supportability) > Document missing properties in yarn-def

[jira] [Commented] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624174#comment-14624174 ] Hudson commented on YARN-3069: -- FAILURE: Integrated in Hadoop-trunk-Commit #8153 (See [https:

[jira] [Updated] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-3069: Issue Type: Improvement (was: Bug) > Document missing properties in yarn-default.xml > -

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624156#comment-14624156 ] Sunil G commented on YARN-3893: --- Thanks [~varun_saxena] for sharing detailed analysis. Infact

[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: 0020-YARN-2003.patch Thank you [~jianhe] Uploading a new patch after addressing few comments. Also r

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624018#comment-14624018 ] Wangda Tan commented on YARN-3916: -- [~varun_saxena], Thanks for updating, but I think the

[jira] [Commented] (YARN-3919) NPEs' while stopping service on exception during CommonNodeLabelsManager#start

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

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

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

[jira] [Updated] (YARN-3919) NPEs' while stopping service on exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3919: --- Description: We get NPE during CommonNodeLabelsManager#serviceStop and AsyncDispatcher#serviceStop if

[jira] [Commented] (YARN-3910) TestRMAppTransitions#testAppAcceptedAttemptKilled fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623960#comment-14623960 ] Varun Saxena commented on YARN-3910: Thanks [~adhoot] for reviewing. Found out the root

[jira] [Updated] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3916: --- Component/s: (was: resourcemanager) > DrainDispatcher#await should wait till event has been complet

[jira] [Updated] (YARN-3919) NPEs' while stopping service on exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3919: --- Attachment: YARN-3919.01.patch > NPEs' while stopping service on exception during CommonNodeLabelsManag

[jira] [Commented] (YARN-3919) NPEs' while stopping service on exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623955#comment-14623955 ] Varun Saxena commented on YARN-3919: Checked and found that NPE in AsyncDispatcher no l

[jira] [Updated] (YARN-3919) NPEs' while stopping service on exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3919: --- Description: We get NPE during CommonNodeLabelsManager#serviceStop and AsyncDispatcher#serviceStop if

[jira] [Commented] (YARN-3919) NPEs' while stopping service on exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623949#comment-14623949 ] Varun Saxena commented on YARN-3919: ConnectException which led to this {noformat} 2015

[jira] [Updated] (YARN-3919) NPEs' while stopping service on exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3919: --- Description: We get NPE during CommonNodeLabelsManager#serviceStop and AsyncDispatcher#serviceStop if

[jira] [Created] (YARN-3919) NPEs' while stopping service on exception during CommonNodeLabelsManager#start

Varun Saxena created YARN-3919: -- Summary: NPEs' while stopping service on exception during CommonNodeLabelsManager#start Key: YARN-3919 URL: https://issues.apache.org/jira/browse/YARN-3919 Project: Hadoo

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

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

[jira] [Updated] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3894: --- Attachment: 0002-YARN-3894.patch Hi [~leftnoteasy] patch for review after handling comments Aft

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623919#comment-14623919 ] Varun Saxena commented on YARN-3916: Thanks [~leftnoteasy] for reviewing the patch. Hav

[jira] [Updated] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3916: --- Attachment: YARN-3916.02.patch > DrainDispatcher#await should wait till event has been completely handl

[jira] [Resolved] (YARN-3918) TestApplicationCleanup#testContainerCleanup occasionally fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-3918. -- Resolution: Duplicate > TestApplicationCleanup#testContainerCleanup occasionally fails on trunk > ---

[jira] [Commented] (YARN-3918) TestApplicationCleanup#testContainerCleanup occasionally fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623915#comment-14623915 ] Wangda Tan commented on YARN-3918: -- [~varun_saxena], Thanks for working at it, just posted

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623913#comment-14623913 ] Wangda Tan commented on YARN-3916: -- Thanks [~varun_saxena] investigating this problem, I t

[jira] [Updated] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3916: --- Description: DrainDispatcher#await should wait till event has been completely handled. Currently it onl

[jira] [Commented] (YARN-3918) TestApplicationCleanup#testContainerCleanup occasionally fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623907#comment-14623907 ] Varun Saxena commented on YARN-3918: [~leftnoteasy], the root cause of these test failu

[jira] [Commented] (YARN-3866) AM-RM protocol changes to support container resizing

[ https://issues.apache.org/jira/browse/YARN-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623901#comment-14623901 ] Wangda Tan commented on YARN-3866: -- bq. 1. DecreasedContainer.java/IncreasedContainer.java

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623897#comment-14623897 ] Wangda Tan commented on YARN-3894: -- Thanks [~bibinchundatt] working on the patch. YARN-39

[jira] [Created] (YARN-3918) TestApplicationCleanup#testContainerCleanup occasionally fails on trunk

Wangda Tan created YARN-3918: Summary: TestApplicationCleanup#testContainerCleanup occasionally fails on trunk Key: YARN-3918 URL: https://issues.apache.org/jira/browse/YARN-3918 Project: Hadoop YARN

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623857#comment-14623857 ] Hudson commented on YARN-3849: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2200 (See [htt

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623858#comment-14623858 ] Hudson commented on YARN-3917: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2200 (See [htt

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623830#comment-14623830 ] Hudson commented on YARN-3917: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #2181 (See [https://

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623829#comment-14623829 ] Hudson commented on YARN-3849: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #2181 (See [https://

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623828#comment-14623828 ] Hudson commented on YARN-3917: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #242 (See [htt

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623827#comment-14623827 ] Hudson commented on YARN-3849: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #242 (See [htt

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623800#comment-14623800 ] Hudson commented on YARN-3917: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #252 (See

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623799#comment-14623799 ] Hudson commented on YARN-3849: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #252 (See

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623748#comment-14623748 ] Hudson commented on YARN-3917: -- FAILURE: Integrated in Hadoop-Yarn-trunk #984 (See [https://b

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623747#comment-14623747 ] Hudson commented on YARN-3849: -- FAILURE: Integrated in Hadoop-Yarn-trunk #984 (See [https://b

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623744#comment-14623744 ] Hudson commented on YARN-3849: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #254 (See [htt

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623745#comment-14623745 ] Hudson commented on YARN-3917: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #254 (See [htt

[jira] [Commented] (YARN-3898) YARN web console only proxies GET to application master but doesn't provide any feedback for other HTTP methods

[ https://issues.apache.org/jira/browse/YARN-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623739#comment-14623739 ] Steve Loughran commented on YARN-3898: -- if allowing all HTTP verbs through is what you