[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781644#comment-15781644 ] Naganarasimha G R commented on YARN-6029: - Thanks [~djp] & [~wangda], for correcting me, missed to

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781914#comment-15781914 ] Bibin A Chundatt commented on YARN-4465: Thank you [~Ying Zhang] Apologies for missing out the

[jira] [Commented] (YARN-5830) Avoid preempting AM containers

[ https://issues.apache.org/jira/browse/YARN-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781991#comment-15781991 ] Karthik Kambatla commented on YARN-5830: [~yufeigu], thanks for working on this. The patch seems

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782067#comment-15782067 ] Tao Yang commented on YARN-6029: Thanks [~gtCarrera9] for correcting me. There is something wrong in my

[jira] [Commented] (YARN-5709) Cleanup leader election configs and pluggability

[ https://issues.apache.org/jira/browse/YARN-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781465#comment-15781465 ] Daniel Templeton commented on YARN-5709: Hmmm... Looks like

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

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

[jira] [Updated] (YARN-5995) Add RMStateStore metrics to monitor all RMStateStoreEventTypeTransition performance

[ https://issues.apache.org/jira/browse/YARN-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5995: --- Assignee: zhangyubiao > Add RMStateStore metrics to monitor all

[jira] [Commented] (YARN-5257) Fix unreleased resources and null dereferences

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

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781529#comment-15781529 ] Daniel Templeton commented on YARN-4882: Test failures are unrelated, and the lack of tests is

[jira] [Comment Edited] (YARN-5831) Propagate allowPreemptionFrom flag all the way down to the app

[ https://issues.apache.org/jira/browse/YARN-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781573#comment-15781573 ] Yufei Gu edited comment on YARN-5831 at 12/27/16 11:59 PM: --- There is an

[jira] [Commented] (YARN-5831) Propagate allowPreemptionFrom flag all the way down to the app

[ https://issues.apache.org/jira/browse/YARN-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781573#comment-15781573 ] Yufei Gu commented on YARN-5831: There is an assumption from the original code: if the parent queue is

[jira] [Updated] (YARN-5831) Propagate allowPreemptionFrom flag all the way down to the app

[ https://issues.apache.org/jira/browse/YARN-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5831: --- Attachment: YARN-5831.001.patch The logic is covered by

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781593#comment-15781593 ] Wangda Tan commented on YARN-6029: -- Thanks [~Tao Yang] for reporting this issue. [~Naganarasimha],

[jira] [Commented] (YARN-5831) Propagate allowPreemptionFrom flag all the way down to the app

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

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782007#comment-15782007 ] Li Lu commented on YARN-6029: - I'm not a scheduler expert, but "not affecting any data structure" sounds like

[jira] [Commented] (YARN-5709) Cleanup leader election configs and pluggability

[ https://issues.apache.org/jira/browse/YARN-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781487#comment-15781487 ] Jian He commented on YARN-5709: --- Could you re-submit the patch with your change and retry ? > Cleanup leader

[jira] [Comment Edited] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781914#comment-15781914 ] Bibin A Chundatt edited comment on YARN-4465 at 12/28/16 3:20 AM: -- Thank

[jira] [Commented] (YARN-6027) Support fromId for flows/flowrun apps

[ https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781976#comment-15781976 ] Varun Saxena commented on YARN-6027: [~sunilg] bq. However if same flow is ran multiple times in same

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781579#comment-15781579 ] Robert Kanter commented on YARN-4882: - +1 > Change the log level to DEBUG for recovering completed

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781969#comment-15781969 ] Tao Yang commented on YARN-6029: Thanks [~Naganarasimha] [~djp] [~leftnoteasy] for your suggestions.

[jira] [Updated] (YARN-5831) Propagate allowPreemptionFrom flag all the way down to the app

[ https://issues.apache.org/jira/browse/YARN-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5831: --- Attachment: YARN-5831.002.patch Found another unnecessary recursion in function {{updatePreemptionVariables}}.

[jira] [Commented] (YARN-220) NM should limit number of applications who's logs are being aggregated

[ https://issues.apache.org/jira/browse/YARN-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782062#comment-15782062 ] Wilfred Spiegelenburg commented on YARN-220: Should this be marked as fixed now that we have

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782102#comment-15782102 ] Li Lu commented on YARN-6029: - Thanks [~wangda]! bq. But it could cause inconsistency read data, for example,

[jira] [Commented] (YARN-6021) When your allocated minShare of all queue`s added up exceed cluster capacity you can get some queue for 0 fairshare

[ https://issues.apache.org/jira/browse/YARN-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782149#comment-15782149 ] Feng Yuan commented on YARN-6021: - [~kasha] Thanks your detailedness reply.I think your explain solves my

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782147#comment-15782147 ] Ying Zhang commented on YARN-4465: -- Thanks [~leftnoteasy], [~sunilg] and [~bibinchundatt]. I've created

[jira] [Updated] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-6031: - Description: Here is the repro steps: Enable node label, restart RM, configure CS properly, and run some

[jira] [Created] (YARN-6032) scm cleaner task should rm InMemorySCMStore some cachedResources which does not exists in hdfs fs

Zhaofei Meng created YARN-6032: -- Summary: scm cleaner task should rm InMemorySCMStore some cachedResources which does not exists in hdfs fs Key: YARN-6032 URL: https://issues.apache.org/jira/browse/YARN-6032

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782197#comment-15782197 ] Sunil G commented on YARN-6031: --- Thanks [~Ying Zhang] for raising this issue. With the help of

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782098#comment-15782098 ] Wangda Tan commented on YARN-6029: -- Thanks all for comments, [~Tao Yang] / [~gtCarrera9]. Yes removing

[jira] [Comment Edited] (YARN-6024) Capacity Scheduler continuous reservation looking doesn't work when queue's used+reserved = max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782092#comment-15782092 ] Ying Zhang edited comment on YARN-6024 at 12/28/16 5:25 AM: Sorry for the

[jira] [Comment Edited] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782147#comment-15782147 ] Ying Zhang edited comment on YARN-4465 at 12/28/16 6:00 AM: Thanks

[jira] [Commented] (YARN-1492) truly shared cache for jars (jobjar/libjar)

[ https://issues.apache.org/jira/browse/YARN-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782173#comment-15782173 ] Zhaofei Meng commented on YARN-1492: Another problem YARN-6032 > truly shared cache for jars

[jira] [Commented] (YARN-6024) Capacity Scheduler continuous reservation looking doesn't work when queue's used+reserved = max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782185#comment-15782185 ] Ying Zhang commented on YARN-6024: -- Thanks for the details:-) > Capacity Scheduler continuous reservation

[jira] [Commented] (YARN-6024) Capacity Scheduler 'continuous reservation looking' doesn't work when sum of queue's used and reserved resources is equal to max

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

[jira] [Commented] (YARN-6024) Capacity Scheduler continuous reservation looking doesn't work when queue's used+reserved = max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782092#comment-15782092 ] Ying Zhang commented on YARN-6024: -- Sorry for the confusion, [~leftnoteasy] and [~sunilg] :-) Yes, it

[jira] [Comment Edited] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782151#comment-15782151 ] Ying Zhang edited comment on YARN-4465 at 12/28/16 5:58 AM: Yes, you're right.

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782151#comment-15782151 ] Ying Zhang commented on YARN-4465: -- Yes, you're right. Please see the repro steps in YARN-6031. >

[jira] [Commented] (YARN-6001) Improve moveApplicationQueues command line

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

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782324#comment-15782324 ] Naganarasimha G R commented on YARN-6029: - Thanks [~wangda] & [~Tao Yang] bq. I think there maybe

[jira] [Updated] (YARN-5756) Add state-machine implementation for scheduler queues

[ https://issues.apache.org/jira/browse/YARN-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5756: - Fix Version/s: 3.0.0-alpha2 2.9.0 > Add state-machine implementation for scheduler

[jira] [Updated] (YARN-5756) Add state-machine implementation for scheduler queues

[ https://issues.apache.org/jira/browse/YARN-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5756: - Summary: Add state-machine implementation for scheduler queues (was: Add state-machine implementation for

[jira] [Updated] (YARN-5906) Update AppSchedulingInfo to use SchedulingPlacementSet

[ https://issues.apache.org/jira/browse/YARN-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5906: - Attachment: YARN-5906.5.patch Attached ver.5 patch, rebased to latest trunk. > Update AppSchedulingInfo

[jira] [Commented] (YARN-6001) Improve moveApplicationQueues command line

[ https://issues.apache.org/jira/browse/YARN-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782244#comment-15782244 ] Sunil G commented on YARN-6001: --- Thanks [~rohithsharma] for review and commit and thanks [~yufeigu] for

[jira] [Commented] (YARN-6024) Capacity Scheduler continuous reservation looking doesn't work when queue's used+reserved = max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782109#comment-15782109 ] Wangda Tan commented on YARN-6024: -- [~Ying Zhang], Gotcha, thanks for elaborate. Yeah it was a historical

[jira] [Updated] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-6031: - Description: Here is the repro steps: Enable node label, restart RM, configure it properly, and run some

[jira] [Updated] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-6031: - Description: Here is the repro steps: Enable node label, restart RM, configure CS properly, and run some

[jira] [Commented] (YARN-5756) Add state-machine implementation for scheduler queues

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

[jira] [Updated] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-6031: - Priority: Minor (was: Major) > Application recovery failed after disabling node label >

[jira] [Updated] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-6031: - Description: Here is the repro steps: Enable node label, restart RM, configure CS properly, and run some

[jira] [Commented] (YARN-5969) FairShareComparator: Cache value of getResourceUsage for better performance

[ https://issues.apache.org/jira/browse/YARN-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782248#comment-15782248 ] zhangshilong commented on YARN-5969: Thanks [~yufeigu] for advice and review and [~kasha] for commit.

[jira] [Resolved] (YARN-5992) revert the visibility of interface AllocationFileLoaderService.Listener to public for outside usage

[ https://issues.apache.org/jira/browse/YARN-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton resolved YARN-5992. Resolution: Duplicate YARN-6000 already resolves the issue, even though this patch was

[jira] [Commented] (YARN-5658) YARN should have a hook to delete a path from HDFS when an application ends

[ https://issues.apache.org/jira/browse/YARN-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781518#comment-15781518 ] Jian He commented on YARN-5658: --- [~templedf], not just HDFS, allowing deleting a path from ZK is also a

[jira] [Issue Comment Deleted] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4882: Comment: was deleted (was: +1) > Change the log level to DEBUG for recovering completed

[jira] [Commented] (YARN-5831) Propagate allowPreemptionFrom flag all the way down to the app

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

[jira] [Updated] (YARN-5830) Avoid preempting AM containers

[ https://issues.apache.org/jira/browse/YARN-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5830: --- Description: While considering containers for preemption, avoid AM containers unless

[jira] [Commented] (YARN-5756) Add state-machine implementation for scheduler queues

[ https://issues.apache.org/jira/browse/YARN-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782087#comment-15782087 ] Wangda Tan commented on YARN-5756: -- Committed to trunk / branch-2, thanks [~xgong] for working on this and

[jira] [Updated] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-6031: - Description: Here is the repro steps: Enable node label, restart RM, configure it properly, and run some

[jira] [Created] (YARN-6031) Application recovery failed after disabling node label

Ying Zhang created YARN-6031: Summary: Application recovery failed after disabling node label Key: YARN-6031 URL: https://issues.apache.org/jira/browse/YARN-6031 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-6031: - Description: Here is the repro steps: Enable node label, restart RM, configure CS properly, and run some

[jira] [Updated] (YARN-6032) SharedCacheManager cleaner task should rm InMemorySCMStore some cachedResources which does not exists in hdfs fs

[ https://issues.apache.org/jira/browse/YARN-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhaofei Meng updated YARN-6032: --- Summary: SharedCacheManager cleaner task should rm InMemorySCMStore some cachedResources which does

[jira] [Commented] (YARN-6032) scm cleaner task should rm InMemorySCMStore some cachedResources which does not exists in hdfs fs

[ https://issues.apache.org/jira/browse/YARN-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782180#comment-15782180 ] Zhaofei Meng commented on YARN-6032: We should modify use interface in ClientProtocolService to verify

[jira] [Commented] (YARN-6024) Capacity Scheduler continuous reservation looking doesn't work when queue's used+reserved = max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782202#comment-15782202 ] Sunil G commented on YARN-6024: --- +1 Committing. > Capacity Scheduler continuous reservation looking doesn't

[jira] [Commented] (YARN-5906) Update AppSchedulingInfo to use SchedulingPlacementSet

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

[jira] [Commented] (YARN-6001) Improve moveApplicationQueues command line

[ https://issues.apache.org/jira/browse/YARN-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782234#comment-15782234 ] Rohith Sharma K S commented on YARN-6001: - committed to trunk/branch-2.. thanks Sunil for your

[jira] [Updated] (YARN-6024) Capacity Scheduler 'continuous reservation looking' doesn't work when sum of queue's used and reserved resources is equal to max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-6024: -- Summary: Capacity Scheduler 'continuous reservation looking' doesn't work when sum of queue's used and reserved

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15779921#comment-15779921 ] Ying Zhang commented on YARN-4465: -- Hi [~bibinchundatt], [~leftnoteasy], I was trying this fix on my

[jira] [Commented] (YARN-5906) Update AppSchedulingInfo to use SchedulingPlacementSet

[ https://issues.apache.org/jira/browse/YARN-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15779939#comment-15779939 ] Sunil G commented on YARN-5906: --- Generally patch looks fine for me. I will commit tomorrow if there are no

[jira] [Created] (YARN-6028) Add document for container metrics

Weiwei Yang created YARN-6028: - Summary: Add document for container metrics Key: YARN-6028 URL: https://issues.apache.org/jira/browse/YARN-6028 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved co

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang updated YARN-6029: --- Attachment: YARN-6029.001.patch deadlock.jstack > CapacityScheduler deadlock when

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15779965#comment-15779965 ] Sunil G commented on YARN-4465: --- I guess I missed one call more call flow. After recovering an app after RM

[jira] [Updated] (YARN-5931) Document timeout interfaces CLI and REST APIs

[ https://issues.apache.org/jira/browse/YARN-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5931: Attachment: YARN-5931.2.patch updated patch fixing review comments.. > Document timeout

[jira] [Created] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved co

Tao Yang created YARN-6029: -- Summary: CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved container Key: YARN-6029

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15779956#comment-15779956 ] Sunil G commented on YARN-4465: --- After RM restart, it seems apps are still sending resource requests with

[jira] [Commented] (YARN-6024) Capacity Scheduler continuous reservation looking doesn't work when queue's used+reserved = max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15779989#comment-15779989 ] Sunil G commented on YARN-6024: --- +1 for branch-2.7 patch. If others does not have any difference of opinion,

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780019#comment-15780019 ] Ying Zhang commented on YARN-4465: -- Hi [~sunilg], can we just skip the check if it is in recovery, i.e.,

[jira] [Commented] (YARN-5969) FairShareComparator getResourceUsage poor performance

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

[jira] [Updated] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved co

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-6029: Priority: Blocker (was: Major) > CapacityScheduler deadlock when

[jira] [Commented] (YARN-5931) Document timeout interfaces CLI and REST APIs

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

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780135#comment-15780135 ] Sunil G commented on YARN-4465: --- Recovery of the app has to fail as well. But other apps recovery should go

[jira] [Commented] (YARN-2663) Race condintion in shared cache CleanerTask during deletion of resource

[ https://issues.apache.org/jira/browse/YARN-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780152#comment-15780152 ] Zhaofei Meng commented on YARN-2663: Cleaner task rm hdfs resource after rm scm cache.Uploader task

[jira] [Commented] (YARN-5931) Document timeout interfaces CLI and REST APIs

[ https://issues.apache.org/jira/browse/YARN-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780534#comment-15780534 ] Daniel Templeton commented on YARN-5931: A few more comments: * "The possible combination of

[jira] [Commented] (YARN-4423) Cleanup lint warnings in resource mananger

[ https://issues.apache.org/jira/browse/YARN-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780600#comment-15780600 ] Daniel Templeton commented on YARN-4423: That's what happens when it sits for a year without a

[jira] [Commented] (YARN-6020) Resource.add exceed Int boundary,when compute queue demand in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780686#comment-15780686 ] Daniel Templeton commented on YARN-6020: It means that the git apply of your patch didn't succeed.

[jira] [Comment Edited] (YARN-5991) Yarn Distributed Shell does not print throwable t to App Master When failed to start container

[ https://issues.apache.org/jira/browse/YARN-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741409#comment-15741409 ] Daniel Templeton edited comment on YARN-5991 at 12/27/16 5:00 PM: -- The

[jira] [Assigned] (YARN-5991) Yarn Distributed Shell does not print throwable t to App Master When failed to start container

[ https://issues.apache.org/jira/browse/YARN-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton reassigned YARN-5991: -- Assignee: Daniel Templeton > Yarn Distributed Shell does not print throwable t to App

[jira] [Commented] (YARN-6021) When your allocated minShare of all queue`s added up exceed cluster capacity you can get some queue for 0 fairshare

[ https://issues.apache.org/jira/browse/YARN-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780867#comment-15780867 ] Karthik Kambatla commented on YARN-6021: Excuse the long-winded response. I believe minshare was

[jira] [Commented] (YARN-3955) Support for priority ACLs in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780979#comment-15780979 ] Sunil G commented on YARN-3955: --- java doc error is not related. Its a known failure from hadoop-azure project

[jira] [Updated] (YARN-5709) Cleanup leader election configs and pluggability

[ https://issues.apache.org/jira/browse/YARN-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5709: -- Attachment: yarn-5709-branch-2.8.02.patch > Cleanup leader election configs and pluggability >

[jira] [Commented] (YARN-6012) Remove node label (removeFromClusterNodeLabels) document is missing

[ https://issues.apache.org/jira/browse/YARN-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780911#comment-15780911 ] Sunil G commented on YARN-6012: --- Could you please upload a patch. I can help to review. > Remove node label

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780983#comment-15780983 ] Wangda Tan commented on YARN-4465: -- Nice catch, thanks [~Ying Zhang]! I think to solve the problem, we

[jira] [Commented] (YARN-6024) Capacity Scheduler continuous reservation looking doesn't work when queue's used+reserved = max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781013#comment-15781013 ] Wangda Tan commented on YARN-6024: -- Thanks for review, [~sunilg] / [~Ying Zhang]. [~Ying Zhang], I may

[jira] [Commented] (YARN-6025) Few issues in synchronization in CapacityScheduler & AbstractYarnScheduler

[ https://issues.apache.org/jira/browse/YARN-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781024#comment-15781024 ] Wangda Tan commented on YARN-6025: -- bq. But just one more doubt In my mind, methods in AYS is majorly

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781054#comment-15781054 ] Naganarasimha G R commented on YARN-6029: - Thanks for working on the patch [~Tao Yang], Actually

[jira] [Commented] (YARN-5899) A small fix for printing debug info inside function canAssignToThisQueue()

[ https://issues.apache.org/jira/browse/YARN-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780909#comment-15780909 ] Sunil G commented on YARN-5899: --- Thanks for the patch. I ll take a look today. > A small fix for printing

[jira] [Commented] (YARN-5969) FairShareComparator getResourceUsage poor performance

[ https://issues.apache.org/jira/browse/YARN-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780987#comment-15780987 ] Yufei Gu commented on YARN-5969: Thanks [~zsl2007]'s new patch. LGTM. +1(non-binding). Would any committer

[jira] [Commented] (YARN-6025) Few issues in synchronization in CapacityScheduler & AbstractYarnScheduler

[ https://issues.apache.org/jira/browse/YARN-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781057#comment-15781057 ] Naganarasimha G R commented on YARN-6025: - Ok in that case will consider only removing of

[jira] [Updated] (YARN-5969) FairShareComparator: Cache value of getResourceUsage for better performance

[ https://issues.apache.org/jira/browse/YARN-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5969: --- Summary: FairShareComparator: Cache value of getResourceUsage for better performance (was:

[jira] [Updated] (YARN-5529) Create new DiskValidator class with metrics

[ https://issues.apache.org/jira/browse/YARN-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5529: --- Attachment: YARN-5529.003.patch Thanks [~rkanter]'s review. I've uploaded the new patch for all your comments.

[jira] [Commented] (YARN-6022) Revert changes of AbstractResourceRequest

[ https://issues.apache.org/jira/browse/YARN-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781255#comment-15781255 ] Junping Du commented on YARN-6022: -- Remove 2.8 from target version given YARN-5774 was not actually in

[jira] [Updated] (YARN-6022) Revert changes of AbstractResourceRequest

[ https://issues.apache.org/jira/browse/YARN-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6022: - Target Version/s: 2.9.0, 3.0.0-alpha2 (was: 2.8.0, 3.0.0-alpha2) > Revert changes of

  1   2   >