[jira] [Commented] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state.

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635202#comment-14635202 ] Sumit Nigam commented on YARN-3946: --- Hi [~varun_saxena] - Yes, the idea is not to only

[jira] [Updated] (YARN-3941) Proportional Preemption policy should try to avoid sending duplicate PREEMPT_CONTAINER event to scheduler

[ https://issues.apache.org/jira/browse/YARN-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3941: -- Attachment: 0001-YARN-3941.patch Hi [~leftnoteasy] Uploading an initial version of patch. *testExpireKill*

[jira] [Updated] (YARN-3947) Add support for short host names in yarn decommissioning process

[ https://issues.apache.org/jira/browse/YARN-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Anand updated YARN-3947: - Description: When running {{yarn decommissioning}} the {{yarn rmadmin -refreshNodes}} doesn't like short

[jira] [Updated] (YARN-3947) Add support for short host names in yarn decommissioning process

[ https://issues.apache.org/jira/browse/YARN-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Anand updated YARN-3947: - Description: When running {{yarn decommissioning}} the {{yarn rmadmin -refreshNodes}} doesn't like short

[jira] [Updated] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3903: --- Fix Version/s: (was: 3.0.0) Disable preemption at Queue level for Fair Scheduler

[jira] [Updated] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3903: --- Assignee: (was: Karthik Kambatla) Disable preemption at Queue level for Fair Scheduler

[jira] [Updated] (YARN-3947) Add support for short host names in yarn decommissioning process

[ https://issues.apache.org/jira/browse/YARN-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Anand updated YARN-3947: - Description: When running {yarn decommissioning} the {{yarn rmadmin -refreshNodes}} doesn't like short

[jira] [Commented] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635332#comment-14635332 ] Karthik Kambatla commented on YARN-3903: I would like to understand the request

[jira] [Commented] (YARN-2019) Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635301#comment-14635301 ] Karthik Kambatla commented on YARN-2019: We could have two fail-fast configs - one

[jira] [Created] (YARN-3947) Add support for short host names in yarn decommissioning process

Amit Anand created YARN-3947: Summary: Add support for short host names in yarn decommissioning process Key: YARN-3947 URL: https://issues.apache.org/jira/browse/YARN-3947 Project: Hadoop YARN

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635292#comment-14635292 ] Jason Lowe commented on YARN-3591: -- Sorry for the delay, as I was on vacation and am still

[jira] [Commented] (YARN-3943) Use separate threshold configurations for disk-full detection and disk-not-full detection.

[ https://issues.apache.org/jira/browse/YARN-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635326#comment-14635326 ] Karthik Kambatla commented on YARN-3943: Marking it critical, since some users see

[jira] [Updated] (YARN-3943) Use separate threshold configurations for disk-full detection and disk-not-full detection.

[ https://issues.apache.org/jira/browse/YARN-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3943: --- Priority: Critical (was: Major) Use separate threshold configurations for disk-full

[jira] [Updated] (YARN-3952) Fix new findbugs warning in resourcemanager in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3952: --- Description: {noformat} file

[jira] [Updated] (YARN-3952) Fix new findbugs warning in resourcemanager in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3952: --- Description: {noformat} file

[jira] [Updated] (YARN-3952) Fix new findbugs warning in resourcemanager in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3952: --- Issue Type: Sub-task (was: Bug) Parent: YARN-2928 Fix new findbugs warning in

[jira] [Updated] (YARN-3952) Fix new findbugs warnings in resourcemanager in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3952: --- Summary: Fix new findbugs warnings in resourcemanager in YARN-2928 branch (was: Fix new findbugs

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635246#comment-14635246 ] Nathan Roberts commented on YARN-3945: -- My feeling is the documentation on

[jira] [Updated] (YARN-3947) Add support for short host names in yarn decommissioning process

[ https://issues.apache.org/jira/browse/YARN-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Anand updated YARN-3947: - Description: When running {{yarn decommissioning}} the {{yarn rmadmin -refreshNodes}} doesn't like short

[jira] [Commented] (YARN-3947) Add support for short host names in yarn decommissioning process

[ https://issues.apache.org/jira/browse/YARN-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635306#comment-14635306 ] Sunil G commented on YARN-3947: --- Hi [~aanand001c] I have a doubt here. If I configure

[jira] [Assigned] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YARN-3641: -- Assignee: Junping Du (was: Allen Wittenauer) NodeManager: stopRecoveryStore()

[jira] [Assigned] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YARN-3641: -- Assignee: Allen Wittenauer (was: Junping Du) NodeManager: stopRecoveryStore()

[jira] [Commented] (YARN-3874) Combine FS Reader and Writer Implementations

[ https://issues.apache.org/jira/browse/YARN-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635512#comment-14635512 ] Varun Saxena commented on YARN-3874: Many are not related as well. Combine FS Reader

[jira] [Commented] (YARN-3816) [Aggregation] App-level Aggregation for YARN system metrics

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635513#comment-14635513 ] Junping Du commented on YARN-3816: -- Thanks [~sjlee0] for review and comments! bq. If I

[jira] [Commented] (YARN-3838) Rest API failing when ip configured in RM address in secure https mode

[ https://issues.apache.org/jira/browse/YARN-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635534#comment-14635534 ] Bibin A Chundatt commented on YARN-3838: Hi [~xgong] any comments on this Rest

[jira] [Updated] (YARN-433) When RM is catching up with node updates then it should not expire acquired containers

[ https://issues.apache.org/jira/browse/YARN-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-433: --- Attachment: YARN-433.4.patch [~zxu] Thanks for the comments. Upload a new patch to address all the latest

[jira] [Commented] (YARN-3874) Combine FS Reader and Writer Implementations

[ https://issues.apache.org/jira/browse/YARN-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635482#comment-14635482 ] Varun Saxena commented on YARN-3874: Test failures are related. Will fix Combine FS

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

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

[jira] [Updated] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3932: --- Attachment: 0006-YARN-3932.patch Hi [~leftnoteasy] attaching patch again to retrigger CI and

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635499#comment-14635499 ] zhihai xu commented on YARN-3591: - +1 for [~jlowe]'s comment. Yes, It fixes some problems

[jira] [Commented] (YARN-3941) Proportional Preemption policy should try to avoid sending duplicate PREEMPT_CONTAINER event to scheduler

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

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3944: -- Priority: Critical (was: Blocker) Connection refused to nodemanagers are retried at multiple levels

[jira] [Created] (YARN-3948) Display Application Priority in RM Web UI

Sunil G created YARN-3948: - Summary: Display Application Priority in RM Web UI Key: YARN-3948 URL: https://issues.apache.org/jira/browse/YARN-3948 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-3874) Combine FS Reader and Writer Implementations

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

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635380#comment-14635380 ] Allen Wittenauer commented on YARN-3641: I can't see how to change this from

[jira] [Updated] (YARN-3261) rewrite resourcemanager restart doc to remove roadmap bits

[ https://issues.apache.org/jira/browse/YARN-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3261: --- Issue Type: Improvement (was: Bug) rewrite resourcemanager restart doc to remove roadmap

[jira] [Commented] (YARN-3261) rewrite resourcemanager restart doc to remove roadmap bits

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

[jira] [Commented] (YARN-3915) scmadmin help message correction

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

[jira] [Commented] (YARN-2003) Support for Application priority : Changes in RM and Capacity Scheduler

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

[jira] [Updated] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-3798: - Attachment: YARN-3798-branch-2.7.006.patch [~zxu] thank you for the comment. Attaching a patch to

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635531#comment-14635531 ] Robert Kanter commented on YARN-3528: - [~brahmareddy], are you still working on this?

[jira] [Commented] (YARN-2003) Support for Application priority : Changes in RM and Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635417#comment-14635417 ] Sunil G commented on YARN-2003: --- Thank you very much [~jianhe] and [~leftnoteasy] for

[jira] [Commented] (YARN-3926) Extend the YARN resource model for easier resource-type management and profiles

[ https://issues.apache.org/jira/browse/YARN-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636068#comment-14636068 ] Varun Vasudev commented on YARN-3926: - Thanks for the feedback [~kasha]! I'm fine with

[jira] [Created] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

Robert Kanter created YARN-3950: --- Summary: Add unique SHELL_ID environment variable to DistributedShell Key: YARN-3950 URL: https://issues.apache.org/jira/browse/YARN-3950 Project: Hadoop YARN

[jira] [Updated] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

[ https://issues.apache.org/jira/browse/YARN-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-3950: Attachment: YARN-3950.001.patch Add unique SHELL_ID environment variable to DistributedShell

[jira] [Commented] (YARN-3874) Optimize and synchronize FS Reader and Writer Implementations

[ https://issues.apache.org/jira/browse/YARN-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636204#comment-14636204 ] Varun Saxena commented on YARN-3874: Test failures are unrelated. They are due to a

[jira] [Commented] (YARN-445) Ability to signal containers

[ https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636221#comment-14636221 ] Joep Rottinghuis commented on YARN-445: --- Can we rekindle this discussion? We've had

[jira] [Commented] (YARN-3874) Optimize and synchronize FS Reader and Writer Implementations

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

[jira] [Commented] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636173#comment-14636173 ] He Tianyi commented on YARN-3903: - The latter one. I encountered the requirement that needs

[jira] [Created] (YARN-3952) Fix new findbugs warning in resourcemanager in YARN-2928 branch

Varun Saxena created YARN-3952: -- Summary: Fix new findbugs warning in resourcemanager in YARN-2928 branch Key: YARN-3952 URL: https://issues.apache.org/jira/browse/YARN-3952 Project: Hadoop YARN

[jira] [Updated] (YARN-3952) Fix new findbugs warnings in resourcemanager in YARN-2928 branch

[ https://issues.apache.org/jira/browse/YARN-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3952: --- Description: {noformat} file

[jira] [Commented] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

[ https://issues.apache.org/jira/browse/YARN-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636134#comment-14636134 ] Allen Wittenauer commented on YARN-3950: This needs to be either YARN_SHELL_ID or

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636244#comment-14636244 ] Joep Rottinghuis commented on YARN-3176: For the record, we're running with this

[jira] [Updated] (YARN-3250) Support admin cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3250: -- Summary: Support admin cli interface in for Application Priority (was: Support admin cli interface in

[jira] [Commented] (YARN-3460) Test TestSecureRMRegistryOperations failed with IBM_JAVA JVM

[ https://issues.apache.org/jira/browse/YARN-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635624#comment-14635624 ] Allen Wittenauer commented on YARN-3460: {code} +Method methodInitialize = +

[jira] [Commented] (YARN-433) When RM is catching up with node updates then it should not expire acquired containers

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

[jira] [Commented] (YARN-3925) ContainerLogsUtils#getContainerLogFile fails to read container log files from full disks.

[ https://issues.apache.org/jira/browse/YARN-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635546#comment-14635546 ] Jason Lowe commented on YARN-3925: -- Nice catch, [~zxu]! I think the patch will work, but

[jira] [Commented] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

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

[jira] [Updated] (YARN-3874) Optimize and synchronize FS Reader and Writer Implementations

[ https://issues.apache.org/jira/browse/YARN-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3874: --- Summary: Optimize and synchronize FS Reader and Writer Implementations (was: Combine FS Reader and

[jira] [Commented] (YARN-2019) Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635876#comment-14635876 ] Junping Du commented on YARN-2019: -- If so, I think we should at least differentiate RM and

[jira] [Commented] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

[ https://issues.apache.org/jira/browse/YARN-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635892#comment-14635892 ] Anubhav Dhoot commented on YARN-3878: - Agree this is ok to ignore AsyncDispatcher can

[jira] [Commented] (YARN-3460) Test TestSecureRMRegistryOperations failed with IBM_JAVA JVM

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

[jira] [Commented] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635727#comment-14635727 ] Bibin A Chundatt commented on YARN-3932: [~leftnoteasy] checkstyle issue is already

[jira] [Created] (YARN-3949) ensure timely flush of timeline writes

Sangjin Lee created YARN-3949: - Summary: ensure timely flush of timeline writes Key: YARN-3949 URL: https://issues.apache.org/jira/browse/YARN-3949 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635754#comment-14635754 ] Sangjin Lee commented on YARN-3908: --- I filed YARN-3949 to address the need for timely

[jira] [Updated] (YARN-3874) Optimize and synchronize FS Reader and Writer Implementations

[ https://issues.apache.org/jira/browse/YARN-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3874: --- Attachment: YARN-3874-YARN-2928.02.patch Optimize and synchronize FS Reader and Writer

[jira] [Commented] (YARN-3852) Add docker container support to container-executor

[ https://issues.apache.org/jira/browse/YARN-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635872#comment-14635872 ] Abin Shahab commented on YARN-3852: --- The test failures are unrelated to the

[jira] [Commented] (YARN-3852) Add docker container support to container-executor

[ https://issues.apache.org/jira/browse/YARN-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635879#comment-14635879 ] Varun Vasudev commented on YARN-3852: - Thanks for the latest patch [~ashahab]. Patch

[jira] [Commented] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

[ https://issues.apache.org/jira/browse/YARN-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635897#comment-14635897 ] Jian He commented on YARN-3878: --- thanks ! committing this. AsyncDispatcher can hang while

[jira] [Commented] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

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

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635761#comment-14635761 ] Tsuyoshi Ozawa commented on YARN-3798: -- The test result is as follows: {quote} -1

[jira] [Created] (YARN-3951) Test case failures in TestLogAggregationService, TestResourceLocalizationService TestContainer

Naganarasimha G R created YARN-3951: --- Summary: Test case failures in TestLogAggregationService, TestResourceLocalizationService TestContainer Key: YARN-3951 URL: https://issues.apache.org/jira/browse/YARN-3951

[jira] [Commented] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636089#comment-14636089 ] Naganarasimha G R commented on YARN-3045: - Test case failures and white space issue

[jira] [Commented] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

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

[jira] [Assigned] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YARN-3641: -- Assignee: Allen Wittenauer (was: Junping Du) NodeManager: stopRecoveryStore()

[jira] [Updated] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3641: --- Reporter: Junping Du (was: Allen Wittenauer) NodeManager: stopRecoveryStore() shouldn't be

[jira] [Reopened] (YARN-2921) Fix MockRM/MockAM#waitForState sleep too long

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reopened YARN-2921: Fix MockRM/MockAM#waitForState sleep too long -

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635996#comment-14635996 ] Sangjin Lee commented on YARN-3908: --- [~jrottinghuis], [~vrushalic], and I had offline

[jira] [Commented] (YARN-3299) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635940#comment-14635940 ] Xuan Gong commented on YARN-3299: - Resolving this umbrella JIRA. And as new

[jira] [Resolved] (YARN-3299) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong resolved YARN-3299. - Resolution: Fixed Synchronize RM and Generic History Service Web-UIs

[jira] [Commented] (YARN-1645) ContainerManager implementation to support container resizing

[ https://issues.apache.org/jira/browse/YARN-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635954#comment-14635954 ] Jian He commented on YARN-1645: --- looks good, +1 ContainerManager implementation to support

[jira] [Updated] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3641: --- Reporter: Allen Wittenauer (was: Junping Du) NodeManager: stopRecoveryStore() shouldn't be

[jira] [Updated] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3641: --- Assignee: Junping Du (was: Allen Wittenauer) NodeManager: stopRecoveryStore() shouldn't be

[jira] [Resolved] (YARN-2921) Fix MockRM/MockAM#waitForState sleep too long

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-2921. Resolution: Fixed Fix MockRM/MockAM#waitForState sleep too long

[jira] [Commented] (YARN-1645) ContainerManager implementation to support container resizing

[ https://issues.apache.org/jira/browse/YARN-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635991#comment-14635991 ] Wangda Tan commented on YARN-1645: -- +1 to latest patch, thanks [~mding].

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636009#comment-14636009 ] Li Lu commented on YARN-3908: - Hi [~sjlee0], I don't think we're still using event type in new

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636050#comment-14636050 ] Sangjin Lee commented on YARN-3908: --- Hmm, then isn't this incorrect?

[jira] [Commented] (YARN-3949) ensure timely flush of timeline writes

[ https://issues.apache.org/jira/browse/YARN-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636056#comment-14636056 ] Sangjin Lee commented on YARN-3949: --- For background, HBase's {{BufferedMutatorImpl}} does

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636058#comment-14636058 ] Li Lu commented on YARN-3908: - Hi [~sjlee0], I think the code you posted here belongs to

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14636057#comment-14636057 ] Sangjin Lee commented on YARN-3908: --- Sorry my bad. I mistakenly pulled up the v.1 of

[jira] [Commented] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

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

[jira] [Updated] (YARN-3932) SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel

[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3932: --- Attachment: 0005-YARN-3932.patch Attaching patch after whitespace fix

[jira] [Created] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state.

Sumit Nigam created YARN-3946: - Summary: Allow fetching exact reason as to why a submitted app is in ACCEPTED state. Key: YARN-3946 URL: https://issues.apache.org/jira/browse/YARN-3946 Project: Hadoop

[jira] [Updated] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state.

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Nigam updated YARN-3946: -- Description: Currently there is no direct way to get the exact reason as to why a submitted app is still

[jira] [Commented] (YARN-2019) Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634638#comment-14634638 ] Karthik Kambatla commented on YARN-2019: How about adopting the approach proposed

[jira] [Commented] (YARN-2019) Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634951#comment-14634951 ] Junping Du commented on YARN-2019: -- +1 on general idea of YARN-3607. However, here users

[jira] [Commented] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state.

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634956#comment-14634956 ] Varun Saxena commented on YARN-3946: [~sumit.nigam], thanks for reporting the issue.

[jira] [Commented] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state.

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634961#comment-14634961 ] Varun Saxena commented on YARN-3946: I hope the intention is primarily debugging and

[jira] [Updated] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3045: Attachment: YARN-3045-YARN-2928.006.patch Hi [~djp] [~varun_saxena] , I have addressed

[jira] [Commented] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state.

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634979#comment-14634979 ] Naganarasimha G R commented on YARN-3946: - @Sumit Nigam, if you are not working on

  1   2   >