[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=16486713#comment-16486713 ] Dinesh Chitlangia commented on YARN-7340: - [~yufeigu] - I have updated the log message to reflect

[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=16486678#comment-16486678 ] Vinod Kumar Vavilapalli commented on YARN-8338: --- [~jlowe], never mind, removing the exclusion

[jira] [Updated] (YARN-4599) Set OOM control for memory cgroups

[ https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-4599: - Attachment: YARN-4599.016.patch > Set OOM control for memory cgroups >

[jira] [Commented] (YARN-7998) RM crashes with NPE during recovering if ACL configuration was changed

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

[jira] [Commented] (YARN-8310) Handle old NMTokenIdentifier, AMRMTokenIdentifier, and ContainerTokenIdentifier formats

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

[jira] [Commented] (YARN-8344) Missing nm.close() in TestNodeManagerResync to fix unit tests on Windows

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

[jira] [Commented] (YARN-8310) Handle old NMTokenIdentifier, AMRMTokenIdentifier, and ContainerTokenIdentifier formats

[ https://issues.apache.org/jira/browse/YARN-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486637#comment-16486637 ] Miklos Szegedi commented on YARN-8310: -- I will backport this to branches branch-2, branch-3.0 and

[jira] [Commented] (YARN-7998) RM crashes with NPE during recovering if ACL configuration was changed

[ https://issues.apache.org/jira/browse/YARN-7998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486638#comment-16486638 ] Wilfred Spiegelenburg commented on YARN-7998: - I don't think we should fail restore of a

[jira] [Commented] (YARN-8310) Handle old NMTokenIdentifier, AMRMTokenIdentifier, and ContainerTokenIdentifier formats

[ https://issues.apache.org/jira/browse/YARN-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486628#comment-16486628 ] Miklos Szegedi commented on YARN-8310: -- Committed to trunk. Thank you for the patch [~rkanter] and for

[jira] [Commented] (YARN-8310) Handle old NMTokenIdentifier, AMRMTokenIdentifier, and ContainerTokenIdentifier formats

[ https://issues.apache.org/jira/browse/YARN-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486626#comment-16486626 ] Miklos Szegedi commented on YARN-8310: -- +1 LGTM. > Handle old NMTokenIdentifier, AMRMTokenIdentifier,

[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=16486618#comment-16486618 ] genericqa commented on YARN-8292: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-8336) Fix potential connection leak in SchedConfCLI and YarnWebServiceUtils

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

[jira] [Commented] (YARN-8334) Fix potential connection leak in GPGUtils

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

[jira] [Commented] (YARN-8344) Missing nm.close() in TestNodeManagerResync to fix unit tests on Windows

[ https://issues.apache.org/jira/browse/YARN-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486577#comment-16486577 ] Giovanni Matteo Fumarola commented on YARN-8344: Missing nm.close let other unit tests to

[jira] [Updated] (YARN-8344) Missing nm.close() in TestNodeManagerResync to fix unit tests on Windows

[ https://issues.apache.org/jira/browse/YARN-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-8344: --- Summary: Missing nm.close() in TestNodeManagerResync to fix unit tests on

[jira] [Updated] (YARN-8344) Missing nm.close() in TestNodeManagerResync

[ https://issues.apache.org/jira/browse/YARN-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-8344: --- Attachment: YARN-8344.v1.patch > Missing nm.close() in TestNodeManagerResync >

[jira] [Created] (YARN-8344) Missing nm.close() in TestNodeManagerResync

Giovanni Matteo Fumarola created YARN-8344: -- Summary: Missing nm.close() in TestNodeManagerResync Key: YARN-8344 URL: https://issues.apache.org/jira/browse/YARN-8344 Project: Hadoop YARN

[jira] [Commented] (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:comment-tabpanel=16486545#comment-16486545 ] Vinod Kumar Vavilapalli commented on YARN-8342: --- Looks like the name

[jira] [Comment Edited] (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:comment-tabpanel=16486530#comment-16486530 ] Eric Yang edited comment on YARN-8342 at 5/23/18 12:58 AM: --- The current behavior

[jira] [Commented] (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:comment-tabpanel=16486530#comment-16486530 ] Eric Yang commented on YARN-8342: - The current behavior is documented in

[jira] [Commented] (YARN-8310) Handle old NMTokenIdentifier, AMRMTokenIdentifier, and ContainerTokenIdentifier formats

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

[jira] [Commented] (YARN-7899) [AMRMProxy] Stateful FederationInterceptor for pending requests

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

[jira] [Comment Edited] (YARN-8326) Yarn 3.0 seems runs slower than Yarn 2.6

[ https://issues.apache.org/jira/browse/YARN-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484721#comment-16484721 ] Hsin-Liang Huang edited comment on YARN-8326 at 5/23/18 12:18 AM: --

[jira] [Updated] (YARN-8334) Fix potential connection leak in GPGUtils

[ https://issues.apache.org/jira/browse/YARN-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-8334: --- Attachment: YARN-8334-YARN-7402.v2.patch > Fix potential connection leak in

[jira] [Updated] (YARN-8336) Fix potential connection leak in SchedConfCLI and YarnWebServiceUtils

[ https://issues.apache.org/jira/browse/YARN-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-8336: --- Attachment: YARN-8336.v2.patch > Fix potential connection leak in SchedConfCLI

[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=16485766#comment-16485766 ] genericqa commented on YARN-8316: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[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=16485752#comment-16485752 ] Vinod Kumar Vavilapalli commented on YARN-8338: --- [~jlowe], yeah, it wasn't easy to figure out

[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=16484735#comment-16484735 ] Wangda Tan commented on YARN-8292: -- Thanks [~jlowe], all great comments. Addressed all of them, please let

[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.007.patch > Fix the dominant resource preemption cannot happen when some of the

[jira] [Commented] (YARN-8326) Yarn 3.0 seems runs slower than Yarn 2.6

[ https://issues.apache.org/jira/browse/YARN-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484721#comment-16484721 ] Hsin-Liang Huang commented on YARN-8326: [~eyang]   this afternoon,  I tried the command and the

[jira] [Updated] (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 ] Shane Kumpf updated YARN-8342: -- Labels: Docker (was: ) > Using docker image from a non-privileged registry, the launch_command is not

[jira] [Updated] (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 ] Shane Kumpf updated YARN-8342: -- Issue Type: Sub-task (was: Bug) Parent: YARN-3611 > Using docker image from a non-privileged

[jira] [Updated] (YARN-8343) YARN should have ability to run images only from a whitelist docker registries

[ https://issues.apache.org/jira/browse/YARN-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Kumpf updated YARN-8343: -- Labels: Docker (was: ) > YARN should have ability to run images only from a whitelist docker registries

[jira] [Updated] (YARN-8343) YARN should have ability to run images only from a whitelist docker registries

[ https://issues.apache.org/jira/browse/YARN-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Kumpf updated YARN-8343: -- Issue Type: Sub-task (was: Bug) Parent: YARN-3611 > YARN should have ability to run images only

[jira] [Commented] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484708#comment-16484708 ] Kanwaljeet Sachdev commented on YARN-4677: -- +1 (non-binding) > RMNodeResourceUpdateEvent update

[jira] [Created] (YARN-8343) YARN should have ability to run images only from a whitelist docker registries

Wangda Tan created YARN-8343: Summary: YARN should have ability to run images only from a whitelist docker registries Key: YARN-8343 URL: https://issues.apache.org/jira/browse/YARN-8343 Project: Hadoop

[jira] [Commented] (YARN-8343) YARN should have ability to run images only from a whitelist docker registries

[ https://issues.apache.org/jira/browse/YARN-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484695#comment-16484695 ] Wangda Tan commented on YARN-8343: -- cc: [~shaneku...@gmail.com], [~eyang], [~ebadger], [~jlowe] > YARN

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

Wangda Tan created YARN-8342: Summary: Using docker image from a non-privileged registry, the launch_command is not honored Key: YARN-8342 URL: https://issues.apache.org/jira/browse/YARN-8342 Project:

[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=16484674#comment-16484674 ] Jason Lowe commented on YARN-8292: -- Thanks for updating the patch! Why does

[jira] [Comment Edited] (YARN-8334) Fix potential connection leak in GPGUtils

[ https://issues.apache.org/jira/browse/YARN-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484651#comment-16484651 ] Botong Huang edited comment on YARN-8334 at 5/22/18 10:03 PM: -- I realized that

[jira] [Comment Edited] (YARN-8334) Fix potential connection leak in GPGUtils

[ https://issues.apache.org/jira/browse/YARN-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484651#comment-16484651 ] Botong Huang edited comment on YARN-8334 at 5/22/18 10:01 PM: -- I realized that

[jira] [Updated] (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:all-tabpanel ] Billie Rinaldi updated YARN-8316: - Attachment: YARN-8316.001.patch > Diagnostic message should improve when yarn service fails to

[jira] [Commented] (YARN-8334) Fix potential connection leak in GPGUtils

[ https://issues.apache.org/jira/browse/YARN-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484651#comment-16484651 ] Botong Huang commented on YARN-8334: I realized that I confused destroy() with finalize() earlier. +1

[jira] [Commented] (YARN-8339) Service AM should localize static/archive resource types to container working directory instead of 'resources'

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

[jira] [Commented] (YARN-8273) Log aggregation does not warn if HDFS quota in target directory is exceeded

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

[jira] [Updated] (YARN-7899) [AMRMProxy] Stateful FederationInterceptor for pending requests

[ https://issues.apache.org/jira/browse/YARN-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-7899: --- Attachment: YARN-7899.v1.patch > [AMRMProxy] Stateful FederationInterceptor for pending requests >

[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=16484624#comment-16484624 ] Billie Rinaldi commented on YARN-8316: -- The issue here appears to be that the YarnClient is throwing a

[jira] [Comment Edited] (YARN-8341) Yarn Service: Integration tests

[ https://issues.apache.org/jira/browse/YARN-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484564#comment-16484564 ] Chandni Singh edited comment on YARN-8341 at 5/22/18 9:36 PM: -- The mvn

[jira] [Assigned] (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:all-tabpanel ] Billie Rinaldi reassigned YARN-8316: Assignee: Billie Rinaldi > Diagnostic message should improve when yarn service fails to

[jira] [Commented] (YARN-8332) Incorrect min/max allocation property name in resource types doc

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

[jira] [Commented] (YARN-8273) Log aggregation does not warn if HDFS quota in target directory is exceeded

[ https://issues.apache.org/jira/browse/YARN-8273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484588#comment-16484588 ] Robert Kanter commented on YARN-8273: - +1 LGTM > Log aggregation does not warn if HDFS quota in target

[jira] [Commented] (YARN-8290) SystemMetricsPublisher.appACLsUpdated should be invoked after application information is published to ATS to avoid "User is not set in the application report" Exception

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

[jira] [Updated] (YARN-8341) Yarn Service: Integration tests

[ https://issues.apache.org/jira/browse/YARN-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-8341: Attachment: (was: YARN-8341.wip.patch) > Yarn Service: Integration tests >

[jira] [Updated] (YARN-8341) Yarn Service: Integration tests

[ https://issues.apache.org/jira/browse/YARN-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-8341: Attachment: YARN-8341.wip.patch > Yarn Service: Integration tests >

[jira] [Commented] (YARN-8041) [Router] Federation: routing some missing REST invocations transparently to multiple RMs

[ https://issues.apache.org/jira/browse/YARN-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484576#comment-16484576 ] Giovanni Matteo Fumarola commented on YARN-8041: Thanks [~yiran] for the patch. I will take

[jira] [Commented] (YARN-8341) Yarn Service: Integration tests

[ https://issues.apache.org/jira/browse/YARN-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484564#comment-16484564 ] Chandni Singh commented on YARN-8341: - The mvn additions are in yarn-services-api pom. In order to run

[jira] [Updated] (YARN-8341) Yarn Service: Integration tests

[ https://issues.apache.org/jira/browse/YARN-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-8341: Attachment: YARN-8341.wip.patch > Yarn Service: Integration tests >

[jira] [Created] (YARN-8341) Yarn Service: Integration tests

Chandni Singh created YARN-8341: --- Summary: Yarn Service: Integration tests Key: YARN-8341 URL: https://issues.apache.org/jira/browse/YARN-8341 Project: Hadoop YARN Issue Type: Improvement

[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=16484553#comment-16484553 ] Wangda Tan commented on YARN-8320: -- Thanks [~cheersyang] / [~yangjiandan], I don't have much bandwidth to

[jira] [Commented] (YARN-8290) SystemMetricsPublisher.appACLsUpdated should be invoked after application information is published to ATS to avoid "User is not set in the application report" Exception

[ https://issues.apache.org/jira/browse/YARN-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484554#comment-16484554 ] Eric Yang commented on YARN-8290: - Thank you [~leftnoteasy] for the review and commit. >

[jira] [Updated] (YARN-8339) Service AM should localize static/archive resource types to container working directory instead of 'resources'

[ https://issues.apache.org/jira/browse/YARN-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8339: - Target Version/s: 3.1.1 Priority: Critical (was: Major) > Service AM should localize

[jira] [Commented] (YARN-8339) Service AM should localize static/archive resource types to container working directory instead of 'resources'

[ https://issues.apache.org/jira/browse/YARN-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484538#comment-16484538 ] Wangda Tan commented on YARN-8339: -- Thanks [~suma.shivaprasad] for the quick fix, patch LGTM, just

[jira] [Created] (YARN-8340) Capacity Scheduler Intra Queue Preemption Should Work When 3rd or more resources enabled.

Wangda Tan created YARN-8340: Summary: Capacity Scheduler Intra Queue Preemption Should Work When 3rd or more resources enabled. Key: YARN-8340 URL: https://issues.apache.org/jira/browse/YARN-8340

[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=16484519#comment-16484519 ] Wangda Tan commented on YARN-8292: -- Thanks [~eepayne], I just created YARN-8340 to track infra queue

[jira] [Commented] (YARN-8332) Incorrect min/max allocation property name in resource types doc

[ https://issues.apache.org/jira/browse/YARN-8332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484513#comment-16484513 ] Wangda Tan commented on YARN-8332: -- +1, committing .. > Incorrect min/max allocation property name in

[jira] [Commented] (YARN-8213) Add Capacity Scheduler metrics

[ https://issues.apache.org/jira/browse/YARN-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484509#comment-16484509 ] Wangda Tan commented on YARN-8213: -- [~cheersyang], I would prefer to not do that, many of such metrics for

[jira] [Updated] (YARN-8290) SystemMetricsPublisher.appACLsUpdated should be invoked after application information is published to ATS to avoid "User is not set in the application report" Exception

[ https://issues.apache.org/jira/browse/YARN-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8290: - Priority: Critical (was: Major) > SystemMetricsPublisher.appACLsUpdated should be invoked after

[jira] [Updated] (YARN-8290) SystemMetricsPublisher.appACLsUpdated should be invoked after application information is published to ATS to avoid "User is not set in the application report" Exception

[ https://issues.apache.org/jira/browse/YARN-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8290: - Summary: SystemMetricsPublisher.appACLsUpdated should be invoked after application information is

[jira] [Updated] (YARN-8290) SystemMetricsPublisher.appACLsUpdated should be invoked after application information is published to ATS to avoid

[ https://issues.apache.org/jira/browse/YARN-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8290: - Summary: SystemMetricsPublisher.appACLsUpdated should be invoked after application information is

[jira] [Commented] (YARN-8339) Service AM should localize static/archive resource types to container working directory instead of 'resources'

[ https://issues.apache.org/jira/browse/YARN-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484500#comment-16484500 ] genericqa commented on YARN-8339: - | (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=16484491#comment-16484491 ] Haibo Chen commented on YARN-8191: -- {quote}The point here is that the set of removed queues can be

[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=16484437#comment-16484437 ] genericqa commented on YARN-8338: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-8041) [Router] Federation: routing some missing REST invocations transparently to multiple RMs

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

[jira] [Commented] (YARN-7960) Add no-new-privileges flag to docker run

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

[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=16484398#comment-16484398 ] Jason Lowe commented on YARN-8338: -- To clarify, the reason the removal of the objenesis dependency didn't

[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=16484390#comment-16484390 ] Jason Lowe commented on YARN-8338: -- Thanks for the patch! Yeah, this looks like a case of a hidden

[jira] [Commented] (YARN-7960) Add no-new-privileges flag to docker run

[ https://issues.apache.org/jira/browse/YARN-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484385#comment-16484385 ] Eric Badger commented on YARN-7960: --- Thanks [~eyang] for the review/commit! > Add no-new-privileges flag

[jira] [Commented] (YARN-8206) Sending a kill does not immediately kill docker containers

[ https://issues.apache.org/jira/browse/YARN-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484382#comment-16484382 ] Eric Badger commented on YARN-8206: --- Wonderful! Thanks [~jlowe] for the review/commit and

[jira] [Resolved] (YARN-8335) Privileged docker containers' jobSubmitDir does not get successfully cleaned up

[ https://issues.apache.org/jira/browse/YARN-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger resolved YARN-8335. --- Resolution: Duplicate > Privileged docker containers' jobSubmitDir does not get successfully cleaned

[jira] [Commented] (YARN-8335) Privileged docker containers' jobSubmitDir does not get successfully cleaned up

[ https://issues.apache.org/jira/browse/YARN-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484379#comment-16484379 ] Eric Badger commented on YARN-8335: --- Hmm, good point. I guess I wouldn't say it's exactly a dup of

[jira] [Updated] (YARN-8339) Service AM should localize static/archive resource types to container working directory instead of 'resources'

[ https://issues.apache.org/jira/browse/YARN-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated YARN-8339: --- Attachment: YARN-8339.1.patch > Service AM should localize static/archive resource types to

[jira] [Created] (YARN-8339) Service AM should localize static/archive resource types to container working directory instead of 'resources' diurectory

Suma Shivaprasad created YARN-8339: -- Summary: Service AM should localize static/archive resource types to container working directory instead of 'resources' diurectory Key: YARN-8339 URL:

[jira] [Updated] (YARN-8339) Service AM should localize static/archive resource types to container working directory instead of 'resources'

[ https://issues.apache.org/jira/browse/YARN-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated YARN-8339: --- Summary: Service AM should localize static/archive resource types to container working

[jira] [Commented] (YARN-8336) Fix potential connection leak in SchedConfCLI and YarnWebServiceUtils

[ https://issues.apache.org/jira/browse/YARN-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484323#comment-16484323 ] Giovanni Matteo Fumarola commented on YARN-8336: I will fix findbugs warnings in the next

[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=16484310#comment-16484310 ] Vinod Kumar Vavilapalli commented on YARN-8338: --- Debugged this with [~leftnoteasy] and found

[jira] [Updated] (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:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-8338: -- Attachment: YARN-8338.txt > TimelineService V1.5 doesn't come up after

[jira] [Commented] (YARN-8041) [Router] Federation: routing some missing REST invocations transparently to multiple RMs

[ https://issues.apache.org/jira/browse/YARN-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484295#comment-16484295 ] Giovanni Matteo Fumarola commented on YARN-8041: [~yiran] thanks for the patch. The latest

[jira] [Commented] (YARN-8337) Deadlock In Federation Router

[ https://issues.apache.org/jira/browse/YARN-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484286#comment-16484286 ] Giovanni Matteo Fumarola commented on YARN-8337: Thanks [~jianchao jia] and [~yiran] for

[jira] [Commented] (YARN-8259) Revisit liveliness checks for Docker containers

[ https://issues.apache.org/jira/browse/YARN-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484271#comment-16484271 ] Eric Yang commented on YARN-8259: - [~shaneku...@gmail.com] The proposal for implementing both is okay, but

[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=16484257#comment-16484257 ] Eric Payne commented on YARN-8292: -- {quote}Actually this is required after the change. {quote} Yes, I see

[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=16484249#comment-16484249 ] Vinod Kumar Vavilapalli commented on YARN-8338: --- Full exception trace {code:java}

[jira] [Updated] (YARN-8041) [Router] Federation: routing some missing REST invocations transparently to multiple RMs

[ https://issues.apache.org/jira/browse/YARN-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiran Wu updated YARN-8041: --- Attachment: YARN-8041.007.patch > [Router] Federation: routing some missing REST invocations transparently to

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

Vinod Kumar Vavilapalli created YARN-8338: - Summary: TimelineService V1.5 doesn't come up after HADOOP-15406 Key: YARN-8338 URL: https://issues.apache.org/jira/browse/YARN-8338 Project: Hadoop

[jira] [Commented] (YARN-8041) [Router] Federation: routing some missing REST invocations transparently to multiple RMs

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

[jira] [Updated] (YARN-8232) RMContainer lost queue name when RM HA happens

[ https://issues.apache.org/jira/browse/YARN-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-8232: - Fix Version/s: 2.8.5 2.9.2 2.10.0 Thanks, [~ziqian hu]! We recently

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484199#comment-16484199 ] Eric Yang commented on YARN-8108: - [~yzhangal] This is a regression in Hadoop 3.x, hence it is marked as a

[jira] [Commented] (YARN-8206) Sending a kill does not immediately kill docker containers

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

[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=16484049#comment-16484049 ] Sunil Govindan commented on YARN-4781: -- Hi [~eepayne] Latest patch looks good to me. I tried to test

[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=16484050#comment-16484050 ] genericqa commented on YARN-8191: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-8041) [Router] Federation: routing some missing REST invocations transparently to multiple RMs

[ https://issues.apache.org/jira/browse/YARN-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiran Wu updated YARN-8041: --- Attachment: YARN-8041.005.patch > [Router] Federation: routing some missing REST invocations transparently to

  1   2   >