[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] [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&focusedCommentId=15082641#comment-15082641 ] zhihai xu commented on YARN-3697: - [~djp], yes, I just committed it to branch-2.6. thanks

[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-3697) FairScheduler: ContinuousSchedulingThread can fail to shutdown

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

[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&focusedCommentId=15082790#comment-15082790 ] Hadoop QA commented on YARN-3446: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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-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&focusedCommentId=15082917#comment-15082917 ] Konstantinos Karanasos commented on YARN-4335: -- Thank you for the feedback, [~

[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 [~leftnoteasy]

[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&focusedCommentId=15083018#comment-15083018 ] Rohith Sharma K S commented on YARN-3692: - Thanks [~Naganarasimha Garla] and [~jlow

[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&focusedCommentId=15083029#comment-15083029 ] Junping Du commented on YARN-4542: -- Hi Naga, please feel free to take it up. Thanks! > Cl

[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&focusedCommentId=15083031#comment-15083031 ] Junping Du commented on YARN-2902: -- Sounds like a good plan. Thanks! > Killing a containe

[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&focusedCommentId=15083034#comment-15083034 ] Junping Du commented on YARN-3697: -- Thanks [~zxu]! > FairScheduler: ContinuousSchedulingT

[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] [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 dia

[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&focusedCommentId=15083077#comment-15083077 ] Jason Lowe commented on YARN-3089: -- As I mentioned in my last comment above, this shouldn'

[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&focusedCommentId=15083163#comment-15083163 ] Junping Du commented on YARN-4265: -- Thanks [~gtCarrera9] for reply and updating the patch.

[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 ResourceSharingPolicyForNodeLabelsParti

[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&focusedCommentId=15083167#comment-15083167 ] Naganarasimha G R commented on YARN-4425: - Further i tried to consider your comment

[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&focusedCommentId=15083223#comment-15083223 ] Karthik Kambatla commented on YARN-1011: We would run an opportunistic container on

[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&focusedCommentId=15083223#comment-15083223 ] Karthik Kambatla edited comment on YARN-1011 at 1/5/16 3:28 PM: -

[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&focusedCommentId=15083226#comment-15083226 ] Karthik Kambatla commented on YARN-1011: Since the plan is develop this on a branch

[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 re

[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&focusedCommentId=15083248#comment-15083248 ] Rohith Sharma K S commented on YARN-4479: - updated 0005-YARN-4479 patch , kindly re

[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 Pr

[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 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&focusedCommentId=15083287#comment-15083287 ] Sunil G commented on YARN-4537: --- +1. Looks good. > Pull out priority comparison from fifocom

[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&focusedCommentId=15083283#comment-15083283 ] Sunil G commented on YARN-4479: --- Patch looks good [~rohithsharma]. > Retrospect app-priority

[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 whi

[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&focusedCommentId=15083305#comment-15083305 ] Rohith Sharma K S commented on YARN-4537: - One small update I have done and updated

[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&focusedCommentId=15083309#comment-15083309 ] Sunil G commented on YARN-4537: --- Thanks Rohith. Yes, Its fine. > Pull out priority compariso

[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&focusedCommentId=15083308#comment-15083308 ] Sunil G commented on YARN-4537: --- Thanks Rohith. Yes, Its fine. > Pull out priority compariso

[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 o

[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&focusedCommentId=15083327#comment-15083327 ] Hadoop QA commented on YARN-4544: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083378#comment-15083378 ] Hadoop QA commented on YARN-4537: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083381#comment-15083381 ] Varun Saxena commented on YARN-4224: bq. One quick thing is about TimelineReaderContext

[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&focusedCommentId=15083404#comment-15083404 ] Hadoop QA commented on YARN-4425: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083473#comment-15083473 ] Li Lu commented on YARN-4224: - Thanks Varun. bq. /flows endpoint is for querying active flows

[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&focusedCommentId=15083480#comment-15083480 ] Li Lu commented on YARN-4265: - bq. Can we provide a default one (could be simple) for built-in

[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 corr

[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 configura

[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 at

[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&focusedCommentId=15083538#comment-15083538 ] Wangda Tan commented on YARN-4304: -- Hi Sunil, Thanks for update, I can still see {{"maxAM

[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&focusedCommentId=15083611#comment-15083611 ] Hadoop QA commented on YARN-4479: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083669#comment-15083669 ] Hadoop QA commented on YARN-4537: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083683#comment-15083683 ] Bikas Saha commented on YARN-1011: -- Good points but let me play the devils advocate to get

[jira] [Updated] (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:all-tabpanel ] Ray Chiang updated YARN-4541: - Attachment: YARN-4541.002.patch Submit same patch to launch tests again. > Change log message in Localized

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15083701#comment-15083701 ] Hadoop QA commented on YARN-4311: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083758#comment-15083758 ] Hadoop QA commented on YARN-4304: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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 w

[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 contain

[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 m

[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&focusedCommentId=15083829#comment-15083829 ] Hadoop QA commented on YARN-4541: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083846#comment-15083846 ] Wangda Tan commented on YARN-4538: -- Thanks for reporting this issue, [~bibinchundatt]. Th

[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&focusedCommentId=15083857#comment-15083857 ] Ray Chiang commented on YARN-4541: -- No test needed for variable name fix. > Change log me

[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&focusedCommentId=15083867#comment-15083867 ] Hadoop QA commented on YARN-4161: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083880#comment-15083880 ] Nathan Roberts commented on YARN-1011: -- Very excited about this feature and agree that

[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&focusedCommentId=15083905#comment-15083905 ] Wangda Tan commented on YARN-1011: -- bq. So, hopefully we can make the policy quite configu

[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 Targe

[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&focusedCommentId=15083919#comment-15083919 ] Wangda Tan commented on YARN-4335: -- Thanks [~kkaranasos] for updating the patch bq. Just

[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&focusedCommentId=15083927#comment-15083927 ] Jason Lowe commented on YARN-4546: -- When the overflow occurs the RM crashes with a stacktr

[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&focusedCommentId=15083929#comment-15083929 ] Arun Suresh commented on YARN-4335: --- [~leftnoteasy], YARN-2885 depends on this.. and YARN

[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&focusedCommentId=15083932#comment-15083932 ] Vrushali C commented on YARN-4200: -- Hi [~gtCarrera] The patch looks good but I believe it

[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&focusedCommentId=15083933#comment-15083933 ] Li Lu commented on YARN-4200: - Sure. Will do that soon. Thanks! > Refactor reader classes in

[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&focusedCommentId=15083938#comment-15083938 ] Li Lu commented on YARN-4356: - One quick query w.r.t changes in this JIRA: I just noticed that

[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&focusedCommentId=15083940#comment-15083940 ] Wangda Tan commented on YARN-2885: -- Thanks [~asuresh], I'm fine with this patch's logic t

[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&focusedCommentId=15083941#comment-15083941 ] Vrushali C commented on YARN-4238: -- The hbase cell timestamps may not indicate the actual

[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&focusedCommentId=15083947#comment-15083947 ] Vrushali C commented on YARN-4356: -- Hmm. I am not sure if it is inconsistent. The actual b

[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&focusedCommentId=15083957#comment-15083957 ] Bikas Saha commented on YARN-1011: -- I agree with natural container churn in favor of preem

[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&focusedCommentId=15083959#comment-15083959 ] Li Lu commented on YARN-4356: - Ah OK. But we do need to update the actual code when we introduc

[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&focusedCommentId=15083968#comment-15083968 ] Hadoop QA commented on YARN-4200: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15083974#comment-15083974 ] Jason Lowe commented on YARN-1011: -- bq. Tasks are incorrectly over-allocated. Will never u

[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. > ResourceMa

[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&focusedCommentId=15083994#comment-15083994 ] Vrushali C commented on YARN-4356: -- Yes, if we want the behavior to be different. If the 2

[jira] [Updated] (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:all-tabpanel ] Li Lu updated YARN-4200: Attachment: YARN-4200-feature-YARN-2928.002.patch Quickly refresh the patch to the latest feature branch. Please feel

[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&focusedCommentId=15084002#comment-15084002 ] Li Lu commented on YARN-4356: - I'm fine to live with it for now. However, if anyone happen to h

[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 ] Junping Du updated YARN-4546: - Target Version/s: 2.8.0, 2.7.3, 2.6.4 (was: 2.7.3, 2.6.4) > ResourceManager crash due to scheduling opport

[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&focusedCommentId=15084010#comment-15084010 ] Ray Chiang commented on YARN-4541: -- Ugh, got JIRAs confused. No test needed for changing

[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&focusedCommentId=15084013#comment-15084013 ] Junping Du commented on YARN-4546: -- Nice catch, [~jlowe]! +1 pending on Jenkins result. >

[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&focusedCommentId=15084040#comment-15084040 ] Hadoop QA commented on YARN-4200: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Updated] (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:all-tabpanel ] Li Lu updated YARN-4200: Attachment: YARN-4200-feature-YARN-2928.003.patch Add package-info.java. > Refactor reader classes in storage to ne

[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&focusedCommentId=15084090#comment-15084090 ] Vrushali C commented on YARN-4200: -- Thanks [~gtCarrera9]! Patch looks good. There is an ex

[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&focusedCommentId=15084097#comment-15084097 ] Li Lu commented on YARN-4200: - Oh I believe right now we're not marking all ATS v2 related APIs

[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&focusedCommentId=15084102#comment-15084102 ] Vrushali C commented on YARN-4200: -- I see, thanks! > Refactor reader classes in storage

[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&focusedCommentId=15084104#comment-15084104 ] Hadoop QA commented on YARN-4200: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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&focusedCommentId=15084415#comment-15084415 ] Sangjin Lee commented on YARN-4356: --- The current code *does* consider the case where the

[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&focusedCommentId=15084419#comment-15084419 ] Li Lu commented on YARN-4356: - Oh I missed this part... Thanks for the reminder! > ensure the

[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&focusedCommentId=15084475#comment-15084475 ] Hadoop QA commented on YARN-4546: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[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

[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&focusedCommentId=15084513#comment-15084513 ] Hadoop QA commented on YARN-4265: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-3352) [Event producers] Change distributed shell to use TIMELINE_SERVICE_VERSION

[ https://issues.apache.org/jira/browse/YARN-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084523#comment-15084523 ] Li Lu commented on YARN-3352: - Just remembered this issue when I'm working on YARN-4545. 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&focusedCommentId=15084543#comment-15084543 ] Karthik Kambatla commented on YARN-1011: Dropping a quick note here. (Traveling - w

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

[ https://issues.apache.org/jira/browse/YARN-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4543: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4478 > TestNodeStatusUpdater.testStopReen

[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&focusedCommentId=15084562#comment-15084562 ] Bibin A Chundatt commented on YARN-4539: [~tangshangwen] Can we close this jira?

[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 > init

[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&focusedCommentId=15084575#comment-15084575 ] tangshangwen commented on YARN-4539: OK, Thanks [~bibinchundatt] > CommonNodeLabelsMan

[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&focusedCommentId=15084576#comment-15084576 ] tangshangwen commented on YARN-4539: OK, Thanks [~bibinchundatt] > CommonNodeLabelsMan

[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 fairSch

[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] [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 >

  1   2   >