[jira] [Commented] (YARN-7340) Missing the time stamp in exception message in Class NoOverCommitPolicy

[ https://issues.apache.org/jira/browse/YARN-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488480#comment-16488480 ] Yufei Gu commented on YARN-7340: [~dineshchitlangia], sorry for delay. Other than the timestamp, we need to

[jira] [Updated] (YARN-8353) LightWeightResource's hashCode function is different from parent class

[ https://issues.apache.org/jira/browse/YARN-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8353: Description: LightWeightResource's hashCode function is different from parent class. One of the

[jira] [Updated] (YARN-8353) LightWeightResource's hashCode function is different from parent class

[ https://issues.apache.org/jira/browse/YARN-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8353: Description: LightWeightResource's hashCode function is different from parent class. One of the

[jira] [Commented] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

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

[jira] [Created] (YARN-8353) LightWeightResource's hashCode function is different from parent class

LongGang Chen created YARN-8353: --- Summary: LightWeightResource's hashCode function is different from parent class Key: YARN-8353 URL: https://issues.apache.org/jira/browse/YARN-8353 Project: Hadoop

[jira] [Updated] (YARN-8353) LightWeightResource's hashCode function is different from parent class

[ https://issues.apache.org/jira/browse/YARN-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8353: Description: LightWeightResource's hashCode function is different from parent class. One of the

[jira] [Updated] (YARN-8354) SingleConstraintAppPlacementAllocator's allocate does not decPendingResource

[ https://issues.apache.org/jira/browse/YARN-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8354: Description: SingleConstraintAppPlacementAllocator.allocate()  does not decPendingResource,only 

[jira] [Created] (YARN-8354) SingleConstraintAppPlacementAllocator's allocate does not decPendingResource

LongGang Chen created YARN-8354: --- Summary: SingleConstraintAppPlacementAllocator's allocate does not decPendingResource Key: YARN-8354 URL: https://issues.apache.org/jira/browse/YARN-8354 Project:

[jira] [Updated] (YARN-8353) LightWeightResource's hashCode function is different from parent class

[ https://issues.apache.org/jira/browse/YARN-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8353: Affects Version/s: 3.0.x > LightWeightResource's hashCode function is different from parent class >

[jira] [Updated] (YARN-8354) SingleConstraintAppPlacementAllocator's allocate does not decPendingResource

[ https://issues.apache.org/jira/browse/YARN-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8354: Affects Version/s: 3.0.x Component/s: RM > SingleConstraintAppPlacementAllocator's

[jira] [Updated] (YARN-8353) LightWeightResource's hashCode function is different from parent class

[ https://issues.apache.org/jira/browse/YARN-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8353: Component/s: RM > LightWeightResource's hashCode function is different from parent class >

[jira] [Commented] (YARN-8353) LightWeightResource's hashCode function is different from parent class

[ https://issues.apache.org/jira/browse/YARN-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488649#comment-16488649 ] Sunil Govindan commented on YARN-8353: -- Hi [~LongGang] We have 2 types of resources. For internal

[jira] [Updated] (YARN-8353) LightWeightResource's hashCode function is different from parent class

[ https://issues.apache.org/jira/browse/YARN-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8353: Description: LightWeightResource's hashCode function is different from parent class. One of the

[jira] [Commented] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488526#comment-16488526 ] Rohith Sharma K S commented on YARN-8346: - committing shortly > Upgrading to 3.1 kills running

[jira] [Commented] (YARN-8319) More YARN pages need to honor yarn.resourcemanager.display.per-user-apps

[ https://issues.apache.org/jira/browse/YARN-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488667#comment-16488667 ] Rohith Sharma K S commented on YARN-8319: - +1, will commit it shortly > More YARN pages need to

[jira] [Commented] (YARN-8338) TimelineService V1.5 doesn't come up after HADOOP-15406

[ https://issues.apache.org/jira/browse/YARN-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488692#comment-16488692 ] Akira Ajisaka commented on YARN-8338: - +1, thanks [~vinodkv] for reporting this issue and providing the

[jira] [Commented] (YARN-8319) More YARN pages need to honor yarn.resourcemanager.display.per-user-apps

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

[jira] [Updated] (YARN-8355) container update error because of competition

[ https://issues.apache.org/jira/browse/YARN-8355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LongGang Chen updated YARN-8355: Description: first, Quickly go through the update logic, Increase as an example： * 1: normal work

[jira] [Created] (YARN-8355) container update error because of competition

LongGang Chen created YARN-8355: --- Summary: container update error because of competition Key: YARN-8355 URL: https://issues.apache.org/jira/browse/YARN-8355 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-8356) yarn.log-aggregation why can auto clean

ma_lie created YARN-8356: Summary: yarn.log-aggregation why can auto clean Key: YARN-8356 URL: https://issues.apache.org/jira/browse/YARN-8356 Project: Hadoop YARN Issue Type: Wish

[jira] [Commented] (YARN-8338) TimelineService V1.5 doesn't come up after HADOOP-15406

[ https://issues.apache.org/jira/browse/YARN-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488742#comment-16488742 ] Steve Loughran commented on YARN-8338: -- {code} +-org.apache.hadoop:hadoop-aws:3.1.1-SNAPSHOT

[jira] [Commented] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488962#comment-16488962 ] Jason Lowe commented on YARN-8346: -- Thanks for the reviews! Does this need to go into branch-2.9 as well?

[jira] [Commented] (YARN-8320) Support CPU isolation for latency-sensitive (LS) service

[ https://issues.apache.org/jira/browse/YARN-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488899#comment-16488899 ] Weiwei Yang commented on YARN-8320: --- Hi [~leftnoteasy] Thanks for reviewing the design doc, very good

[jira] [Commented] (YARN-8352) AM should retry on a different node after the previous application attempt fail

[ https://issues.apache.org/jira/browse/YARN-8352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488969#comment-16488969 ] Jason Lowe commented on YARN-8352: -- Is this a duplicate of YARN-2005? This is filed against 2.7.5, but

[jira] [Updated] (YARN-6919) Add default volume mount list

[ https://issues.apache.org/jira/browse/YARN-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Kumpf updated YARN-6919: -- Attachment: YARN-6919-branch-3.1.002.patch > Add default volume mount list >

[jira] [Commented] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489047#comment-16489047 ] Rohith Sharma K S commented on YARN-8346: - back ported to 2.9 as well. > Upgrading to 3.1 kills

[jira] [Commented] (YARN-8356) yarn.log-aggregation why can auto clean

[ https://issues.apache.org/jira/browse/YARN-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488922#comment-16488922 ] Jason Lowe commented on YARN-8356: -- Couple of questions to clarify the setup: Is

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489132#comment-16489132 ] Gergo Repas commented on YARN-8191: --- Thanks [~haibochen]. I changed the return value 

[jira] [Updated] (YARN-8320) [Umbrella] Support CPU isolation for latency-sensitive (LS) service

[ https://issues.apache.org/jira/browse/YARN-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YARN-8320: -- Summary: [Umbrella] Support CPU isolation for latency-sensitive (LS) service (was: Support CPU

[jira] [Commented] (YARN-8279) AggregationLogDeletionService does not honor yarn.log-aggregation.IndexedFormat.remote-app-log-dir-suffix

[ https://issues.apache.org/jira/browse/YARN-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489061#comment-16489061 ] Jason Lowe commented on YARN-8279: -- Did this really occur in Hadoop 2.7.3?

[jira] [Commented] (YARN-4781) Support intra-queue preemption for fairness ordering policy.

[ https://issues.apache.org/jira/browse/YARN-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489086#comment-16489086 ] Sunil Govindan commented on YARN-4781: -- Yes. That makes sense to me. Thanks [~eepayne] If no

[jira] [Updated] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gergo Repas updated YARN-8191: -- Attachment: YARN-8191.016.patch > Fair scheduler: queue deletion without RM restart >

[jira] [Commented] (YARN-8338) TimelineService V1.5 doesn't come up after HADOOP-15406

[ https://issues.apache.org/jira/browse/YARN-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488908#comment-16488908 ] Jason Lowe commented on YARN-8338: -- My personal preference would be to use objenesis 1.0 in this JIRA to

[jira] [Updated] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8346: Fix Version/s: 2.9.2 > Upgrading to 3.1 kills running containers with error "Opportunistic

[jira] [Commented] (YARN-8279) AggregationLogDeletionService does not honor yarn.log-aggregation.IndexedFormat.remote-app-log-dir-suffix

[ https://issues.apache.org/jira/browse/YARN-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489024#comment-16489024 ] Tarun Parimi commented on YARN-8279: This issue occurs since LogAggregationIndexedFileController

[jira] [Commented] (YARN-8356) yarn.log-aggregation why can auto clean

[ https://issues.apache.org/jira/browse/YARN-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489063#comment-16489063 ] Jason Lowe commented on YARN-8356: -- I agree this looks very likely to be a duplicate of YARN-8279,

[jira] [Updated] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8292: - Attachment: YARN-8292.009.patch > Fix the dominant resource preemption cannot happen when some of the

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489384#comment-16489384 ] Wangda Tan commented on YARN-8292: -- Thanks [~jlowe]/[~eepayne], I just uploaded ver.9 patch addressed

[jira] [Commented] (YARN-6919) Add default volume mount list

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

[jira] [Commented] (YARN-8348) Incorrect and missing AfterClass in HBase-tests to fix NPE failures

[ https://issues.apache.org/jira/browse/YARN-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489300#comment-16489300 ] Giovanni Matteo Fumarola commented on YARN-8348: >From the [Linux run

[jira] [Commented] (YARN-8333) Load balance YARN services using RegistryDNS multiple A records

[ https://issues.apache.org/jira/browse/YARN-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489365#comment-16489365 ] Eric Yang commented on YARN-8333: - Patch 002 fixed check style issues. > Load balance YARN services using

[jira] [Commented] (YARN-6919) Add default volume mount list

[ https://issues.apache.org/jira/browse/YARN-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489232#comment-16489232 ] Shane Kumpf commented on YARN-6919: --- Thanks to [~ebadger] for the contribution and [~Jim_Brennan] for the

[jira] [Commented] (YARN-8348) Incorrect and missing AfterClass in HBase-tests to fix NPE failures

[ https://issues.apache.org/jira/browse/YARN-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489349#comment-16489349 ] Giovanni Matteo Fumarola commented on YARN-8348: I took another look at the failed tests

[jira] [Created] (YARN-8357) Yarn Service: NPE when service is saved first and then started.

Chandni Singh created YARN-8357: --- Summary: Yarn Service: NPE when service is saved first and then started. Key: YARN-8357 URL: https://issues.apache.org/jira/browse/YARN-8357 Project: Hadoop YARN

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

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

[jira] [Commented] (YARN-8320) [Umbrella] Support CPU isolation for latency-sensitive (LS) service

[ https://issues.apache.org/jira/browse/YARN-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489398#comment-16489398 ] Miklos Szegedi commented on YARN-8320: -- [~cheersyang] / [~yangjiandan], thank you for raising this,

[jira] [Assigned] (YARN-8342) Using docker image from a non-privileged registry, the launch_command is not honored

[ https://issues.apache.org/jira/browse/YARN-8342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang reassigned YARN-8342: --- Assignee: Eric Yang > Using docker image from a non-privileged registry, the launch_command is not >

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489192#comment-16489192 ] Jason Lowe commented on YARN-8292: -- Thanks for updating the patch! I agree with Eric's comment but

[jira] [Updated] (YARN-8333) Load balance YARN services using RegistryDNS multiple A records

[ https://issues.apache.org/jira/browse/YARN-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang updated YARN-8333: Attachment: YARN-8333.002.patch > Load balance YARN services using RegistryDNS multiple A records >

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489410#comment-16489410 ] Haibo Chen commented on YARN-8191: -- Findbugs is complaining about `return

[jira] [Commented] (YARN-8333) Load balance YARN services using RegistryDNS multiple A records

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

[jira] [Assigned] (YARN-6483) Add nodes transitioning to DECOMMISSIONING state to the list of updated nodes returned to the AM

[ https://issues.apache.org/jira/browse/YARN-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-6483: - Assignee: Arun Suresh (was: Juan Rodríguez Hortalá) > Add nodes transitioning to DECOMMISSIONING

[jira] [Assigned] (YARN-6483) Add nodes transitioning to DECOMMISSIONING state to the list of updated nodes returned to the AM

[ https://issues.apache.org/jira/browse/YARN-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-6483: - Assignee: Juan Rodríguez Hortalá (was: Arun Suresh) > Add nodes transitioning to DECOMMISSIONING

[jira] [Updated] (YARN-5764) NUMA awareness support for launching containers

[ https://issues.apache.org/jira/browse/YARN-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5764: - Fix Version/s: 3.2.0 3.1.0 > NUMA awareness support for launching containers >

[jira] [Commented] (YARN-6919) Add default volume mount list

[ https://issues.apache.org/jira/browse/YARN-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489243#comment-16489243 ] Eric Badger commented on YARN-6919: --- Thanks [~shaneku...@gmail.com] and [~Jim_Brennan]! > Add default

[jira] [Updated] (YARN-8068) Application Priority field causes NPE in app timeline publish when Hadoop 2.7 based clients to 2.8+

[ https://issues.apache.org/jira/browse/YARN-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-8068: - Fix Version/s: 2.9.2 2.10.0 Thanks, [~sunilg]! This fix needs to go everywhere

[jira] [Updated] (YARN-8357) Yarn Service: NPE when service is saved first and then started.

[ https://issues.apache.org/jira/browse/YARN-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-8357: Attachment: YARN-8357.001.patch > Yarn Service: NPE when service is saved first and then started. >

[jira] [Commented] (YARN-8357) Yarn Service: NPE when service is saved first and then started.

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

[jira] [Updated] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gergo Repas updated YARN-8191: -- Attachment: YARN-8191.017.patch > Fair scheduler: queue deletion without RM restart >

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489481#comment-16489481 ] Gergo Repas commented on YARN-8191: --- [~haibochen] - that's a nice catch, I fixed it. > Fair scheduler:

[jira] [Resolved] (YARN-8358) ResourceManager restart fail to recover due to TimelineServiceV1Publisher NPE

[ https://issues.apache.org/jira/browse/YARN-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-8358. -- Resolution: Duplicate > ResourceManager restart fail to recover due to TimelineServiceV1Publisher NPE >

[jira] [Commented] (YARN-8358) ResourceManager restart fail to recover due to TimelineServiceV1Publisher NPE

[ https://issues.apache.org/jira/browse/YARN-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489504#comment-16489504 ] Jason Lowe commented on YARN-8358: -- This looks like a duplicate of YARN-8068. Unfortunately that fix

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

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

[jira] [Created] (YARN-8358) ResourceManager restart fail to recover due to TimelineServiceV1Publisher NPE

Che Yufei created YARN-8358: --- Summary: ResourceManager restart fail to recover due to TimelineServiceV1Publisher NPE Key: YARN-8358 URL: https://issues.apache.org/jira/browse/YARN-8358 Project: Hadoop YARN

[jira] [Commented] (YARN-8068) Application Priority field causes NPE in app timeline publish when Hadoop 2.7 based clients to 2.8+

[ https://issues.apache.org/jira/browse/YARN-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489548#comment-16489548 ] Sunil Govindan commented on YARN-8068: -- Thanks [~jlowe]. Yes, we missed it earlier. Thanks for helping

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

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

[jira] [Commented] (YARN-8279) AggregationLogDeletionService does not honor yarn.log-aggregation.IndexedFormat.remote-app-log-dir-suffix

[ https://issues.apache.org/jira/browse/YARN-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489074#comment-16489074 ] Tarun Parimi commented on YARN-8279: [~jlowe] YARN-7072 seems to have been backported in HDP

[jira] [Commented] (YARN-6919) Add default volume mount list

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

[jira] [Commented] (YARN-8324) Fix TestPrivilegedOperationExecutor.testExecutorPath on Windows

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

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

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

[jira] [Commented] (YARN-8324) Fix TestPrivilegedOperationExecutor.testExecutorPath on Windows

[ https://issues.apache.org/jira/browse/YARN-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490082#comment-16490082 ] Íñigo Goiri commented on YARN-8324: --- Other than the checkstyle, this looks good. > Fix

[jira] [Commented] (YARN-8356) yarn.log-aggregation why can auto clean

[ https://issues.apache.org/jira/browse/YARN-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489028#comment-16489028 ] Tarun Parimi commented on YARN-8356: This issue seems to be the same as the one raised in YARN-8279 >

[jira] [Updated] (YARN-8279) AggregationLogDeletionService does not honor yarn.log-aggregation.IndexedFormat.remote-app-log-dir-suffix

[ https://issues.apache.org/jira/browse/YARN-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-8279: Affects Version/s: (was: 2.7.3) 2.9.1 > AggregationLogDeletionService

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489070#comment-16489070 ] Eric Payne commented on YARN-8292: -- [~leftnoteasy], thanks for the new patch. - In the following

[jira] [Commented] (YARN-8279) AggregationLogDeletionService does not honor yarn.log-aggregation.IndexedFormat.remote-app-log-dir-suffix

[ https://issues.apache.org/jira/browse/YARN-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489071#comment-16489071 ] Prabhu Joseph commented on YARN-8279: - [~jlowe] We have faced this on HDP Distribution with Hadoop

[jira] [Commented] (YARN-8316) Diagnostic message should improve when yarn service fails to launch due to ATS unavailability

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

[jira] [Commented] (YARN-8357) Yarn Service: NPE when service is saved first and then started.

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

[jira] [Assigned] (YARN-8360) Yarn service conflict between restart policy and NM configuration

[ https://issues.apache.org/jira/browse/YARN-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad reassigned YARN-8360: -- Assignee: Suma Shivaprasad > Yarn service conflict between restart policy and NM

[jira] [Commented] (YARN-8359) Disable containermanager.linux.runtime.TEST to run on Windows

[ https://issues.apache.org/jira/browse/YARN-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489884#comment-16489884 ] Giovanni Matteo Fumarola commented on YARN-8359: Thanks [~jlowe] , I have the same doubt

[jira] [Created] (YARN-8359) Disable containermanager.linux.runtime.TEST to run on Windows

Giovanni Matteo Fumarola created YARN-8359: -- Summary: Disable containermanager.linux.runtime.TEST to run on Windows Key: YARN-8359 URL: https://issues.apache.org/jira/browse/YARN-8359

[jira] [Created] (YARN-8360) Yarn service conflict between restart policy and NM configuration

Chandni Singh created YARN-8360: --- Summary: Yarn service conflict between restart policy and NM configuration Key: YARN-8360 URL: https://issues.apache.org/jira/browse/YARN-8360 Project: Hadoop YARN

[jira] [Updated] (YARN-8325) Miscellaneous QueueManager code clean up

[ https://issues.apache.org/jira/browse/YARN-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szilard Nemeth updated YARN-8325: - Attachment: YARN-8325.001.patch > Miscellaneous QueueManager code clean up >

[jira] [Updated] (YARN-8359) Disable containermanager.linux.runtime.TEST to run on Windows

[ https://issues.apache.org/jira/browse/YARN-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-8359: --- Description: Some of the tests in containermanager.linux.runtime failed in

[jira] [Updated] (YARN-8359) Disable containermanager.linux.runtime.TEST to run on Windows

[ https://issues.apache.org/jira/browse/YARN-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-8359: --- Description: Some of the tests in containermanager.linux.runtime failed in

[jira] [Commented] (YARN-8359) Disable containermanager.linux.runtime.TEST to run on Windows

[ https://issues.apache.org/jira/browse/YARN-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489749#comment-16489749 ] Giovanni Matteo Fumarola commented on YARN-8359: cc. [~gphillips] , [~rkanter], [~elgoiri],

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489751#comment-16489751 ] Haibo Chen commented on YARN-8191: -- +1 on the latest patch. Will check it in later today. > Fair

[jira] [Commented] (YARN-8357) Yarn Service: NPE when service is saved first and then started.

[ https://issues.apache.org/jira/browse/YARN-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489752#comment-16489752 ] Eric Yang commented on YARN-8357: - +1 looks good. > Yarn Service: NPE when service is saved first and then

[jira] [Updated] (YARN-7451) Resources Types should be visible in the Cluster Apps API "resourceRequests" section

[ https://issues.apache.org/jira/browse/YARN-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szilard Nemeth updated YARN-7451: - Attachment: YARN-7451.011.patch > Resources Types should be visible in the Cluster Apps API

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

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

[jira] [Commented] (YARN-8316) Diagnostic message should improve when yarn service fails to launch due to ATS unavailability

[ https://issues.apache.org/jira/browse/YARN-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489730#comment-16489730 ] Eric Yang commented on YARN-8316: - +1 looks good to me. > Diagnostic message should improve when yarn

[jira] [Updated] (YARN-8359) Disable containermanager.linux.runtime.TEST to run on Windows

[ https://issues.apache.org/jira/browse/YARN-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-8359: --- Description: Some of the tests in containermanager.linux.runtime failed in

[jira] [Commented] (YARN-8359) Disable containermanager.linux.runtime.TEST to run on Windows

[ https://issues.apache.org/jira/browse/YARN-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489807#comment-16489807 ] Jason Lowe commented on YARN-8359: -- The java package is containermanager.*linux*.runtime, so is it

[jira] [Created] (YARN-8361) Change App Name Placement Rule to use App Name instead of App Id for configuration

Zian Chen created YARN-8361: --- Summary: Change App Name Placement Rule to use App Name instead of App Id for configuration Key: YARN-8361 URL: https://issues.apache.org/jira/browse/YARN-8361 Project: Hadoop

[jira] [Commented] (YARN-8362) Number of remaining retries are updated twice after a container failure in NM

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

[jira] [Commented] (YARN-8361) Change App Name Placement Rule to use App Name instead of App Id for configuration

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

[jira] [Commented] (YARN-8320) [Umbrella] Support CPU isolation for latency-sensitive (LS) service

[ https://issues.apache.org/jira/browse/YARN-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490165#comment-16490165 ] Weiwei Yang commented on YARN-8320: --- Hi [~miklos.szeg...@cloudera.com] Thanks for the comments, please

[jira] [Updated] (YARN-8358) ResourceManager restart fail to recover due to TimelineServiceV1Publisher NPE

[ https://issues.apache.org/jira/browse/YARN-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Che Yufei updated YARN-8358: Description: I'm upgrading from Hadoop 2.7.3 to 2.9.1. ResourceManager restart works fine for 2.7.3, but

[jira] [Updated] (YARN-8358) ResourceManager restart fail to recover due to TimelineServiceV1Publisher NPE

[ https://issues.apache.org/jira/browse/YARN-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Che Yufei updated YARN-8358: Description: I'm upgrading from Hadoop 2.7.3 to 2.9.1. ResourceManager restart works fine for 2.7.3, but

[jira] [Commented] (YARN-8359) Disable containermanager.linux.runtime.TEST to run on Windows

[ https://issues.apache.org/jira/browse/YARN-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489917#comment-16489917 ] Íñigo Goiri commented on YARN-8359: --- I'm fine with using {{PlatformAssumptions.assumeNotWindows()}}. I'd

[jira] [Created] (YARN-8362) Number of remaining retries are updated twice after a container failure in NM

Chandni Singh created YARN-8362: --- Summary: Number of remaining retries are updated twice after a container failure in NM Key: YARN-8362 URL: https://issues.apache.org/jira/browse/YARN-8362 Project:

  1   2   >