[jira] [Updated] (YARN-3367) Replace starting a separate thread for post entity with event loop in TimelineClient

[ https://issues.apache.org/jira/browse/YARN-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3367: Attachment: YARN-3367-feature-YARN-2928.v1.004.patch WIP patch with fixes for test case >

[jira] [Commented] (YARN-3586) RM only get back addresses of Collectors that NM needs to know.

[ https://issues.apache.org/jira/browse/YARN-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068238#comment-15068238 ] Varun Saxena commented on YARN-3586: Will commit it shortly. > RM only get back addresses of

[jira] [Commented] (YARN-4098) Document ApplicationPriority feature

[ https://issues.apache.org/jira/browse/YARN-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068535#comment-15068535 ] Sunil G commented on YARN-4098: --- Hi [~rohithsharma] Thank you for sharing the patch. Some minor nits. CS

[jira] [Updated] (YARN-4062) Add the flush and compaction functionality via coprocessors and scanners for flow run table

[ https://issues.apache.org/jira/browse/YARN-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-4062: - Attachment: YARN-4062-feature-YARN-2928.01.patch Thanks [~sjlee0], renamed the patch now. > Add the

[jira] [Commented] (YARN-4062) Add the flush and compaction functionality via coprocessors and scanners for flow run table

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

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

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

[jira] [Updated] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3480: --- Attachment: YARN-3480.13.patch > Recovery may get very slow with lots of services with lots of app-attempts >

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069045#comment-15069045 ] Jun Gong commented on YARN-3480: Discussed with [~jianhe] offline, we think the

[jira] [Commented] (YARN-4496) Improve HA ResourceManager Failover detection on the client

[ https://issues.apache.org/jira/browse/YARN-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069043#comment-15069043 ] Arun Suresh commented on YARN-4496: --- Had a discussion with [~subru], and we think this would also be

[jira] [Commented] (YARN-4003) ReservationQueue inherit getAMResourceLimit() from LeafQueue, but behavior is not consistent

[ https://issues.apache.org/jira/browse/YARN-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069062#comment-15069062 ] Sunil G commented on YARN-4003: --- Hi [~curino] bq.Assume a reservation queue R1 launches tons of AMs, and now

[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=15068939#comment-15068939 ] Daniel Templeton commented on YARN-4311: In the constructor, you check if the inactive nodes list

[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=15068940#comment-15068940 ] Daniel Templeton commented on YARN-4311: Oh, and I'm a big proponent of using blank lines to make

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068934#comment-15068934 ] Jian He commented on YARN-4138: --- looks like some files are created at a wrong direcotry "hadoop-yarn/"

[jira] [Commented] (YARN-4224) Change the ATSv2 reader side 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=15068950#comment-15068950 ] Li Lu commented on YARN-4224: - Thanks Varun. Some of my comments: bq. You mean just have one endpoint and based

[jira] [Commented] (YARN-4459) container-executor might kill process wrongly

[ https://issues.apache.org/jira/browse/YARN-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068996#comment-15068996 ] Jun Gong commented on YARN-4459: Thanks [~Naganarasimha] for the info. Yes, it seems same problem. I think

[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: 0007-YARN-4304.patch Hi [~leftnoteasy] Thank you for sharing the comments. Uploading a new patch

[jira] [Commented] (YARN-4195) Support of node-labels in the ReservationSystem "Plan"

[ https://issues.apache.org/jira/browse/YARN-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069080#comment-15069080 ] Wangda Tan commented on YARN-4195: -- Hi [~curino], Thanks for responses, the "unified" label is a great

[jira] [Commented] (YARN-4352) Timeout for tests in TestYarnClient, TestAMRMClient and TestNMClient

[ https://issues.apache.org/jira/browse/YARN-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069081#comment-15069081 ] Rohith Sharma K S commented on YARN-4352: - [~sunilg] can you check test failures, I checked logs,

[jira] [Updated] (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:all-tabpanel ] Arun Suresh updated YARN-2885: -- Attachment: YARN-2885-yarn-2877.v4.patch Rebasing patch against latest YARN-2882 and YARN-4335 patches

[jira] [Commented] (YARN-4482) Default values of several config parameters are missing

[ https://issues.apache.org/jira/browse/YARN-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068959#comment-15068959 ] Tianyin Xu commented on YARN-4482: -- I got some time to look into this. Yes... the values changed...

[jira] [Commented] (YARN-4494) Recover completed apps asynchronously

[ https://issues.apache.org/jira/browse/YARN-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069014#comment-15069014 ] Jun Gong commented on YARN-4494: [~sunilg] Yes, I think we all agree with the option "an on-demand fast

[jira] [Created] (YARN-4496) Improve HA ResourceManager Failover detection on the client

Arun Suresh created YARN-4496: - Summary: Improve HA ResourceManager Failover detection on the client Key: YARN-4496 URL: https://issues.apache.org/jira/browse/YARN-4496 Project: Hadoop YARN

[jira] [Commented] (YARN-4352) Timeout for tests in TestYarnClient, TestAMRMClient and TestNMClient

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

[jira] [Commented] (YARN-3367) Replace starting a separate thread for post entity with event loop in TimelineClient

[ https://issues.apache.org/jira/browse/YARN-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068468#comment-15068468 ] Naganarasimha G R commented on YARN-3367: - check style issues some cannot be handled(line lengths >

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

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068490#comment-15068490 ] Sangjin Lee commented on YARN-3816: --- Just to clarify, it appears both aggregated (but not accumulated

[jira] [Commented] (YARN-4352) Timeout for tests in TestYarnClient, TestAMRMClient and TestNMClient

[ https://issues.apache.org/jira/browse/YARN-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068493#comment-15068493 ] Rohith Sharma K S commented on YARN-4352: - Tx Sunil for providing patch. 3rd approach looks fine to

[jira] [Commented] (YARN-4492) Add documentation for queue level preemption which is supported in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068503#comment-15068503 ] Daniel Templeton commented on YARN-4492: +1 (non-binding). Thanks, [~Naganarasimha]! > Add

[jira] [Commented] (YARN-4327) RM can not renew TIMELINE_DELEGATION_TOKEN in secure clusters

[ https://issues.apache.org/jira/browse/YARN-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069121#comment-15069121 ] zhangshilong commented on YARN-4327: yeah，I tried

[jira] [Created] (YARN-4498) Application level running labels/stats to be available to UI/REST/CLI

Bibin A Chundatt created YARN-4498: -- Summary: Application level running labels/stats to be available to UI/REST/CLI Key: YARN-4498 URL: https://issues.apache.org/jira/browse/YARN-4498 Project:

[jira] [Updated] (YARN-4498) Application level node labels stats to be available in UI/REST/CLI

[ https://issues.apache.org/jira/browse/YARN-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4498: --- Summary: Application level node labels stats to be available in UI/REST/CLI (was: Application

[jira] [Commented] (YARN-4224) Change the ATSv2 reader side 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=15069172#comment-15069172 ] Varun Saxena commented on YARN-4224: bq. So the UID in /entities/{entitytype}/{uid}/ is actually app

[jira] [Commented] (YARN-4224) Change the ATSv2 reader side 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=15069190#comment-15069190 ] Varun Saxena commented on YARN-4224: bq. It's about locating resources in the system. /flows will be a

[jira] [Commented] (YARN-4492) Add documentation for queue level preemption which is supported in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069093#comment-15069093 ] Naganarasimha G R commented on YARN-4492: - Thanks [~templedf], for the review Hope [~jlowe] /

[jira] [Commented] (YARN-4109) Exception on RM scheduler page loading with labels

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

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

[jira] [Assigned] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-3215: --- Assignee: Naganarasimha G R (was: Wangda Tan) > Respect labels in CapacityScheduler

[jira] [Updated] (YARN-4497) RM might fail to restart when recovering apps whose attempts are missing

[ https://issues.apache.org/jira/browse/YARN-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-4497: --- Description: Find following problem when discussing in YARN-3480. If RM fails to store some attempts in

[jira] [Created] (YARN-4497) RM might fail to restart when recovering apps whose attempts are missing

Jun Gong created YARN-4497: -- Summary: RM might fail to restart when recovering apps whose attempts are missing Key: YARN-4497 URL: https://issues.apache.org/jira/browse/YARN-4497 Project: Hadoop YARN

[jira] [Commented] (YARN-3870) Providing raw container request information for fine scheduling

[ https://issues.apache.org/jira/browse/YARN-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069208#comment-15069208 ] Arun Suresh commented on YARN-3870: --- Thank you for starting this discussion [~grey] Correct me if I am

[jira] [Commented] (YARN-2882) Add ExecutionType to denote if a container execution is GUARANTEED or OPPORTUNISTIC

[ https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069226#comment-15069226 ] Arun Suresh commented on YARN-2882: --- bq. However, I think we still need a flag in ResourceRequest to

[jira] [Commented] (YARN-4373) Jobs can be temporarily forgotten during recovery

[ https://issues.apache.org/jira/browse/YARN-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068335#comment-15068335 ] Daniel Templeton commented on YARN-4373: I'm also incredulous. I'm still working to reproduce the

[jira] [Commented] (YARN-4494) Recover completed apps asynchronously

[ https://issues.apache.org/jira/browse/YARN-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068377#comment-15068377 ] Sunil G commented on YARN-4494: --- Thanks [~hex108] for filing this. It will speed up the recovery. For the

[jira] [Commented] (YARN-4234) New put APIs in TimelineClient for ats v1.5

[ https://issues.apache.org/jira/browse/YARN-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067853#comment-15067853 ] Junping Du commented on YARN-4234: -- Thanks [~xgong] for updating the patch. +1 on latest patch. I will

[jira] [Commented] (YARN-4466) ResourceManager should tolerate unexpected exceptions to happen in non-critical subsystem/services like SystemMetricsPublisher

[ https://issues.apache.org/jira/browse/YARN-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067852#comment-15067852 ] Naganarasimha G R commented on YARN-4466: - Hi [~djp] Was looking into the exception trace which

[jira] [Commented] (YARN-4172) Extend DominantResourceCalculator to account for all resources

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

[jira] [Commented] (YARN-4224) Change the ATSv2 reader side 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=15067939#comment-15067939 ] Varun Saxena commented on YARN-4224: Formatting issue for one of the comments. Writing it here again.

[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=15067730#comment-15067730 ] Rohith Sharma K S commented on YARN-3692: - Tx [~rjainqb]for sharing your use case. It was quite

[jira] [Updated] (YARN-4109) Exception on RM scheduler page loading with labels

[ https://issues.apache.org/jira/browse/YARN-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4109: Priority: Minor (was: Major) > Exception on RM scheduler page loading with labels >

[jira] [Commented] (YARN-4224) Change the ATSv2 reader side 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=15067935#comment-15067935 ] Varun Saxena commented on YARN-4224: [~gtCarrera9], {quote} 1. I understand we would like to have

[jira] [Commented] (YARN-4172) Extend DominantResourceCalculator to account for all resources

[ https://issues.apache.org/jira/browse/YARN-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067867#comment-15067867 ] Varun Vasudev commented on YARN-4172: - Looks like we need to rebase the YARN-3926 branch.

[jira] [Resolved] (YARN-4027) ApplicationHistory web UI(timeline V1) apps column rendering is incorrect

[ https://issues.apache.org/jira/browse/YARN-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-4027. - Resolution: Duplicate Closing as duplicate > ApplicationHistory web UI(timeline V1) apps

[jira] [Commented] (YARN-4109) Exception on RM scheduler page loading with labels

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

[jira] [Commented] (YARN-4109) Exception on RM scheduler page loading with labels

[ https://issues.apache.org/jira/browse/YARN-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067782#comment-15067782 ] Rohith Sharma K S commented on YARN-4109: - +1 lgtm, pending jenkins > Exception on RM scheduler

[jira] [Commented] (YARN-2599) Standby RM should also expose some jmx and metrics

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067814#comment-15067814 ] Rohith Sharma K S commented on YARN-2599: - Apologies for missing the sequence of comments:-( I will

[jira] [Updated] (YARN-4324) AM hang more than 10 min was kill by RM

[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4324: --- Attachment: (was: am105361log.tar.gz) > AM hang more than 10 min was kill by RM >

[jira] [Updated] (YARN-4172) Extend DominantResourceCalculator to account for all resources

[ https://issues.apache.org/jira/browse/YARN-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4172: Attachment: YARN-4172-YARN-3926.002.patch bq. 1) Who will update DRC.resourceNames, I found

[jira] [Updated] (YARN-4324) AM hang more than 10 min was kill by RM

[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4324: --- Attachment: am105361log.tar.gz I update other AM Log > AM hang more than 10 min was kill by RM >

[jira] [Commented] (YARN-3458) CPU resource monitoring in Windows

[ https://issues.apache.org/jira/browse/YARN-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067745#comment-15067745 ] Inigo Goiri commented on YARN-3458: --- [~cnauroth], thank you very much for the review! > CPU resource

[jira] [Commented] (YARN-3863) Enhance filters in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068029#comment-15068029 ] Varun Saxena commented on YARN-3863: Will update patch to fix checkstyle, whitespace and javac issues

[jira] [Commented] (YARN-4459) container-executor might kill process wrongly

[ https://issues.apache.org/jira/browse/YARN-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067999#comment-15067999 ] Naganarasimha G R commented on YARN-4459: - Is this issue similar to YARN-3678 ? >

[jira] [Commented] (YARN-3995) Some of the NM events are not getting published due race condition when AM container finishes in NM

[ https://issues.apache.org/jira/browse/YARN-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068068#comment-15068068 ] Naganarasimha G R commented on YARN-3995: - Hi [~sjlee0], As per the discussion we had in the status

[jira] [Commented] (YARN-4109) Exception on RM scheduler page loading with labels

[ https://issues.apache.org/jira/browse/YARN-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068001#comment-15068001 ] Mohammad Shahid Khan commented on YARN-4109: UT Failure are unrelated to current patch. UT

[jira] [Commented] (YARN-4470) Application Master in-place upgrade

[ https://issues.apache.org/jira/browse/YARN-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068034#comment-15068034 ] Steve Loughran commented on YARN-4470: -- talk to [~gsaha] about the work. Thinking more about it, one

[jira] [Updated] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3542: Attachment: YARN-3542.007.patch Uploaded a new patch that'll apply on trunk. Just a note on the

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068394#comment-15068394 ] Jun Gong commented on YARN-3480: Attach a new patch, move remove attempts logic to RMStateStore, then it

[jira] [Updated] (YARN-4352) Timeout for tests in TestYarnClient, TestAMRMClient and TestNMClient

[ https://issues.apache.org/jira/browse/YARN-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4352: -- Attachment: 0001-YARN-4352.patch Attaching a simpler patch to lookup when multiple loopback address is present

[jira] [Commented] (YARN-3586) RM only get back addresses of Collectors that NM needs to know.

[ https://issues.apache.org/jira/browse/YARN-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068316#comment-15068316 ] Junping Du commented on YARN-3586: -- Thanks all for help in review! > RM only get back addresses of

[jira] [Commented] (YARN-3367) Replace starting a separate thread for post entity with event loop in TimelineClient

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

[jira] [Updated] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3480: --- Attachment: YARN-3480.12.patch > Recovery may get very slow with lots of services with lots of app-attempts >

[jira] [Commented] (YARN-3586) RM only get back addresses of Collectors that NM needs to know.

[ https://issues.apache.org/jira/browse/YARN-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068187#comment-15068187 ] Naganarasimha G R commented on YARN-3586: - +1, latest patch LGTM > RM only get back addresses of

[jira] [Commented] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

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

[jira] [Updated] (YARN-4352) Timeout for tests in TestYarnClient, TestAMRMClient and TestNMClient

[ https://issues.apache.org/jira/browse/YARN-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4352: - Labels: security (was: ) > Timeout for tests in TestYarnClient, TestAMRMClient and TestNMClient >

[jira] [Commented] (YARN-3223) Resource update during NM graceful decommission

[ https://issues.apache.org/jira/browse/YARN-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068420#comment-15068420 ] Junping Du commented on YARN-3223: -- Hi [~brookz], thanks for updating the patch. The current approach

[jira] [Commented] (YARN-4062) Add the flush and compaction functionality via coprocessors and scanners for flow run table

[ https://issues.apache.org/jira/browse/YARN-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068450#comment-15068450 ] Sangjin Lee commented on YARN-4062: --- You'll need to use a name like

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

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

[jira] [Commented] (YARN-4062) Add the flush and compaction functionality via coprocessors and scanners for flow run table

[ https://issues.apache.org/jira/browse/YARN-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069174#comment-15069174 ] Vrushali C commented on YARN-4062: -- I will fix the findbug warning and take a look at the whitespace

[jira] [Commented] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069175#comment-15069175 ] Naganarasimha G R commented on YARN-3215: - Hi [~wangda], As i was discussing with you offline wrt

[jira] [Commented] (YARN-4438) Implement RM leader election with curator

[ https://issues.apache.org/jira/browse/YARN-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069202#comment-15069202 ] Karthik Kambatla commented on YARN-4438: bq. And because ZKRMStateStore is currently in active

[jira] [Updated] (YARN-4397) if this addAll() function`s params is fault? @NodeListManager#getUnusableNodes()

[ https://issues.apache.org/jira/browse/YARN-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-4397: -- Fix Version/s: (was: 2.8.0) > if this addAll() function`s params is fault?

[jira] [Updated] (YARN-4499) Bad config values of "scheduler.maximum-allocation-vcores"

[ https://issues.apache.org/jira/browse/YARN-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tianyin Xu updated YARN-4499: - Description: Currently, the default value of {{yarn.scheduler.maximum-allocation-vcores}} is {{4}},

[jira] [Created] (YARN-4499) Bad config values of "scheduler.maximum-allocation-vcores"

Tianyin Xu created YARN-4499: Summary: Bad config values of "scheduler.maximum-allocation-vcores" Key: YARN-4499 URL: https://issues.apache.org/jira/browse/YARN-4499 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-4499) Bad config values of "scheduler.maximum-allocation-vcores"

[ https://issues.apache.org/jira/browse/YARN-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tianyin Xu updated YARN-4499: - Description: Currently, the default value of {{yarn.scheduler.maximum-allocation-vcores}} is {{4}},

[jira] [Updated] (YARN-4499) Bad config values of "scheduler.maximum-allocation-vcores"

[ https://issues.apache.org/jira/browse/YARN-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tianyin Xu updated YARN-4499: - Description: Currently, the default value of {{yarn.scheduler.maximum-allocation-vcores}} is {{4}},