[jira] [Commented] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175180#comment-15175180 ] Sidharta Seethana commented on YARN-4744: - /cc [~vvasudev] It looks like this is an artifact of

[jira] [Commented] (YARN-4750) App metrics may not be correct when an app is recovered

[ https://issues.apache.org/jira/browse/YARN-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175105#comment-15175105 ] Srikanth Sampath commented on YARN-4750: Agree [~jianhe]that it would be expensive to do update

[jira] [Updated] (YARN-4753) Use doxia macro to generate in-page TOC of YARN site documentation

[ https://issues.apache.org/jira/browse/YARN-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated YARN-4753: --- Description: Since maven-site-plugin 3.5 was released, we can use toc macro in Markdown.

[jira] [Created] (YARN-4753) Use doxia macro to generate in-page TOC of YARN site documentation

Masatake Iwasaki created YARN-4753: -- Summary: Use doxia macro to generate in-page TOC of YARN site documentation Key: YARN-4753 URL: https://issues.apache.org/jira/browse/YARN-4753 Project: Hadoop

[jira] [Commented] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

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

[jira] [Commented] (YARN-4700) ATS storage has one extra record each time the RM got restarted

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

[jira] [Commented] (YARN-4478) [Umbrella] : Track all the Test failures in YARN

[ https://issues.apache.org/jira/browse/YARN-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175002#comment-15175002 ] Rohith Sharma K S commented on YARN-4478: - bq. Also, in 20+ years of Unix system administration, I

[jira] [Commented] (YARN-4478) [Umbrella] : Track all the Test failures in YARN

[ https://issues.apache.org/jira/browse/YARN-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174995#comment-15174995 ] Allen Wittenauer commented on YARN-4478: You realize that RFC is talking about DNS and not

[jira] [Commented] (YARN-4478) [Umbrella] : Track all the Test failures in YARN

[ https://issues.apache.org/jira/browse/YARN-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174968#comment-15174968 ] Rohith Sharma K S commented on YARN-4478: - In analysis of HADOOP-12687, test failures are not

[jira] [Updated] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

[ https://issues.apache.org/jira/browse/YARN-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4712: Attachment: YARN-4712-YARN-2928.v1.002.patch Hi [~varun_saxena], bq. I was incorrectly

[jira] [Commented] (YARN-4478) [Umbrella] : Track all the Test failures in YARN

[ https://issues.apache.org/jira/browse/YARN-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174888#comment-15174888 ] Allen Wittenauer commented on YARN-4478: * There are plenty of examples where the Jenkins network

[jira] [Commented] (YARN-4478) [Umbrella] : Track all the Test failures in YARN

[ https://issues.apache.org/jira/browse/YARN-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174874#comment-15174874 ] Rohith Sharma K S commented on YARN-4478: - Consistently few test cases are failing because of

[jira] [Commented] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.

[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174870#comment-15174870 ] wanglei-it commented on YARN-1506: -- Thanks for your reply. > Replace set resource change on

[jira] [Commented] (YARN-4133) Containers to be preempted leak in FairScheduler preemption logic.

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

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

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

[jira] [Commented] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

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

[jira] [Commented] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174833#comment-15174833 ] Rohith Sharma K S commented on YARN-4002: - All the method in HostsFileReader are synchronized. And

[jira] [Updated] (YARN-3903) Disable preemption at Queue level for Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3903: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-4752 > Disable preemption at

[jira] [Updated] (YARN-4661) Per-queue preemption policy in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4661: --- Issue Type: Sub-task (was: Wish) Parent: YARN-4752 > Per-queue preemption policy in

[jira] [Updated] (YARN-3054) Preempt policy in FairScheduler may cause mapreduce job never finish

[ https://issues.apache.org/jira/browse/YARN-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3054: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > Preempt policy in FairScheduler

[jira] [Updated] (YARN-3414) FairScheduler's preemption may cause livelock

[ https://issues.apache.org/jira/browse/YARN-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3414: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > FairScheduler's preemption may

[jira] [Updated] (YARN-3121) FairScheduler preemption metrics

[ https://issues.apache.org/jira/browse/YARN-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3121: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-4752 > FairScheduler preemption

[jira] [Updated] (YARN-1961) Fair scheduler preemption doesn't work for non-leaf queues

[ https://issues.apache.org/jira/browse/YARN-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1961: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > Fair scheduler preemption doesn't

[jira] [Updated] (YARN-4133) Containers to be preempted leak in FairScheduler preemption logic.

[ https://issues.apache.org/jira/browse/YARN-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4133: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > Containers to be preempted leak

[jira] [Updated] (YARN-3902) Fair scheduler preempts ApplicationMaster

[ https://issues.apache.org/jira/browse/YARN-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3902: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > Fair scheduler preempts

[jira] [Updated] (YARN-4134) FairScheduler preemption stops at queue level that all child queues are not over their fairshare

[ https://issues.apache.org/jira/browse/YARN-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4134: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > FairScheduler preemption stops at

[jira] [Updated] (YARN-4120) FSAppAttempt.getResourceUsage() should not take preemptedResource into account

[ https://issues.apache.org/jira/browse/YARN-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4120: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > FSAppAttempt.getResourceUsage()

[jira] [Updated] (YARN-2154) FairScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2154: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-4752 > FairScheduler: Improve

[jira] [Updated] (YARN-4333) Fair scheduler should support preemption within queue

[ https://issues.apache.org/jira/browse/YARN-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4333: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-4752 > Fair scheduler should

[jira] [Updated] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3405: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > FairScheduler's preemption cannot

[jira] [Created] (YARN-4752) [Umbrella] FairScheduler: Improve preemption

Karthik Kambatla created YARN-4752: -- Summary: [Umbrella] FairScheduler: Improve preemption Key: YARN-4752 URL: https://issues.apache.org/jira/browse/YARN-4752 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-3997) An Application requesting multiple core containers can't preempt running application made of single core containers

[ https://issues.apache.org/jira/browse/YARN-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3997: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4752 > An Application requesting

[jira] [Commented] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174795#comment-15174795 ] Hong Zhiguo commented on YARN-4002: --- Hi, [~rohithsharma], thanks for the refinement. But why don't take

[jira] [Commented] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174776#comment-15174776 ] Rohith Sharma K S commented on YARN-4002: - [~leftnoteasy] would you like to have look at patch? If

[jira] [Updated] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4002: Target Version/s: 2.8.0 > make ResourceTrackerService.nodeHeartbeat more concurrent >

[jira] [Commented] (YARN-1040) De-link container life cycle from the process and add ability to execute multiple processes in the same long-lived container

[ https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174775#comment-15174775 ] Vinod Kumar Vavilapalli commented on YARN-1040: --- bq. General case: AM launches multiple

[jira] [Updated] (YARN-4700) ATS storage has one extra record each time the RM got restarted

[ https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4700: Attachment: YARN-4700-YARN-2928.v1.002.patch > ATS storage has one extra record each time

[jira] [Updated] (YARN-4700) ATS storage has one extra record each time the RM got restarted

[ https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4700: Attachment: (was: YARN-4700-YARN-2928.v1.002.patch) > ATS storage has one extra record

[jira] [Updated] (YARN-4700) ATS storage has one extra record each time the RM got restarted

[ https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4700: Attachment: YARN-4700-YARN-2928.v1.002.patch Thanks for the comments [~varun_saxena] and

[jira] [Commented] (YARN-4719) Add a helper library to maintain node state and allows common queries

[ https://issues.apache.org/jira/browse/YARN-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174594#comment-15174594 ] Karthik Kambatla commented on YARN-4719: bq. For ClusterNodeTracker#nodes, can we use lock-free

[jira] [Commented] (YARN-4737) Use CSRF Filter in YARN

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

[jira] [Commented] (YARN-4671) There is no need to acquire CS lock when completing a container

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

[jira] [Commented] (YARN-4634) Scheduler UI/Metrics need to consider cases like non-queue label mappings

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

[jira] [Commented] (YARN-4681) ProcfsBasedProcessTree should not calculate private clean pages

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

[jira] [Commented] (YARN-4681) ProcfsBasedProcessTree should not calculate private clean pages

[ https://issues.apache.org/jira/browse/YARN-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174361#comment-15174361 ] Chris Nauroth commented on YARN-4681: - [~je.ik], thank you for updating the patch. I'm +1 for this

[jira] [Updated] (YARN-4681) ProcfsBasedProcessTree should not calculate private clean pages

[ https://issues.apache.org/jira/browse/YARN-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-4681: Assignee: Jan Lukavsky > ProcfsBasedProcessTree should not calculate private clean pages >

[jira] [Commented] (YARN-4751) In 2.7, Labeled queue usage not shown properly in capacity scheduler UI

[ https://issues.apache.org/jira/browse/YARN-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174314#comment-15174314 ] Eric Payne commented on YARN-4751: -- Thanks, [~sunilg] for pointing out YARN-4304. I see that this revision

[jira] [Updated] (YARN-4634) Scheduler UI/Metrics need to consider cases like non-queue label mappings

[ https://issues.apache.org/jira/browse/YARN-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4634: -- Attachment: 0003-YARN-4634.patch Updating patch as per the above mentioned comments. > Scheduler UI/Metrics

[jira] [Commented] (YARN-4634) Scheduler UI/Metrics need to consider cases like non-queue label mappings

[ https://issues.apache.org/jira/browse/YARN-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174165#comment-15174165 ] Wangda Tan commented on YARN-4634: -- [~sunilg], sounds good. > Scheduler UI/Metrics need to consider cases

[jira] [Commented] (YARN-4751) In 2.7, Labeled queue usage not shown properly in capacity scheduler UI

[ https://issues.apache.org/jira/browse/YARN-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174114#comment-15174114 ] Sunil G commented on YARN-4751: --- [~eepayne], Thanks for updating this. YARN-4304 handled issue in few

[jira] [Updated] (YARN-4737) Use CSRF Filter in YARN

[ https://issues.apache.org/jira/browse/YARN-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron updated YARN-4737: - Attachment: YARN-4737.001.patch > Use CSRF Filter in YARN > --- > >

[jira] [Updated] (YARN-4737) Use CSRF Filter in YARN

[ https://issues.apache.org/jira/browse/YARN-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron updated YARN-4737: - Attachment: (was: YARN-4737.patch.001) > Use CSRF Filter in YARN > --- > >

[jira] [Updated] (YARN-4751) In 2.7, Labeled queue usage not shown properly in capacity scheduler UI

[ https://issues.apache.org/jira/browse/YARN-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-4751: - Attachment: 2.7 CS UI No BarGraph.jpg In the attached screenshot, please note that the {{Used Capacity}},

[jira] [Created] (YARN-4751) In 2.7, Labeled queue usage not shown properly in capacity scheduler UI

Eric Payne created YARN-4751: Summary: In 2.7, Labeled queue usage not shown properly in capacity scheduler UI Key: YARN-4751 URL: https://issues.apache.org/jira/browse/YARN-4751 Project: Hadoop YARN

[jira] [Commented] (YARN-4634) Scheduler UI/Metrics need to consider cases like non-queue label mappings

[ https://issues.apache.org/jira/browse/YARN-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174082#comment-15174082 ] Sunil G commented on YARN-4634: --- Thanks [~leftnoteasy] for the comments. I agree that we are considering too

[jira] [Comment Edited] (YARN-4740) container complete msg may lost while AM restart in race condition

[ https://issues.apache.org/jira/browse/YARN-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174027#comment-15174027 ] Jian He edited comment on YARN-4740 at 3/1/16 5:05 PM: --- thanks [~sandflee] ! - could

[jira] [Commented] (YARN-4740) container complete msg may lost while AM restart in race condition

[ https://issues.apache.org/jira/browse/YARN-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174027#comment-15174027 ] Jian He commented on YARN-4740: --- thanks [~sandflee] ! - could you add a check that the completed container is

[jira] [Commented] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.

[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173941#comment-15173941 ] Junping Du commented on YARN-1506: -- Hi Wanglei, Yes. the understanding here is correct. We are not

[jira] [Commented] (YARN-4750) App metrics may not be correct when an app is recovered

[ https://issues.apache.org/jira/browse/YARN-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173917#comment-15173917 ] Jian He commented on YARN-4750: --- this was intentional, as the thought was persisting the metrics periodically

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

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

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-010.patch YARN-4696 patch 010. Checkstyle warnings. The

[jira] [Commented] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

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

[jira] [Commented] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.

[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173716#comment-15173716 ] wanglei-it commented on YARN-1506: -- Hi Junping Du, thanks for your work. I tested this feature in HA. When

[jira] [Commented] (YARN-4746) yarn web services should convert parse failures of appId to 400

[ https://issues.apache.org/jira/browse/YARN-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173560#comment-15173560 ] Steve Loughran commented on YARN-4746: -- Having played with this some more, I think it's probably wise

[jira] [Commented] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173557#comment-15173557 ] Rohith Sharma K S commented on YARN-4002: - Recently we hit this issue in 2K nodes testing. It is

[jira] [Updated] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4002: Attachment: 0001-YARN-4002.patch Updated patch myself with small correction. > make

[jira] [Commented] (YARN-4700) ATS storage has one extra record each time the RM got restarted

[ https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173510#comment-15173510 ] Varun Saxena commented on YARN-4700: Thanks [~Naganarasimha] for the patch. I have nothing further to

[jira] [Commented] (YARN-4734) Merge branch:YARN-3368 to trunk

[ https://issues.apache.org/jira/browse/YARN-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173427#comment-15173427 ] Chris Douglas commented on YARN-4734: - bq. For merge it at the top level, did you mean LICENSE.txt and