[jira] [Updated] (YARN-4113) RM should respect retry-interval when uses RetryPolicies.RETRY_FOREVER

[ https://issues.apache.org/jira/browse/YARN-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4113: -- Attachment: 0001-YARN-4113.patch As HADOOP-12386 is committed, changing {{RetryProxy}} and {{ServerProy}} to use

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

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

[jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token

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

[jira] [Commented] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

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

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Component/s: security resourcemanager > Yarn Client uses local address instead RM address

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Attachment: YARN-4187.000.patch > Yarn Client uses local address instead RM address as token renewer in a >

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Attachment: YARN-4187.000.patch > Yarn Client uses local address instead RM address as token renewer in a >

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead of RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Description: Yarn Client uses local address instead of RM address as token renewer in a secure cluster when

[jira] [Commented] (YARN-4187) Yarn Client uses local address instead of RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876724#comment-14876724 ] zhihai xu commented on YARN-4187: - I attached a patch YARN-4187.000.patch which use YarnConfiguration

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Attachment: (was: YARN-4187.000.patch) > Yarn Client uses local address instead RM address as token

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Description: Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Description: Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead of RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Description: Yarn Client uses local address instead of RM address as token renewer in a secure cluster when

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead of RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Summary: Yarn Client uses local address instead of RM address as token renewer in a secure cluster when RM

[jira] [Updated] (YARN-4188) MoveApplicationAcrossQueuesResponse should be an abstract class

[ https://issues.apache.org/jira/browse/YARN-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-4188: --- Description: (was: In AppSchedulingInfo.java the method

[jira] [Commented] (YARN-4190) missing container information in FairScheduler preemption log.

[ https://issues.apache.org/jira/browse/YARN-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876762#comment-14876762 ] Xianyin Xin commented on YARN-4190: --- Hi [~zxu], will we consider to fix the issue in YARN-4134 or

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

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

[jira] [Commented] (YARN-4075) [reader REST API] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876765#comment-14876765 ] Sangjin Lee commented on YARN-4075: --- The latest patch looks good to me. Once YARN-4074 is committed, we

[jira] [Resolved] (YARN-4190) missing container information in FairScheduler preemption log.

[ https://issues.apache.org/jira/browse/YARN-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu resolved YARN-4190. - Resolution: Later > missing container information in FairScheduler preemption log. >

[jira] [Commented] (YARN-4190) missing container information in FairScheduler preemption log.

[ https://issues.apache.org/jira/browse/YARN-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876772#comment-14876772 ] zhihai xu commented on YARN-4190: - thanks [~xinxianyin] for the information! Yes, good suggestion. resolve

[jira] [Updated] (YARN-4180) AMLauncher does not retry on failures when talking to NM

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4180: Attachment: YARN-4180.001.patch reuse the same retry proxy used by AM client for RM client. Also

[jira] [Commented] (YARN-4186) Make WebAppUtils a public API for yarn

[ https://issues.apache.org/jira/browse/YARN-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876125#comment-14876125 ] Sunil G commented on YARN-4186: --- We could also get this information also from REST api

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Description: Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM

[jira] [Updated] (YARN-4189) Capacity Scheduler : Improve location preference waiting mechanism

[ https://issues.apache.org/jira/browse/YARN-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4189: - Attachment: YARN-4189 design v1.pdf > Capacity Scheduler : Improve location preference waiting mechanism >

[jira] [Created] (YARN-4189) Capacity Scheduler : Improve location preference waiting mechanism

Wangda Tan created YARN-4189: Summary: Capacity Scheduler : Improve location preference waiting mechanism Key: YARN-4189 URL: https://issues.apache.org/jira/browse/YARN-4189 Project: Hadoop YARN

[jira] [Created] (YARN-4190) Add container information in FairScheduler preemption log to help debug.

zhihai xu created YARN-4190: --- Summary: Add container information in FairScheduler preemption log to help debug. Key: YARN-4190 URL: https://issues.apache.org/jira/browse/YARN-4190 Project: Hadoop YARN

[jira] [Updated] (YARN-4190) missing container information in FairScheduler preemption log.

[ https://issues.apache.org/jira/browse/YARN-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4190: Summary: missing container information in FairScheduler preemption log. (was: Add container information in

[jira] [Created] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA is enabled.

zhihai xu created YARN-4187: --- Summary: Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA is enabled. Key: YARN-4187 URL: https://issues.apache.org/jira/browse/YARN-4187

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Description: Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Description: Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Summary: Yarn Client uses local address instead RM address as token renewer in a secure cluster when RM HA

[jira] [Updated] (YARN-4188) MoveApplicationAcrossQueuesResponse should be an abstract class

[ https://issues.apache.org/jira/browse/YARN-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-4188: --- Priority: Minor (was: Blocker) > MoveApplicationAcrossQueuesResponse should

[jira] [Created] (YARN-4188) MoveApplicationAcrossQueuesResponse should be an abstract class

Giovanni Matteo Fumarola created YARN-4188: -- Summary: MoveApplicationAcrossQueuesResponse should be an abstract class Key: YARN-4188 URL: https://issues.apache.org/jira/browse/YARN-4188

[jira] [Updated] (YARN-4188) MoveApplicationAcrossQueuesResponse should be an abstract class

[ https://issues.apache.org/jira/browse/YARN-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-4188: --- Target Version/s: (was: 2.7.0) > MoveApplicationAcrossQueuesResponse should

[jira] [Updated] (YARN-4188) MoveApplicationAcrossQueuesResponse should be an abstract class

[ https://issues.apache.org/jira/browse/YARN-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-4188: --- Labels: (was: 2.6.1-candidate) > MoveApplicationAcrossQueuesResponse should

[jira] [Updated] (YARN-4188) MoveApplicationAcrossQueuesResponse should be an abstract class

[ https://issues.apache.org/jira/browse/YARN-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-4188: --- Fix Version/s: (was: 2.6.1) (was: 2.7.0) >

[jira] [Assigned] (YARN-4188) MoveApplicationAcrossQueuesResponse should be an abstract class

[ https://issues.apache.org/jira/browse/YARN-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola reassigned YARN-4188: -- Assignee: Giovanni Matteo Fumarola (was: Brahma Reddy Battula) >

[jira] [Updated] (YARN-4188) MoveApplicationAcrossQueuesResponse should be an abstract class

[ https://issues.apache.org/jira/browse/YARN-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-4188: --- Description: MoveApplicationAcrossQueuesResponse should be an abstract class.

[jira] [Updated] (YARN-4187) Yarn Client uses local client address instead of RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Summary: Yarn Client uses local client address instead of RM address as token renewer in a secure cluster

[jira] [Updated] (YARN-4187) Yarn Client uses local address instead of RM address as token renewer in a secure cluster when RM HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4187: Summary: Yarn Client uses local address instead of RM address as token renewer in a secure cluster when RM

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

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

[jira] [Resolved] (YARN-4182) Killed containers disappear on app attempt page

[ https://issues.apache.org/jira/browse/YARN-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang resolved YARN-4182. -- Resolution: Duplicate > Killed containers disappear on app attempt page >

[jira] [Commented] (YARN-4182) Killed containers disappear on app attempt page

[ https://issues.apache.org/jira/browse/YARN-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805223#comment-14805223 ] Jeff Zhang commented on YARN-4182: -- Thanks [~bibinchundatt] Close it as duplicated and put comment in

[jira] [Commented] (YARN-2597) MiniYARNCluster should propagate reason for AHS not starting

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

[jira] [Created] (YARN-4182) Killed containers disappear on app attempt page

Jeff Zhang created YARN-4182: Summary: Killed containers disappear on app attempt page Key: YARN-4182 URL: https://issues.apache.org/jira/browse/YARN-4182 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805279#comment-14805279 ] Varun Saxena commented on YARN-2902: [~jlowe], bq. As far as properly handling DIE so we actually stop

[jira] [Commented] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType

[ https://issues.apache.org/jira/browse/YARN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805098#comment-14805098 ] Sunil G commented on YARN-4143: --- Sorry, for point 1, I meant adding below snippet. {code} // The working

[jira] [Commented] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType

[ https://issues.apache.org/jira/browse/YARN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805095#comment-14805095 ] Sunil G commented on YARN-4143: --- Hi [~adhoot] Thank you for sharing the patch. Yes, this overall helps to

[jira] [Updated] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

[ https://issues.apache.org/jira/browse/YARN-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4140: --- Attachment: 0006-YARN-4140.patch Attaching patch after update > RM container allocation

[jira] [Commented] (YARN-4113) RM should respect retry-interval when uses RetryPolicies.RETRY_FOREVER

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

[jira] [Updated] (YARN-4182) Killed containers disappear on app attempt page

[ https://issues.apache.org/jira/browse/YARN-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated YARN-4182: - Attachment: 2015-09-18_1601.png > Killed containers disappear on app attempt page >

[jira] [Commented] (YARN-2597) MiniYARNCluster should propagate reason for AHS not starting

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

[jira] [Commented] (YARN-3697) FairScheduler: ContinuousSchedulingThread can fail to shutdown

[ https://issues.apache.org/jira/browse/YARN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805084#comment-14805084 ] zhihai xu commented on YARN-3697: - I also cherry-picked the change from trunk to branch-2.7, Since

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

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

[jira] [Commented] (YARN-3603) Application Attempts page confusing

[ https://issues.apache.org/jira/browse/YARN-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805222#comment-14805222 ] Jeff Zhang commented on YARN-3603: -- [~sunilg] If it is "Running Container ID", is it still necessary to

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805281#comment-14805281 ] Varun Saxena commented on YARN-2902: I should say "This way localizer should quit quickly after

[jira] [Updated] (YARN-4181) node blacklist for AM launching

[ https://issues.apache.org/jira/browse/YARN-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hong Zhiguo updated YARN-4181: -- Description: In some cases, a node goes problematic and most launching containers fail on this node, as

[jira] [Commented] (YARN-4182) Killed containers disappear on app attempt page

[ https://issues.apache.org/jira/browse/YARN-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805183#comment-14805183 ] Bibin A Chundatt commented on YARN-4182: Its similar to YARN-3603 rt? > Killed containers

[jira] [Updated] (YARN-4177) yarn.util.Clock should not be used to time a duration or time interval

[ https://issues.apache.org/jira/browse/YARN-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-4177: -- Attachment: YARN-4177.002.patch Upload patch ver2. > yarn.util.Clock should not be used to time a

[jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

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

[jira] [Commented] (YARN-3975) WebAppProxyServlet should not redirect to RM page if AHS is enabled

[ https://issues.apache.org/jira/browse/YARN-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876238#comment-14876238 ] Jason Lowe commented on YARN-3975: -- Thanks for updating the patch, Mit! Looks good overall with just two

[jira] [Commented] (YARN-4180) AMLauncher does not retry on failures when talking to NM

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

[jira] [Commented] (YARN-4163) Audit getQueueInfo and getApplications calls

[ https://issues.apache.org/jira/browse/YARN-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876041#comment-14876041 ] Chang Li commented on YARN-4163: broken unit tests are unrelated. > Audit getQueueInfo and getApplications

[jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

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

[jira] [Created] (YARN-4186) Make WebAppUtils a public API for yarn

Jonathan Eagles created YARN-4186: - Summary: Make WebAppUtils a public API for yarn Key: YARN-4186 URL: https://issues.apache.org/jira/browse/YARN-4186 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-4185) Retry interval delay for NM client can be improved from the fixed static retry

Anubhav Dhoot created YARN-4185: --- Summary: Retry interval delay for NM client can be improved from the fixed static retry Key: YARN-4185 URL: https://issues.apache.org/jira/browse/YARN-4185 Project:

[jira] [Updated] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3985: Attachment: YARN-3985.003.patch > Make ReservationSystem persist state using RMStateStore

[jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

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

[jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

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

[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-tabpanel=14876038#comment-14876038 ] Anubhav Dhoot commented on YARN-2005: - Thanks [~jianhe], [~sunilg], [~jlowe] for the reviews and

[jira] [Updated] (YARN-4157) Merge YARN-1197 back to trunk

[ https://issues.apache.org/jira/browse/YARN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4157: - Attachment: YARN-1197.diff.5.patch Updated to latest diff. (ver.5) > Merge YARN-1197 back to trunk >

[jira] [Commented] (YARN-4074) [timeline reader] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876185#comment-14876185 ] Vrushali C commented on YARN-4074: -- Patch v8 looks good too me. Thanks for updating the test cases to use

[jira] [Commented] (YARN-4170) AM need to be notified with priority in AllocateResponse

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

[jira] [Commented] (YARN-4157) Merge YARN-1197 back to trunk

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

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

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

[jira] [Commented] (YARN-4189) Capacity Scheduler : Improve location preference waiting mechanism

[ https://issues.apache.org/jira/browse/YARN-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876871#comment-14876871 ] Xianyin Xin commented on YARN-4189: --- Hi [~leftnoteasy], just go through the doc. Please correct me if i

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

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

[jira] [Updated] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3920: -- Summary: FairScheduler container reservation on a node should be configurable to limit it to large

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

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

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876621#comment-14876621 ] Hudson commented on YARN-3920: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1153 (See

[jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

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

[jira] [Commented] (YARN-4131) Add API and CLI to kill container on given containerId

[ https://issues.apache.org/jira/browse/YARN-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876669#comment-14876669 ] Anubhav Dhoot commented on YARN-4131: - Can you please add [~kasha] and me to this? We are interested in

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

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

[jira] [Commented] (YARN-4180) AMLauncher does not retry on failures when talking to NM

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876583#comment-14876583 ] Robert Kanter commented on YARN-4180: - Looks good. Two minor things: - Can you look into the test

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876408#comment-14876408 ] Arun Suresh commented on YARN-3920: --- Committed to trunk and branch-2. > FairScheduler container

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876473#comment-14876473 ] Anubhav Dhoot commented on YARN-3920: - Thx [~asuresh] for review and commit! > FairScheduler container

[jira] [Commented] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType

[ https://issues.apache.org/jira/browse/YARN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876494#comment-14876494 ] Anubhav Dhoot commented on YARN-4143: - Cannot think of an API to add to the scheduler that will be

[jira] [Commented] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers

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

[jira] [Updated] (YARN-4044) Running applications information changes such as movequeue is not published to TimeLine server

[ https://issues.apache.org/jira/browse/YARN-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4044: -- Attachment: 0005-YARN-4044.patch Thank you. Uploading a new patch addressing test comments. > Running

[jira] [Commented] (YARN-3603) Application Attempts page confusing

[ https://issues.apache.org/jira/browse/YARN-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14847294#comment-14847294 ] Sunil G commented on YARN-3603: --- Hi [~jeffzhang] Thank you for pointing this. {{Container Exit Status}} must

[jira] [Commented] (YARN-4044) Running applications information changes such as movequeue is not published to TimeLine server

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

[jira] [Commented] (YARN-2597) MiniYARNCluster should propagate reason for AHS not starting

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

[jira] [Commented] (YARN-2597) MiniYARNCluster should propagate reason for AHS not starting

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

[jira] [Commented] (YARN-2597) MiniYARNCluster should propagate reason for AHS not starting

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

[jira] [Commented] (YARN-4181) node blacklist for AM launching

[ https://issues.apache.org/jira/browse/YARN-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875727#comment-14875727 ] Jason Lowe commented on YARN-4181: -- Dup of YARN-2005? > node blacklist for AM launching >

[jira] [Assigned] (YARN-4177) yarn.util.Clock should not be used to time a duration or time interval

[ https://issues.apache.org/jira/browse/YARN-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin reassigned YARN-4177: - Assignee: Xianyin Xin > yarn.util.Clock should not be used to time a duration or time interval >

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

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3816: - Attachment: YARN-3816-YARN-2928-v4.patch Update the patch according to latest patch checked in YARN-2928

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875721#comment-14875721 ] Jason Lowe commented on YARN-2902: -- bq. In container localizer, when processing HB DIE response, we send

[jira] [Commented] (YARN-2513) Host framework UIs in YARN for use with the ATS

[ https://issues.apache.org/jira/browse/YARN-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875732#comment-14875732 ] Jonathan Eagles commented on YARN-2513: --- [~xgong], [~zjshen], will you have time to review this

[jira] [Updated] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4138: Attachment: YARN-4138-YARN-1197.2.patch Submit an updated patch that includes extensive test cases. > Roll

  1   2   >