[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395084#comment-15395084 ] Rohith Sharma K S commented on YARN-5431: - I think since it new opts being added, what varun says

[jira] [Commented] (YARN-5195) RM intermittently crashed with NPE while handling APP_ATTEMPT_REMOVED event when async-scheduling enabled in CapacityScheduler

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

[jira] [Commented] (YARN-5342) Improve non-exclusive node partition resource allocation in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395019#comment-15395019 ] Wangda Tan commented on YARN-5342: -- Committed to trunk/branch-2. [~sunilg], mind to update the patch to

[jira] [Commented] (YARN-4091) Add REST API to retrieve scheduler activity

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

[jira] [Commented] (YARN-3662) Federation Membership State Store internal APIs

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

[jira] [Commented] (YARN-5113) Refactoring and other clean-up for distributed scheduling

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

[jira] [Commented] (YARN-5327) API changes required to support recurring reservations in the YARN ReservationSystem

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

[jira] [Commented] (YARN-5287) LinuxContainerExecutor fails to set proper permission

[ https://issues.apache.org/jira/browse/YARN-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394986#comment-15394986 ] Ying Zhang commented on YARN-5287: -- Thanks Naganarasimha and Rohith for review. I've updated the patch

[jira] [Commented] (YARN-5079) [Umbrella] Native YARN framework layer for services and beyond

[ https://issues.apache.org/jira/browse/YARN-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394979#comment-15394979 ] Vinod Kumar Vavilapalli commented on YARN-5079: --- bq. I'm going to go ahead with creating a

[jira] [Updated] (YARN-3662) Federation Membership State Store internal APIs

[ https://issues.apache.org/jira/browse/YARN-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3662: - Attachment: YARN-3662-YARN-2915-v5.patch Thanks [~vvasudev] for the clarifications. I have

[jira] [Updated] (YARN-5312) Parameter 'size' in the webservices "/containerlogs/$containerid/$filename" and in AHSWebServices is semantically confusing

[ https://issues.apache.org/jira/browse/YARN-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-5312: -- Issue Type: Sub-task (was: Bug) Parent: YARN-4904 > Parameter 'size' in

[jira] [Commented] (YARN-5081) Replace RPC calls with WebService calls in LogsCLI

[ https://issues.apache.org/jira/browse/YARN-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394958#comment-15394958 ] Vinod Kumar Vavilapalli commented on YARN-5081: --- bq. To goal is to remove

[jira] [Commented] (YARN-5203) Return ResourceRequest JAXB object in ResourceManager Cluster Applications REST API

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

[jira] [Updated] (YARN-5327) API changes required to support recurring reservations in the YARN ReservationSystem

[ https://issues.apache.org/jira/browse/YARN-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Abdu Jyothi updated YARN-5327: Attachment: YARN-5327.001.patch > API changes required to support recurring

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerRequestKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394949#comment-15394949 ] Subru Krishnan commented on YARN-5392: -- Thanks [~asuresh] for driving this and [~leftnoteasy]/[~kasha]

[jira] [Commented] (YARN-5351) ResourceRequest should take ExecutionType into account during comparison

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

[jira] [Commented] (YARN-5351) ResourceRequest should take ExecutionType into account during comparison

[ https://issues.apache.org/jira/browse/YARN-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394930#comment-15394930 ] Arun Suresh commented on YARN-5351: --- +1, Committing this shortly > ResourceRequest should take

[jira] [Commented] (YARN-5342) Improve non-exclusive node partition resource allocation in Capacity Scheduler

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

[jira] [Updated] (YARN-4091) Add REST API to retrieve scheduler activity

[ https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Ge updated YARN-4091: -- Attachment: YARN-4091.4.patch updated with new version > Add REST API to retrieve scheduler activity >

[jira] [Updated] (YARN-5203) Return ResourceRequest JAXB object in ResourceManager Cluster Applications REST API

[ https://issues.apache.org/jira/browse/YARN-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ellen Hui updated YARN-5203: Attachment: YARN-5203.v4.patch Thanks [~subru] for the feedback. - Add ExecutionTypeRequestInfo object -

[jira] [Updated] (YARN-5113) Refactoring and other clean-up for distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos updated YARN-5113: - Attachment: YARN-5113.007.patch Fixing unit test failures, checkstyle, whitespace

[jira] [Commented] (YARN-5342) Improve non-exclusive node partition resource allocation in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394891#comment-15394891 ] Wangda Tan commented on YARN-5342: -- Committing this. > Improve non-exclusive node partition resource

[jira] [Commented] (YARN-5432) Lock already held by another process while LevelDB cache store creation for dag

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

[jira] [Commented] (YARN-4091) Add REST API to retrieve scheduler activity

[ https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394834#comment-15394834 ] Wangda Tan commented on YARN-4091: -- Created a new parent JIRA (YARN-5437) and moved all original children

[jira] [Updated] (YARN-4091) Add REST API to retrieve scheduler activity

[ https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4091: - Summary: Add REST API to retrieve scheduler activity (was: Improvement: Introduce more debug/diagnostics

[jira] [Updated] (YARN-4091) Improvement: Introduce more debug/diagnostics information to detail out scheduler activity

[ https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4091: - Issue Type: Sub-task (was: Improvement) Parent: YARN-5437 > Improvement: Introduce more

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

[ https://issues.apache.org/jira/browse/YARN-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4329: - Parent Issue: YARN-5437 (was: YARN-4091) > Allow fetching exact reason as to why a submitted app is in

[jira] [Updated] (YARN-4490) RM restart the finished app shows wrong Diagnostics status

[ https://issues.apache.org/jira/browse/YARN-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4490: - Parent Issue: YARN-5437 (was: YARN-4091) > RM restart the finished app shows wrong Diagnostics status >

[jira] [Updated] (YARN-4192) Add YARN metric logging periodically to a seperate file

[ https://issues.apache.org/jira/browse/YARN-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4192: - Parent Issue: YARN-5437 (was: YARN-4091) > Add YARN metric logging periodically to a seperate file >

[jira] [Updated] (YARN-4104) dryrun of schedule for diagnostic and tenant's complain

[ https://issues.apache.org/jira/browse/YARN-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4104: - Parent Issue: YARN-5437 (was: YARN-4091) > dryrun of schedule for diagnostic and tenant's complain >

[jira] [Updated] (YARN-3946) Update exact reason as to why a submitted app is in ACCEPTED state to app's diagnostic message

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3946: - Parent Issue: YARN-5437 (was: YARN-4091) > Update exact reason as to why a submitted app is in ACCEPTED

[jira] [Created] (YARN-5437) [Umbrella] Add more debug/diagnostic messages to scheduler

Wangda Tan created YARN-5437: Summary: [Umbrella] Add more debug/diagnostic messages to scheduler Key: YARN-5437 URL: https://issues.apache.org/jira/browse/YARN-5437 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-5432) Lock already held by another process while LevelDB cache store creation for dag

[ https://issues.apache.org/jira/browse/YARN-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-5432: Attachment: YARN-5432-trunk.003.patch Fix checkstyle issues. > Lock already held by another process while LevelDB

[jira] [Commented] (YARN-5432) Lock already held by another process while LevelDB cache store creation for dag

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

[jira] [Updated] (YARN-5436) Race in AsyncDispatcher can cause random test failures in Tez(probably YARN also )

[ https://issues.apache.org/jira/browse/YARN-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated YARN-5436: --- Description: In YARN-2264, a race in DrainDispatcher was fixed. Unfortunately, it also exists in

[jira] [Updated] (YARN-5432) Lock already held by another process while LevelDB cache store creation for dag

[ https://issues.apache.org/jira/browse/YARN-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-5432: Attachment: YARN-5432-trunk.002.patch Had some offline discussion with [~djp]. Seems we're on a track of

[jira] [Created] (YARN-5436) Race in AsyncDispatcher can cause random test failures in Tez(probably YARN also )

Zhiyuan Yang created YARN-5436: -- Summary: Race in AsyncDispatcher can cause random test failures in Tez(probably YARN also ) Key: YARN-5436 URL: https://issues.apache.org/jira/browse/YARN-5436 Project:

[jira] [Created] (YARN-5435) User AM resource limit for does not get updated for ReservationQueue after execution of plan-follower.

Sean Po created YARN-5435: - Summary: User AM resource limit for does not get updated for ReservationQueue after execution of plan-follower. Key: YARN-5435 URL: https://issues.apache.org/jira/browse/YARN-5435

[jira] [Commented] (YARN-5434) Add -client|server argument for graceful decom

[ https://issues.apache.org/jira/browse/YARN-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394708#comment-15394708 ] Robert Kanter commented on YARN-5434: - Remaining checkstyle is in line with the current formatting of

[jira] [Commented] (YARN-5382) RM does not audit log kill request for active applications

[ https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394699#comment-15394699 ] Jason Lowe commented on YARN-5382: -- Note that if the trunk patch applies as-is to branch-2 (as I suspect

[jira] [Commented] (YARN-5382) RM does not audit log kill request for active applications

[ https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394696#comment-15394696 ] Vrushali C commented on YARN-5382: -- Thanks [~jlowe]! I will make the changes and upload an updated patch

[jira] [Commented] (YARN-5382) RM does not audit log kill request for active applications

[ https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394678#comment-15394678 ] Jason Lowe commented on YARN-5382: -- Thanks for the update, Vrushali! I should have said this earlier:

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerRequestKey

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

[jira] [Commented] (YARN-5434) Add -client|server argument for graceful decom

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

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerRequestKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Summary: Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerRequestKey

[jira] [Commented] (YARN-5351) ResourceRequest should take ExecutionType into account during comparison

[ https://issues.apache.org/jira/browse/YARN-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394595#comment-15394595 ] Konstantinos Karanasos commented on YARN-5351: -- The three test methods of {{TestYarnClient}}

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394594#comment-15394594 ] Karthik Kambatla commented on YARN-5392: +1. Thanks for your patience through the reviews, Arun.

[jira] [Updated] (YARN-5434) Add -client|server argument for graceful decom

[ https://issues.apache.org/jira/browse/YARN-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-5434: Attachment: YARN-5343.002.patch The 002 patch fixes some of the checkstyle warnings. The remaining

[jira] [Commented] (YARN-5428) Allow for specifying the docker client configuration directory

[ https://issues.apache.org/jira/browse/YARN-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394591#comment-15394591 ] Shane Kumpf commented on YARN-5428: --- As previously mentioned, the checkstyle failures are because two

[jira] [Commented] (YARN-5434) Add -client|server argument for graceful decom

[ https://issues.apache.org/jira/browse/YARN-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394582#comment-15394582 ] Karthik Kambatla commented on YARN-5434: Marking this a blocker for 5.8.0 to ensure we maintain

[jira] [Updated] (YARN-5434) Add -client|server argument for graceful decom

[ https://issues.apache.org/jira/browse/YARN-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5434: --- Priority: Blocker (was: Major) > Add -client|server argument for graceful decom >

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394580#comment-15394580 ] Arun Suresh commented on YARN-5392: --- The test failure is unrelated > Replace use of Priority in the

[jira] [Commented] (YARN-5434) Add -client|server argument for graceful decom

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

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

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

[jira] [Commented] (YARN-5404) Add the ability to split reverse zone subnets

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

[jira] [Updated] (YARN-5404) Add the ability to split reverse zone subnets

[ https://issues.apache.org/jira/browse/YARN-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Kumpf updated YARN-5404: -- Attachment: YARN-5404-YARN-4757.002.patch > Add the ability to split reverse zone subnets >

[jira] [Updated] (YARN-5434) Add -client|server argument for graceful decom

[ https://issues.apache.org/jira/browse/YARN-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-5434: Attachment: YARN-5343.001.patch [~djp] > Add -client|server argument for graceful decom >

[jira] [Commented] (YARN-5434) Add -client|server argument for graceful decom

[ https://issues.apache.org/jira/browse/YARN-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394512#comment-15394512 ] Robert Kanter commented on YARN-5434: - I also noticed that the optional timeout isn't actually optional

[jira] [Created] (YARN-5434) Add -client|server argument for graceful decom

Robert Kanter created YARN-5434: --- Summary: Add -client|server argument for graceful decom Key: YARN-5434 URL: https://issues.apache.org/jira/browse/YARN-5434 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-5425) TestDirectoryCollection.testCreateDirectories failed

[ https://issues.apache.org/jira/browse/YARN-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu reassigned YARN-5425: -- Assignee: Yufei Gu > TestDirectoryCollection.testCreateDirectories failed >

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.010.patch Hmm.. Being a test class, I did not want to modify any more of it than

[jira] [Commented] (YARN-5137) Make DiskChecker pluggable in NodeManager

[ https://issues.apache.org/jira/browse/YARN-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394456#comment-15394456 ] Ray Chiang commented on YARN-5137: -- Yeah, I think the fix to LinuxContainerExecutor and

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394449#comment-15394449 ] Karthik Kambatla commented on YARN-5392: In my comments above, 2.1 still applies. Otherwise, looks

[jira] [Commented] (YARN-5404) Add the ability to split reverse zone subnets

[ https://issues.apache.org/jira/browse/YARN-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394441#comment-15394441 ] Shane Kumpf commented on YARN-5404: --- Uploading a new patch that addresses the comments above. Please let

[jira] [Commented] (YARN-5429) Fix @return related javadoc warnings in yarn-api

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

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394356#comment-15394356 ] Allen Wittenauer commented on YARN-5431: FWIW, I'm planning on making this all consistent in trunk

[jira] [Commented] (YARN-5432) Lock already held by another process while LevelDB cache store creation for dag

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

[jira] [Commented] (YARN-5382) RM does not audit log kill request for active applications

[ https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394338#comment-15394338 ] Vrushali C commented on YARN-5382: -- Thanks [~sunilg]! [~jlowe] Would appreciate your feedback as well..

[jira] [Updated] (YARN-5429) Fix @return related javadoc warnings in yarn-api

[ https://issues.apache.org/jira/browse/YARN-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5429: - Attachment: YARN-5429.02.patch Thanks [~varun_saxena], yes fixed the minor checkstyle issue and uploading

[jira] [Updated] (YARN-5432) Lock already held by another process while LevelDB cache store creation for dag

[ https://issues.apache.org/jira/browse/YARN-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-5432: Attachment: YARN-5432-trunk.001.patch Upload a patch to fix this issue. It fixes the problems on two sides: 1. using

[jira] [Commented] (YARN-5432) Lock already held by another process while LevelDB cache store creation for dag

[ https://issues.apache.org/jira/browse/YARN-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394287#comment-15394287 ] Li Lu commented on YARN-5432: - Thanks for reporting this issue [~karams]! The main cause of this issue is

[jira] [Commented] (YARN-5137) Make DiskChecker pluggable in NodeManager

[ https://issues.apache.org/jira/browse/YARN-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394278#comment-15394278 ] Yufei Gu commented on YARN-5137: The failed tests are unrelated. > Make DiskChecker pluggable in

[jira] [Updated] (YARN-5264) Use FSQueue to store queue-specific information

[ https://issues.apache.org/jira/browse/YARN-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5264: --- Attachment: YARN-5264.002.patch Uploaded patch 002 to solve the test failures. > Use FSQueue to store

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394191#comment-15394191 ] Varun Saxena commented on YARN-5431: I am not sure why changes for all the daemons were not made as

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394151#comment-15394151 ] Rohith Sharma K S commented on YARN-5431: - Changing from {{HADOOP_TIMELINEREADER_OPTS}} to

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394125#comment-15394125 ] Varun Saxena commented on YARN-5431: I think last point should be fine. Because we capture which daemon

[jira] [Comment Edited] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394115#comment-15394115 ] Varun Saxena edited comment on YARN-5431 at 7/26/16 5:18 PM: - [~rohithsharma],

[jira] [Comment Edited] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394115#comment-15394115 ] Varun Saxena edited comment on YARN-5431 at 7/26/16 5:16 PM: - [~rohithsharma],

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394115#comment-15394115 ] Varun Saxena commented on YARN-5431: [~rohithsharma], I would prefer to name the opts as

[jira] [Updated] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5431: Attachment: YARN-5431.1.patch Thanks [~aw] for pointing out which are all the files to be

[jira] [Updated] (YARN-5422) ContainerLocalizer log should be logged in separate log file.

[ https://issues.apache.org/jira/browse/YARN-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-5422: --- Assignee: Surendra Singh Lilhore > ContainerLocalizer log should be logged in separate log file. >

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

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

[jira] [Commented] (YARN-5433) Audit dependencies for Category-X

[ https://issues.apache.org/jira/browse/YARN-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393978#comment-15393978 ] Sean Busbey commented on YARN-5433: --- fixing the findbugs annotations jar is easy, we just need to exclude

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393974#comment-15393974 ] Varun Saxena commented on YARN-5431: I have reverted the commit. [~rohithsharma], kindly make the

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393975#comment-15393975 ] Allen Wittenauer commented on YARN-5431: It also needs to get added to yarn.cmd. > TimeLineReader

[jira] [Reopened] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reopened YARN-5431: > TimeLineReader daemon start should allow to pass its own reader opts >

[jira] [Created] (YARN-5433) Audit dependencies for Category-X

Sean Busbey created YARN-5433: - Summary: Audit dependencies for Category-X Key: YARN-5433 URL: https://issues.apache.org/jira/browse/YARN-5433 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393965#comment-15393965 ] Varun Saxena commented on YARN-5431: Oops, sorry, I did not know about. > TimeLineReader daemon start

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393959#comment-15393959 ] Varun Saxena commented on YARN-5431: Committed to trunk. Thanks Rohith for your contribution >

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393960#comment-15393960 ] Allen Wittenauer commented on YARN-5431: Where's the yarn-env.sh documentation? > TimeLineReader

[jira] [Commented] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

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

[jira] [Commented] (YARN-5287) LinuxContainerExecutor fails to set proper permission

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

[jira] [Commented] (YARN-5428) Allow for specifying the docker client configuration directory

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

[jira] [Updated] (YARN-5431) TimeLineReader daemon start should allow to pass its own reader opts

[ https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-5431: --- Fix Version/s: (was: 3.0.0-alpha1) 3.0.0-alpha2 > TimeLineReader daemon start

[jira] [Commented] (YARN-5404) Add the ability to split reverse zone subnets

[ https://issues.apache.org/jira/browse/YARN-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393932#comment-15393932 ] Shane Kumpf commented on YARN-5404: --- Thanks for the review [~vvasudev]! I'll get these fixed up and a new

[jira] [Commented] (YARN-5402) Fix NoSuchMethodError in ClusterMetricsInfo

[ https://issues.apache.org/jira/browse/YARN-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393923#comment-15393923 ] Weiwei Yang commented on YARN-5402: --- Hello [~sunilg] I did not try on trunk yet, I can give a try

[jira] [Updated] (YARN-5432) Lock already held by another process while LevelDB cache store creation for dag

[ https://issues.apache.org/jira/browse/YARN-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-5432: - Assignee: Li Lu > Lock already held by another process while LevelDB cache store creation for > dag >

[jira] [Updated] (YARN-5287) LinuxContainerExecutor fails to set proper permission

[ https://issues.apache.org/jira/browse/YARN-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-5287: - Attachment: YARN-5287.004.patch > LinuxContainerExecutor fails to set proper permission >

[jira] [Updated] (YARN-5428) Allow for specifying the docker client configuration directory

[ https://issues.apache.org/jira/browse/YARN-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Kumpf updated YARN-5428: -- Attachment: YARN-5428.002.patch > Allow for specifying the docker client configuration directory >

[jira] [Commented] (YARN-5428) Allow for specifying the docker client configuration directory

[ https://issues.apache.org/jira/browse/YARN-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393865#comment-15393865 ] Shane Kumpf commented on YARN-5428: --- After taking a harder looking, adding this to the DockerCommand

  1   2   >