[jira] [Comment Edited] (YARN-6156) AM blacklisting to consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867376#comment-15867376 ] Varun Saxena edited comment on YARN-6156 at 2/15/17 7:29 AM: - For unmanaged AM

[jira] [Updated] (YARN-6156) AM blacklisting to consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-6156: --- Description: As per the current implementation for AM blacklisting, disabling is based on complete

[jira] [Updated] (YARN-6156) AM blacklisting to consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-6156: --- Description: As per the current implementation for AM blacklisting, disabling is based on complete

[jira] [Updated] (YARN-6156) AM blacklisting to consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-6156: --- Description: As per the current implementation for AM blacklisting, disabling is based on complete

[jira] [Commented] (YARN-6156) AM blacklisting to consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867376#comment-15867376 ] Varun Saxena commented on YARN-6156: For unmanaged AM as AM blacklisting is not done, it is equivalent

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

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

[jira] [Updated] (YARN-6156) AM blacklisting to consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-6156: --- Summary: AM blacklisting to consider node label partition (was: AM blacklisting consider node label

[jira] [Updated] (YARN-6156) AM blacklisting to consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-6156: --- Description: As per the current implementation for AM blacklisting, disabling is based on complete

[jira] [Updated] (YARN-6156) AM blacklisting consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-6156: --- Description: As per the current implementation for AM blacklisting, disabling is based on complete

[jira] [Commented] (YARN-5068) Expose scheduler queue to application master

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867356#comment-15867356 ] Vinod Kumar Vavilapalli commented on YARN-5068: --- It's a bit of an old JIRA but I just

[jira] [Commented] (YARN-6156) AM blacklisting consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867355#comment-15867355 ] Varun Saxena commented on YARN-6156: Thanks [~sunilg]. Will drop a comment and update the description.

[jira] [Commented] (YARN-6183) [YARN-3368] Few missing informations in Application and Application Attempt page for Basic Info table

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

[jira] [Updated] (YARN-6183) [YARN-3368] Few missing informations in Application and Application Attempt page for Basic Info table

[ https://issues.apache.org/jira/browse/YARN-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-6183: --- Attachment: YARN-6183.004.patch > [YARN-3368] Few missing informations in Application and Application Attempt

[jira] [Commented] (YARN-6175) Negative vcore for resource needed to preempt

[ https://issues.apache.org/jira/browse/YARN-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867330#comment-15867330 ] Karthik Kambatla commented on YARN-6175: Just skimmed through the patch. When using

[jira] [Commented] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867323#comment-15867323 ] Karthik Kambatla commented on YARN-6171: The latest patch looks pretty good, but undoes YARN-4690.

[jira] [Commented] (YARN-6183) [YARN-3368] Few missing informations in Application and Application Attempt page for Basic Info table

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

[jira] [Updated] (YARN-6183) [YARN-3368] Few missing informations in Application and Application Attempt page for Basic Info table

[ https://issues.apache.org/jira/browse/YARN-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated YARN-6183: --- Attachment: YARN-6183.003.patch > [YARN-3368] Few missing informations in Application and Application Attempt

[jira] [Updated] (YARN-6038) Check other resource requests if cannot match the first one while identifying containers to preempt

[ https://issues.apache.org/jira/browse/YARN-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6038: --- Issue Type: Bug (was: Sub-task) Parent: (was: YARN-5990) > Check other resource

[jira] [Resolved] (YARN-6038) Check other resource requests if cannot match the first one while identifying containers to preempt

[ https://issues.apache.org/jira/browse/YARN-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-6038. Resolution: Duplicate This is a duplicate of YARN-5832. > Check other resource requests if

[jira] [Commented] (YARN-6183) [YARN-3368] Few missing informations in Application and Application Attempt page for Basic Info table

[ https://issues.apache.org/jira/browse/YARN-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867313#comment-15867313 ] Sunil G commented on YARN-6183: --- In cluster overview page, Donut charts are not alligned cleanly when

[jira] [Updated] (YARN-5832) Preemption should consider more resource-requests of a starved app if the initial set can not be satisfied

[ https://issues.apache.org/jira/browse/YARN-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5832: --- Summary: Preemption should consider more resource-requests of a starved app if the initial set

[jira] [Updated] (YARN-6194) Cluster capacity in SchedulingPolicy is updated only on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6194: --- Attachment: (was: YARN-6193.000.patch) > Cluster capacity in SchedulingPolicy is updated

[jira] [Updated] (YARN-6193) FairScheduler might not trigger preemption when using DRF

[ https://issues.apache.org/jira/browse/YARN-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6193: --- Issue Type: Sub-task (was: Bug) Parent: YARN-5990 > FairScheduler might not trigger

[jira] [Updated] (YARN-6193) FairScheduler might not trigger preemption when using DRF

[ https://issues.apache.org/jira/browse/YARN-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6193: --- Attachment: YARN-6193.000.patch > FairScheduler might not trigger preemption when using DRF >

[jira] [Commented] (YARN-6193) FairScheduler might not trigger preemption when using DRF

[ https://issues.apache.org/jira/browse/YARN-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867309#comment-15867309 ] Karthik Kambatla commented on YARN-6193: Patch that: # Uses policy-based check instead of fitsIn to

[jira] [Issue Comment Deleted] (YARN-6194) Cluster capacity in SchedulingPolicy is updated only on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6194: --- Comment: was deleted (was: Patch that: # Uses policy-based check instead of fitsIn to see if a

[jira] [Updated] (YARN-6194) Cluster capacity in SchedulingPolicy is updated only on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6194: --- Attachment: YARN-6193.000.patch Patch that: # Uses policy-based check instead of fitsIn to see

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

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

[jira] [Commented] (YARN-6194) Cluster capacity in SchedulingPolicy is updated only on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867300#comment-15867300 ] Karthik Kambatla commented on YARN-6194: When this is fixed, we should remove the TODO in

[jira] [Created] (YARN-6194) Cluster capacity in SchedulingPolicy is updated only on allocation file reload

Karthik Kambatla created YARN-6194: -- Summary: Cluster capacity in SchedulingPolicy is updated only on allocation file reload Key: YARN-6194 URL: https://issues.apache.org/jira/browse/YARN-6194

[jira] [Commented] (YARN-6148) NM node count reported to AM in Allocate Response should consider requested node label partitions.

[ https://issues.apache.org/jira/browse/YARN-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867298#comment-15867298 ] Sunil G commented on YARN-6148: --- +1 for the current approach. > NM node count reported to AM in Allocate

[jira] [Commented] (YARN-6156) AM blacklisting consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867295#comment-15867295 ] Sunil G commented on YARN-6156: --- It looks fine. But this change is not the cause of this ticket, however its

[jira] [Commented] (YARN-6148) NM node count reported to AM in Allocate Response should consider requested node label partitions.

[ https://issues.apache.org/jira/browse/YARN-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867294#comment-15867294 ] Varun Saxena commented on YARN-6148: Yes, that's the plan. > NM node count reported to AM in Allocate

[jira] [Commented] (YARN-6175) Negative vcore for resource needed to preempt

[ https://issues.apache.org/jira/browse/YARN-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867275#comment-15867275 ] Yufei Gu commented on YARN-6175: Thanks [~wilfreds] for the review. [~kasha], wanna take a look? >

[jira] [Commented] (YARN-4753) Use doxia macro to generate in-page TOC of YARN site documentation

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

[jira] [Updated] (YARN-6193) FairScheduler might not trigger preemption when using DRF

[ https://issues.apache.org/jira/browse/YARN-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6193: --- Description: {{FSAppAttempt#canContainerBePreempted}} verifies preempting a container doesn't

[jira] [Updated] (YARN-6193) FairScheduler might not trigger preemption when using DRF

[ https://issues.apache.org/jira/browse/YARN-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6193: --- Summary: FairScheduler might not trigger preemption when using DRF (was:

[jira] [Updated] (YARN-6193) FSAppAttempt#canContainerBePreempted considers all resources instead of just dominant resource

[ https://issues.apache.org/jira/browse/YARN-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6193: --- Summary: FSAppAttempt#canContainerBePreempted considers all resources instead of just dominant

[jira] [Commented] (YARN-6156) AM blacklisting consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867243#comment-15867243 ] Varun Saxena commented on YARN-6156: By the way for unmanaged AM, am resource request will be null and

[jira] [Updated] (YARN-4753) Use doxia macro to generate in-page TOC of YARN site documentation

[ https://issues.apache.org/jira/browse/YARN-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated YARN-4753: --- Attachment: YARN-4753-branch-2.001.patch > Use doxia macro to generate in-page TOC of YARN

[jira] [Updated] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6163: --- Attachment: YARN-6163.004.patch Uploading patch v4 to match 4th commit in the PR. Not sure why

[jira] [Commented] (YARN-4753) Use doxia macro to generate in-page TOC of YARN site documentation

[ https://issues.apache.org/jira/browse/YARN-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867229#comment-15867229 ] Hudson commented on YARN-4753: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11250 (See

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867224#comment-15867224 ] ASF GitHub Bot commented on YARN-6163: -- Github user kambatla commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867217#comment-15867217 ] ASF GitHub Bot commented on YARN-6163: -- Github user kambatla commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867215#comment-15867215 ] ASF GitHub Bot commented on YARN-6163: -- Github user kambatla commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867211#comment-15867211 ] ASF GitHub Bot commented on YARN-6163: -- Github user kambatla commented on a diff in the pull request:

[jira] [Commented] (YARN-6175) Negative vcore for resource needed to preempt

[ https://issues.apache.org/jira/browse/YARN-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867208#comment-15867208 ] Wilfred Spiegelenburg commented on YARN-6175: - The change overall looks good. The junit test

[jira] [Commented] (YARN-6180) Clean unused SchedulerRequestKeys once ExecutionType updates are completed

[ https://issues.apache.org/jira/browse/YARN-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867207#comment-15867207 ] Arun Suresh commented on YARN-6180: --- Yup, this is meant to track for container updates in general.

[jira] [Commented] (YARN-6156) AM blacklisting consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867203#comment-15867203 ] Varun Saxena commented on YARN-6156: Thanks [~bibinchundatt]. Yeah it is not necessary to invoke simple

[jira] [Commented] (YARN-6156) AM blacklisting consider node label partition

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

[jira] [Commented] (YARN-4753) Use doxia macro to generate in-page TOC of YARN site documentation

[ https://issues.apache.org/jira/browse/YARN-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867191#comment-15867191 ] Masatake Iwasaki commented on YARN-4753: Thanks. Committing to trunk and backporting to branch-2.

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867187#comment-15867187 ] ASF GitHub Bot commented on YARN-6163: -- Github user kambatla commented on a diff in the pull request:

[jira] [Commented] (YARN-6050) AMs can't be scheduled on racks or nodes

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

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867178#comment-15867178 ] ASF GitHub Bot commented on YARN-6163: -- Github user kambatla commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867177#comment-15867177 ] ASF GitHub Bot commented on YARN-6163: -- Github user kambatla commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867180#comment-15867180 ] ASF GitHub Bot commented on YARN-6163: -- Github user kambatla commented on a diff in the pull request:

[jira] [Commented] (YARN-6148) NM node count reported to AM in Allocate Response should consider requested node label partitions.

[ https://issues.apache.org/jira/browse/YARN-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867139#comment-15867139 ] Rohith Sharma K S commented on YARN-6148: - Basically in this JIRA lets do for YARN related changes

[jira] [Updated] (YARN-6156) AM blacklisting consider node label partition

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-6156: --- Attachment: YARN-6156.0006.patch [~sunilg]/[~varun_saxena] Minor change in patch for checking

[jira] [Commented] (YARN-6042) Fairscheduler: Dump scheduler state in log

[ https://issues.apache.org/jira/browse/YARN-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867112#comment-15867112 ] Wilfred Spiegelenburg commented on YARN-6042: - Thank you for the update, we discussed it

[jira] [Commented] (YARN-6093) Invalid AMRM token exception when using FederationRMFailoverProxyProvider at AMRMtoken renewal during a RM failover

[ https://issues.apache.org/jira/browse/YARN-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867101#comment-15867101 ] Subru Krishnan commented on YARN-6093: -- [~botong], can you open a JIRA to track the test failure as we

[jira] [Commented] (YARN-6180) Clean unused SchedulerRequestKeys once ExecutionType updates are completed

[ https://issues.apache.org/jira/browse/YARN-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867100#comment-15867100 ] Subru Krishnan commented on YARN-6180: -- [~asuresh], IIUC this is valid for all key attributes and not

[jira] [Updated] (YARN-6190) Bug fixes in federation polices

[ https://issues.apache.org/jira/browse/YARN-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-6190: - Issue Type: Sub-task (was: Bug) Parent: YARN-2915 > Bug fixes in federation polices >

[jira] [Commented] (YARN-4036) Findbugs warnings in hadoop-yarn-server-common

[ https://issues.apache.org/jira/browse/YARN-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867096#comment-15867096 ] Akira Ajisaka commented on YARN-4036: - Now there are no findbugs warnings in hadoop-yarn-server-common

[jira] [Resolved] (YARN-4036) Findbugs warnings in hadoop-yarn-server-common

[ https://issues.apache.org/jira/browse/YARN-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YARN-4036. - Resolution: Not A Problem > Findbugs warnings in hadoop-yarn-server-common >

[jira] [Comment Edited] (YARN-6093) Invalid AMRM token exception when using FederationRMFailoverProxyProvider at AMRMtoken renewal during a RM failover

[ https://issues.apache.org/jira/browse/YARN-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867060#comment-15867060 ] Botong Huang edited comment on YARN-6093 at 2/15/17 1:23 AM: - Talked to

[jira] [Commented] (YARN-6093) Invalid AMRM token exception when using FederationRMFailoverProxyProvider at AMRMtoken renewal during a RM failover

[ https://issues.apache.org/jira/browse/YARN-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867060#comment-15867060 ] Botong Huang commented on YARN-6093: Talked to [~curino] offline, this is a randomized test, and

[jira] [Commented] (YARN-6093) Invalid AMRM token exception when using FederationRMFailoverProxyProvider at AMRMtoken renewal during a RM failover

[ https://issues.apache.org/jira/browse/YARN-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867042#comment-15867042 ] Botong Huang commented on YARN-6093: +[~curino]: can you please take a look at the test failure

[jira] [Commented] (YARN-6175) Negative vcore for resource needed to preempt

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

[jira] [Commented] (YARN-6093) Invalid AMRM token exception when using FederationRMFailoverProxyProvider at AMRMtoken renewal during a RM failover

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

[jira] [Commented] (YARN-6164) Expose maximum-am-resource-percent to Hadoop clients

[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866995#comment-15866995 ] Benson Qiu commented on YARN-6164: -- Version 003: Fix test failures > Expose maximum-am-resource-percent

[jira] [Updated] (YARN-6164) Expose maximum-am-resource-percent to Hadoop clients

[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Qiu updated YARN-6164: - Attachment: YARN-6164.003.patch > Expose maximum-am-resource-percent to Hadoop clients >

[jira] [Commented] (YARN-6192) Move yarn-native-service API records into hadoop-yarn-slider-core module

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

[jira] [Updated] (YARN-6050) AMs can't be scheduled on racks or nodes

[ https://issues.apache.org/jira/browse/YARN-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-6050: Attachment: YARN-6050.007.patch The 007 patch: - Integrates the AM blacklisting feature by setting

[jira] [Commented] (YARN-6061) Add an UncaughtExceptionHandler for critical threads in RM

[ https://issues.apache.org/jira/browse/YARN-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866955#comment-15866955 ] Hudson commented on YARN-6061: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11249 (See

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866937#comment-15866937 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866936#comment-15866936 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Updated] (YARN-6093) Invalid AMRM token exception when using FederationRMFailoverProxyProvider at AMRMtoken renewal during a RM failover

[ https://issues.apache.org/jira/browse/YARN-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-6093: --- Attachment: YARN-6093-YARN-2915.v4.patch > Invalid AMRM token exception when using

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866939#comment-15866939 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Updated] (YARN-6093) Invalid AMRM token exception when using FederationRMFailoverProxyProvider at AMRMtoken renewal during a RM failover

[ https://issues.apache.org/jira/browse/YARN-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-6093: --- Attachment: (was: YARN-6093-YARN-2915.v4.patch) > Invalid AMRM token exception when using

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866938#comment-15866938 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866940#comment-15866940 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Commented] (YARN-6042) Fairscheduler: Dump scheduler state in log

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

[jira] [Updated] (YARN-6192) Move yarn-native-service API records into hadoop-yarn-slider-core module

[ https://issues.apache.org/jira/browse/YARN-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-6192: -- Attachment: YARN-6192.yarn-native-services.02.patch > Move yarn-native-service API records into

[jira] [Commented] (YARN-6191) CapacityScheduler preemption by container priority can be problematic for MapReduce

[ https://issues.apache.org/jira/browse/YARN-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866914#comment-15866914 ] Chris Douglas commented on YARN-6191: - This is related to a

[jira] [Commented] (YARN-6061) Add an UncaughtExceptionHandler for critical threads in RM

[ https://issues.apache.org/jira/browse/YARN-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866907#comment-15866907 ] Karthik Kambatla commented on YARN-6061: Included an extraneous change in the original commit. Just

[jira] [Commented] (YARN-5280) Allow YARN containers to run with Java Security Manager

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

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866847#comment-15866847 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866848#comment-15866848 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866841#comment-15866841 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866842#comment-15866842 ] ASF GitHub Bot commented on YARN-6163: -- Github user templedf commented on a diff in the pull request:

[jira] [Commented] (YARN-6190) Bug fixes in federation polices

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

[jira] [Commented] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

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

[jira] [Updated] (YARN-6042) Fairscheduler: Dump scheduler state in log

[ https://issues.apache.org/jira/browse/YARN-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6042: --- Attachment: YARN-6042.005.patch Patch v5 is a rebase. The upstream changes too fast. > Fairscheduler: Dump

[jira] [Comment Edited] (YARN-6190) Bug fixes in federation polices

[ https://issues.apache.org/jira/browse/YARN-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866793#comment-15866793 ] Carlo Curino edited comment on YARN-6190 at 2/14/17 10:04 PM: -- Hi [~botong],

[jira] [Comment Edited] (YARN-6190) Bug fixes in federation polices

[ https://issues.apache.org/jira/browse/YARN-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866793#comment-15866793 ] Carlo Curino edited comment on YARN-6190 at 2/14/17 10:03 PM: -- Hi [~botong],

[jira] [Commented] (YARN-6190) Bug fixes in federation polices

[ https://issues.apache.org/jira/browse/YARN-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866793#comment-15866793 ] Carlo Curino commented on YARN-6190: Hi [~botong], Thanks for the patch, it looks good in general. I

[jira] [Created] (YARN-6193) DominantResourceFairnessPolicy#checkIfUsageOverFairShare considers all resources instead of just dominant resource

Karthik Kambatla created YARN-6193: -- Summary: DominantResourceFairnessPolicy#checkIfUsageOverFairShare considers all resources instead of just dominant resource Key: YARN-6193 URL:

[jira] [Commented] (YARN-6061) Add an UncaughtExceptionHandler for critical threads in RM

[ https://issues.apache.org/jira/browse/YARN-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866776#comment-15866776 ] Hudson commented on YARN-6061: -- FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #11248 (See

[jira] [Commented] (YARN-6061) Add an UncaughtExceptionHandler for critical threads in RM

[ https://issues.apache.org/jira/browse/YARN-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866773#comment-15866773 ] Yufei Gu commented on YARN-6061: Yeah! Thanks [~kasha] for review, advice and commit. > Add an

[jira] [Commented] (YARN-6192) Move yarn-native-service API records into hadoop-yarn-slider-core module

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

  1   2   >