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

[ https://issues.apache.org/jira/browse/YARN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082641#comment-15082641 ] zhihai xu commented on YARN-3697: - [~djp], yes, I just committed it to branch-2.6. thanks > FairScheduler:

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

[ https://issues.apache.org/jira/browse/YARN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3697: Fix Version/s: 2.6.4 > FairScheduler: ContinuousSchedulingThread can fail to shutdown >

[jira] [Updated] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4538: --- Priority: Major (was: Critical) > QueueMetrics pending cores and memory metrics wrong >

[jira] [Commented] (YARN-3446) FairScheduler HeadRoom calculation should exclude nodes in the blacklist.

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

[jira] [Created] (YARN-4543) TestNodeStatusUpdater.testStopReentrant fails + JUnit misusage

Akihiro Suda created YARN-4543: -- Summary: TestNodeStatusUpdater.testStopReentrant fails + JUnit misusage Key: YARN-4543 URL: https://issues.apache.org/jira/browse/YARN-4543 Project: Hadoop YARN

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

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

[jira] [Updated] (YARN-4544) All the log messages about rolling monitoring interval are shown with the WARN level

[ https://issues.apache.org/jira/browse/YARN-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takashi Ohnishi updated YARN-4544: -- Attachment: YARN-4544.patch Attached a patch. > All the log messages about rolling monitoring

[jira] [Commented] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

[ https://issues.apache.org/jira/browse/YARN-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083308#comment-15083308 ] Sunil G commented on YARN-4537: --- Thanks Rohith. Yes, Its fine. > Pull out priority comparison from

[jira] [Commented] (YARN-4544) All the log messages about rolling monitoring interval are shown with the WARN level

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

[jira] [Commented] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

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

[jira] [Commented] (YARN-4425) Pluggable sharing policy for Partition Node Label resources

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

[jira] [Updated] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

[ https://issues.apache.org/jira/browse/YARN-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4537: Attachment: 0003-YARN-4537.patch [~sunilg] I updated patch avoiding expression evaluation

[jira] [Updated] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-4311: -- Attachment: YARN-4311-v4.patch Thanks [~templedf]. Attaching an updated patch. I removed the null check

[jira] [Commented] (YARN-4479) Retrospect app-priority in pendingOrderingPolicy during recovering applications

[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083283#comment-15083283 ] Sunil G commented on YARN-4479: --- Patch looks good [~rohithsharma]. > Retrospect app-priority in

[jira] [Commented] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

[ https://issues.apache.org/jira/browse/YARN-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083305#comment-15083305 ] Rohith Sharma K S commented on YARN-4537: - One small update I have done and updated it. > Pull out

[jira] [Commented] (YARN-4224) Support fetching entities by UID and change the REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083381#comment-15083381 ] Varun Saxena commented on YARN-4224: bq. One quick thing is about TimelineReaderContext. This class

[jira] [Commented] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

[ https://issues.apache.org/jira/browse/YARN-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083309#comment-15083309 ] Sunil G commented on YARN-4537: --- Thanks Rohith. Yes, Its fine. > Pull out priority comparison from

[jira] [Updated] (YARN-3692) Allow REST API to set a user generated message when killing an application

[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3692: Description: Currently YARN's REST API supports killing an application without setting a

[jira] [Commented] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083163#comment-15083163 ] Junping Du commented on YARN-4265: -- Thanks [~gtCarrera9] for reply and updating the patch. I am still

[jira] [Comment Edited] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083223#comment-15083223 ] Karthik Kambatla edited comment on YARN-1011 at 1/5/16 3:28 PM: We would

[jira] [Updated] (YARN-4479) Retrospect app-priority in pendingOrderingPolicy during recovering applications

[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4479: Attachment: 0005-YARN-4479.patch > Retrospect app-priority in pendingOrderingPolicy during

[jira] [Updated] (YARN-4425) Pluggable sharing policy for Partition Node Label resources

[ https://issues.apache.org/jira/browse/YARN-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4425: Attachment: YARN-4425.20160105-1.patch

[jira] [Created] (YARN-4544) All the log messages about rolling monitoring interval are shown with the WARN level

Takashi Ohnishi created YARN-4544: - Summary: All the log messages about rolling monitoring interval are shown with the WARN level Key: YARN-4544 URL: https://issues.apache.org/jira/browse/YARN-4544

[jira] [Commented] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

[ https://issues.apache.org/jira/browse/YARN-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083287#comment-15083287 ] Sunil G commented on YARN-4537: --- +1. Looks good. > Pull out priority comparison from fifocomparator and use

[jira] [Commented] (YARN-4425) Pluggable sharing policy for Partition Node Label resources

[ https://issues.apache.org/jira/browse/YARN-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083167#comment-15083167 ] Naganarasimha G R commented on YARN-4425: - Further i tried to consider your comment ??I can

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083223#comment-15083223 ] Karthik Kambatla commented on YARN-1011: We would run an opportunistic container on a node only if

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083226#comment-15083226 ] Karthik Kambatla commented on YARN-1011: Since the plan is develop this on a branch, we could get

[jira] [Commented] (YARN-4479) Retrospect app-priority in pendingOrderingPolicy during recovering applications

[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083248#comment-15083248 ] Rohith Sharma K S commented on YARN-4479: - updated 0005-YARN-4479 patch , kindly review it >

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083538#comment-15083538 ] Wangda Tan commented on YARN-4304: -- Hi Sunil, Thanks for update, I can still see

[jira] [Commented] (YARN-4224) Support fetching entities by UID and change the REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083473#comment-15083473 ] Li Lu commented on YARN-4224: - Thanks Varun. bq. /flows endpoint is for querying active flows with default

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: 0009-YARN-4304.patch Thank You [~leftnoteasy] Uploading a new patch addressing the comments. Also

[jira] [Commented] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083480#comment-15083480 ] Li Lu commented on YARN-4265: - bq. Can we provide a default one (could be simple) for built-in YARN

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: (was: REST_and_UI.zip) > AM max resource configuration per partition to be displayed/updated

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: REST_and_UI.zip Uploading screen shots and REST o/p as per latest change > AM max resource

[jira] [Created] (YARN-4545) Allow YARN distributed shell to use ATS v1.5 APIs

Li Lu created YARN-4545: --- Summary: Allow YARN distributed shell to use ATS v1.5 APIs Key: YARN-4545 URL: https://issues.apache.org/jira/browse/YARN-4545 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-4479) Retrospect app-priority in pendingOrderingPolicy during recovering applications

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

[jira] [Commented] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

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

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

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

[jira] [Commented] (YARN-3089) LinuxContainerExecutor does not handle file arguments to deleteAsUser

[ https://issues.apache.org/jira/browse/YARN-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083077#comment-15083077 ] Jason Lowe commented on YARN-3089: -- As I mentioned in my last comment above, this shouldn't be needed in

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083683#comment-15083683 ] Bikas Saha commented on YARN-1011: -- Good points but let me play the devils advocate to get some more

[jira] [Assigned] (YARN-3934) Application with large ApplicationSubmissionContext can cause RM to exit when ZK store is used

[ https://issues.apache.org/jira/browse/YARN-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote reassigned YARN-3934: - Assignee: Dustin Cote > Application with large ApplicationSubmissionContext can cause RM to exit

[jira] [Resolved] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen resolved YARN-4539. Resolution: Fixed > CommonNodeLabelsManager throw NullPointerException when the fairScheduler >

[jira] [Commented] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

[ https://issues.apache.org/jira/browse/YARN-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084943#comment-15084943 ] Naganarasimha G R commented on YARN-4537: - +1 LGTM > Pull out priority comparison from

[jira] [Updated] (YARN-4479) Retrospect app-priority in pendingOrderingPolicy during recovering applications

[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4479: Attachment: 0006-YARN-4479.patch Updating the patch fixing test failure for

[jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085011#comment-15085011 ] Bibin A Chundatt commented on YARN-4538: Test failures are not related to patch attached. All CI

[jira] [Commented] (YARN-4479) Retrospect app-priority in pendingOrderingPolicy during recovering applications

[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084608#comment-15084608 ] Jian He commented on YARN-4479: --- +1, [~rohithsharma], could you see if the warnings are related > Retrospect

[jira] [Created] (YARN-4547) LeagQueue#getApplications() is read-only interface, but it provides reference to caller

Rohith Sharma K S created YARN-4547: --- Summary: LeagQueue#getApplications() is read-only interface, but it provides reference to caller Key: YARN-4547 URL: https://issues.apache.org/jira/browse/YARN-4547

[jira] [Updated] (YARN-4547) LeagQueue#getApplications() is read-only interface, but it provides reference to caller

[ https://issues.apache.org/jira/browse/YARN-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4547: Description: The below API is read-only interface, but returning reference to the caller.

[jira] [Resolved] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-4539. - Resolution: Duplicate > CommonNodeLabelsManager throw NullPointerException when the

[jira] [Reopened] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reopened YARN-4539: - Reopening the issue for making duplicate > CommonNodeLabelsManager throw NullPointerException

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084576#comment-15084576 ] tangshangwen commented on YARN-4539: OK, Thanks [~bibinchundatt] > CommonNodeLabelsManager throw

[jira] [Reopened] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen reopened YARN-4539: > CommonNodeLabelsManager throw NullPointerException when the fairScheduler > init failed >

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084602#comment-15084602 ] Rohith Sharma K S commented on YARN-4539: - Hi [~tangshangwen], when closing the issue as a

[jira] [Resolved] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen resolved YARN-4539. Resolution: Duplicate > CommonNodeLabelsManager throw NullPointerException when the fairScheduler >

[jira] [Commented] (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:comment-tabpanel=15085027#comment-15085027 ] Naganarasimha G R commented on YARN-3946: - I will take a look and update, Thanks for informing ! >

[jira] [Updated] (YARN-4547) LeafQueue#getApplications() is read-only interface, but it provides reference to caller

[ https://issues.apache.org/jira/browse/YARN-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4547: Summary: LeafQueue#getApplications() is read-only interface, but it provides reference to

[jira] [Commented] (YARN-4238) createdTime and modifiedTime is not reported while publishing entities to ATSv2

[ https://issues.apache.org/jira/browse/YARN-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084955#comment-15084955 ] Naganarasimha G R commented on YARN-4238: - IMO i dont see much value or usecase for *modified

[jira] [Commented] (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:comment-tabpanel=15085012#comment-15085012 ] Akira AJISAKA commented on YARN-3946: - Hi [~Naganarasimha] and [~leftnoteasy], TestNetworkedJob is

[jira] [Updated] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4538: --- Attachment: 0001-YARN-4538.patch Thanks for looking into the issue, [~leftnoteasy] * Added

[jira] [Commented] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

[ https://issues.apache.org/jira/browse/YARN-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084606#comment-15084606 ] Rohith Sharma K S commented on YARN-4537: - test case failures are handled in YARN-4306, > Pull

[jira] [Created] (YARN-4548) TestCapacityScheduler.testRecoverRequestAfterPreemption fails with NPE

Akihiro Suda created YARN-4548: -- Summary: TestCapacityScheduler.testRecoverRequestAfterPreemption fails with NPE Key: YARN-4548 URL: https://issues.apache.org/jira/browse/YARN-4548 Project: Hadoop YARN

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084575#comment-15084575 ] tangshangwen commented on YARN-4539: OK, Thanks [~bibinchundatt] > CommonNodeLabelsManager throw

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084562#comment-15084562 ] Bibin A Chundatt commented on YARN-4539: [~tangshangwen] Can we close this jira? >

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084611#comment-15084611 ] Sunil G commented on YARN-4304: --- Hi [~leftnoteasy] Thannk you for pointing out. As I see it,

[jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

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

[jira] [Commented] (YARN-4168) Test TestLogAggregationService.testLocalFileDeletionOnDiskFull failing

[ https://issues.apache.org/jira/browse/YARN-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085020#comment-15085020 ] Akihiro Suda commented on YARN-4168: I'm also hitting this one and YARN-1978. > Test

[jira] [Commented] (YARN-1978) TestLogAggregationService#testLocalFileDeletionAfterUpload fails sometimes

[ https://issues.apache.org/jira/browse/YARN-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085021#comment-15085021 ] Akihiro Suda commented on YARN-1978: I'm also hitting this one and YARN-4168. >

[jira] [Commented] (YARN-4335) Allow ResourceRequests to specify ExecutionType of a request ask

[ https://issues.apache.org/jira/browse/YARN-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083929#comment-15083929 ] Arun Suresh commented on YARN-4335: --- [~leftnoteasy], YARN-2885 depends on this.. and YARN-4412 depends on

[jira] [Commented] (YARN-4546) ResourceManager crash due to scheduling opportunity overflow

[ https://issues.apache.org/jira/browse/YARN-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083927#comment-15083927 ] Jason Lowe commented on YARN-4546: -- When the overflow occurs the RM crashes with a stacktrace like this:

[jira] [Commented] (YARN-4200) Refactor reader classes in storage to nest under hbase specific package name

[ https://issues.apache.org/jira/browse/YARN-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083932#comment-15083932 ] Vrushali C commented on YARN-4200: -- Hi [~gtCarrera] The patch looks good but I believe it's outdated now

[jira] [Commented] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083940#comment-15083940 ] Wangda Tan commented on YARN-2885: -- Thanks [~asuresh], I'm fine with this patch's logic to interact with

[jira] [Commented] (YARN-4356) ensure the timeline service v.2 is disabled cleanly and has no impact when it's turned off

[ https://issues.apache.org/jira/browse/YARN-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083947#comment-15083947 ] Vrushali C commented on YARN-4356: -- Hmm. I am not sure if it is inconsistent. The actual behavior right

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083957#comment-15083957 ] Bikas Saha commented on YARN-1011: -- I agree with natural container churn in favor of preemption to avoid

[jira] [Commented] (YARN-4356) ensure the timeline service v.2 is disabled cleanly and has no impact when it's turned off

[ https://issues.apache.org/jira/browse/YARN-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083959#comment-15083959 ] Li Lu commented on YARN-4356: - Ah OK. But we do need to update the actual code when we introduce a new version

[jira] [Updated] (YARN-4546) ResourceManager crash due to scheduling opportunity overflow

[ https://issues.apache.org/jira/browse/YARN-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-4546: - Attachment: YARN-4546.001.patch Patch to cap scheduling opportunities so they don't overflow. >

[jira] [Commented] (YARN-4200) Refactor reader classes in storage to nest under hbase specific package name

[ https://issues.apache.org/jira/browse/YARN-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083933#comment-15083933 ] Li Lu commented on YARN-4200: - Sure. Will do that soon. Thanks! > Refactor reader classes in storage to nest

[jira] [Commented] (YARN-4356) ensure the timeline service v.2 is disabled cleanly and has no impact when it's turned off

[ https://issues.apache.org/jira/browse/YARN-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083938#comment-15083938 ] Li Lu commented on YARN-4356: - One quick query w.r.t changes in this JIRA: I just noticed that in

[jira] [Commented] (YARN-4238) createdTime and modifiedTime is not reported while publishing entities to ATSv2

[ https://issues.apache.org/jira/browse/YARN-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083941#comment-15083941 ] Vrushali C commented on YARN-4238: -- The hbase cell timestamps may not indicate the actual entity

[jira] [Commented] (YARN-4200) Refactor reader classes in storage to nest under hbase specific package name

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

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083974#comment-15083974 ] Jason Lowe commented on YARN-1011: -- bq. Tasks are incorrectly over-allocated. Will never use the resources

[jira] [Commented] (YARN-4356) ensure the timeline service v.2 is disabled cleanly and has no impact when it's turned off

[ https://issues.apache.org/jira/browse/YARN-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083994#comment-15083994 ] Vrushali C commented on YARN-4356: -- Yes, if we want the behavior to be different. If the 2.1 behavior

[jira] [Updated] (YARN-4335) Allow ResourceRequests to specify ExecutionType of a request ask

[ https://issues.apache.org/jira/browse/YARN-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos updated YARN-4335: - Attachment: YARN-4335.002.patch New version of the patch, addressing

[jira] [Commented] (YARN-4335) Allow ResourceRequests to specify ExecutionType of a request ask

[ https://issues.apache.org/jira/browse/YARN-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082917#comment-15082917 ] Konstantinos Karanasos commented on YARN-4335: -- Thank you for the feedback, [~leftnoteasy]. I

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083880#comment-15083880 ] Nathan Roberts commented on YARN-1011: -- Very excited about this feature and agree that we should make

[jira] [Commented] (YARN-4335) Allow ResourceRequests to specify ExecutionType of a request ask

[ https://issues.apache.org/jira/browse/YARN-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083919#comment-15083919 ] Wangda Tan commented on YARN-4335: -- Thanks [~kkaranasos] for updating the patch bq. Just double-checking:

[jira] [Moved] (YARN-4546) ResourceManager crash due to scheduling opportunity overflow

[ https://issues.apache.org/jira/browse/YARN-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe moved MAPREDUCE-6599 to YARN-4546: - Affects Version/s: (was: 2.6.1) 2.6.1

[jira] [Updated] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4265: Attachment: YARN-4265-trunk.003.patch Refresh the patch once more to: # Add documentations about cache item and its

[jira] [Updated] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

[ https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-4161: Attachment: YARN-4161.patch Attaching patch > Capacity Scheduler : Assign single or multiple

[jira] [Commented] (YARN-4541) Change log message in LocalizedResource#handle() to DEBUG

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

[jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083846#comment-15083846 ] Wangda Tan commented on YARN-4538: -- Thanks for reporting this issue, [~bibinchundatt]. The root cause is

[jira] [Commented] (YARN-4541) Change log message in LocalizedResource#handle() to DEBUG

[ https://issues.apache.org/jira/browse/YARN-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083857#comment-15083857 ] Ray Chiang commented on YARN-4541: -- No test needed for variable name fix. > Change log message in

[jira] [Commented] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

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

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083905#comment-15083905 ] Wangda Tan commented on YARN-1011: -- bq. So, hopefully we can make the policy quite configurable so that

[jira] [Commented] (YARN-3692) Allow REST API to set a user generated message when killing an application

[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083018#comment-15083018 ] Rohith Sharma K S commented on YARN-3692: - Thanks [~Naganarasimha Garla] and [~jlowe] for sharing

[jira] [Commented] (YARN-4542) Cleanup AHS code and configuration

[ https://issues.apache.org/jira/browse/YARN-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083029#comment-15083029 ] Junping Du commented on YARN-4542: -- Hi Naga, please feel free to take it up. Thanks! > Cleanup AHS code

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

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083031#comment-15083031 ] Junping Du commented on YARN-2902: -- Sounds like a good plan. Thanks! > Killing a container that is

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

[ https://issues.apache.org/jira/browse/YARN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083034#comment-15083034 ] Junping Du commented on YARN-3697: -- Thanks [~zxu]! > FairScheduler: ContinuousSchedulingThread can fail

[jira] [Updated] (YARN-4537) Pull out priority comparison from fifocomparator and use compound comparator for FifoOrdering policy

[ https://issues.apache.org/jira/browse/YARN-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4537: Attachment: 0003-YARN-4537.patch Updating the patch fixing comments..Kindly review the patch

[jira] [Commented] (YARN-4546) ResourceManager crash due to scheduling opportunity overflow

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

[jira] [Updated] (YARN-4544) All the log messages about rolling monitoring interval are shown with the WARN level

[ https://issues.apache.org/jira/browse/YARN-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takashi Ohnishi updated YARN-4544: -- Description: About yarn.nodemanager.log-aggregation.roll-monitoring-interval-seconds, there are

  1   2   >