[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051236#comment-15051236 ] Junping Du commented on YARN-3623: -- bq. "it means the cluster will and should bring up the timeline

[jira] [Commented] (YARN-4434) NodeManager Disk Checker parameter documentation is not correct

[ https://issues.apache.org/jira/browse/YARN-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051363#comment-15051363 ] Junping Du commented on YARN-4434: -- Hi [~ajisakaa], we are moving on to 2.6.3-RC0. Would you hold on any

[jira] [Updated] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4416: Description: While debugging in eclipse came across a scenario where in i had to get to know

[jira] [Created] (YARN-4443) Improve locks of OrderingPolicy

Naganarasimha G R created YARN-4443: --- Summary: Improve locks of OrderingPolicy Key: YARN-4443 URL: https://issues.apache.org/jira/browse/YARN-4443 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-4399) FairScheduler allocated container should resetSchedulingOpportunities count of its priority

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

[jira] [Updated] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in CS

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3946: Attachment: YARN-3946.v1.008.patch Thanks for pointing it out [~wangda], have corrected the

[jira] [Updated] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4416: Attachment: YARN-4416.v2.001.patch Hi [~wangda], as per your earlier comment i have split

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

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

[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=15051498#comment-15051498 ] Sangjin Lee commented on YARN-4356: --- Thanks for the feedback. Now that YARN-3623 has been committed, I'll

[jira] [Commented] (YARN-4422) Generic AHS sometimes doesn't show started, node, or logs on App page

[ https://issues.apache.org/jira/browse/YARN-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051548#comment-15051548 ] Ming Ma commented on YARN-4422: --- Thanks [~eepayne]. > Generic AHS sometimes doesn't show started, node, or

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051459#comment-15051459 ] Xuan Gong commented on YARN-3623: - +1 Checking this in > We should have a config to indicate the Timeline

[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=15051542#comment-15051542 ] Kuhu Shukla commented on YARN-4311: --- [~eepayne], request for comments and review. Thanks a lot. >

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051463#comment-15051463 ] Xuan Gong commented on YARN-3623: - Committed the addendum patch in trunk/branch-2. Thanks, junping. > We

[jira] [Updated] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3623: - Attachment: YARN-3623-addendum.patch Sounds good. I put an addendum patch here. Please check if it make

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051335#comment-15051335 ] Naganarasimha G R commented on YARN-3623: - +1 lgtm > We should have a config to indicate the

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051332#comment-15051332 ] Sunil G commented on YARN-4108: --- Hi [~leftnoteasy] Thank you for sharing the detailed doc and patch. Its a

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051419#comment-15051419 ] Junping Du commented on YARN-3623: -- Yes. That's the flexibility we want here - we probably bring up old

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1856: Attachment: YARN-1856.004.patch {quote} Should add all the configs to yarn-default.xml, saying

[jira] [Updated] (YARN-4358) Improve relationship between SharingPolicy and ReservationAgent

[ https://issues.apache.org/jira/browse/YARN-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4358: -- Attachment: YARN-4358.addendum-2.patch Updated based on [~subru]'s suggestion > Improve relationship

[jira] [Commented] (YARN-3226) UI changes for decommissioning node

[ https://issues.apache.org/jira/browse/YARN-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15050449#comment-15050449 ] Rohith Sharma K S commented on YARN-3226: - Sorry for coming late, looking into UI part of the code.

[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=15050391#comment-15050391 ] Karthik Kambatla commented on YARN-4438: Would very much like for us to use Curator for leader

[jira] [Commented] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

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

[jira] [Updated] (YARN-4414) Nodemanager connection errors are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4414: --- Attachment: YARN-4414.1.patch > Nodemanager connection errors are retried at multiple levels >

[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=15051966#comment-15051966 ] Li Lu commented on YARN-4356: - I can see in the v.6 patch both concerns are addressed. Any other

[jira] [Updated] (YARN-4414) Nodemanager connection errors are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4414: --- Attachment: YARN-4414.1.2.patch > Nodemanager connection errors are retried at multiple levels >

[jira] [Updated] (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:all-tabpanel ] Sangjin Lee updated YARN-4356: -- Attachment: YARN-4356-feature-YARN-2928.006.patch Posted patch v.6. Addressed Junping's comment for

[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=15051956#comment-15051956 ] Li Lu commented on YARN-4224: - I scanned through the patch. The patch itself looks fine, but I would like to

[jira] [Updated] (YARN-3817) [Aggregation] Flow and User level aggregation on Application States table

[ https://issues.apache.org/jira/browse/YARN-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3817: Attachment: YARN-3817-poc-v1-rebase.patch Rebase the POC patch to the feature-YARN-2928 branch. The new patch is

[jira] [Updated] (YARN-4219) New levelDB cache storage for timeline v1.5

[ https://issues.apache.org/jira/browse/YARN-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4219: Attachment: YARN-4219-YARN-4265.003.patch Fixed the synchronization issue on service stop. > New levelDB cache

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15050551#comment-15050551 ] Junping Du commented on YARN-3623: -- Ok. I think I already find the answer from YARN-4234 that ATS 1.5

[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=15050645#comment-15050645 ] Junping Du commented on YARN-4356: -- Thanks [~sjlee0] for updating the patch! bq. This is the java 7

[jira] [Updated] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3623: - Target Version/s: 2.8.0 (was: YARN-2928) > We should have a config to indicate the Timeline Service

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

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

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15050496#comment-15050496 ] Junping Du commented on YARN-3623: -- Oh. Just noticed target version is YARN-2928 but I think ATS 1.5 need

[jira] [Commented] (YARN-2934) Improve handling of container's stderr

[ https://issues.apache.org/jira/browse/YARN-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15050495#comment-15050495 ] Varun Vasudev commented on YARN-2934: - [~Naganarasimha] - one minor comment - can we make the tail size

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

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

[jira] [Commented] (YARN-2934) Improve handling of container's stderr

[ https://issues.apache.org/jira/browse/YARN-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15050887#comment-15050887 ] Naganarasimha G R commented on YARN-2934: - Hi [~vvasudev], Hi as per the

[jira] [Commented] (YARN-1856) cgroups based memory monitoring for containers

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

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15050494#comment-15050494 ] Junping Du commented on YARN-3623: -- +1. Committing. > We should have a config to indicate the Timeline

[jira] [Updated] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4416: Description: While debugging in eclipse came across a scenario where in i had to get to know

[jira] [Updated] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4416: Issue Type: Sub-task (was: Bug) Parent: YARN-3091 > Deadlock due to synchronised

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

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051264#comment-15051264 ] Sangjin Lee commented on YARN-3623: --- That's why I asked whether you were OK with the wording. How about

[jira] [Commented] (YARN-4424) Fix deadlock in RMAppImpl

[ https://issues.apache.org/jira/browse/YARN-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051309#comment-15051309 ] Junping Du commented on YARN-4424: -- Hi [~leftnoteasy] and [~jianhe], Is this blocker for 2.6.3? If so, we

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051377#comment-15051377 ] Li Lu commented on YARN-3623: - I'd like to make sure I understand this change correctly. Specifically, what

[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=15052001#comment-15052001 ] Jian He commented on YARN-4438: --- bq. Otherwise, the clients (and their individual timeouts etc.) could lead

[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=15052022#comment-15052022 ] Vinod Kumar Vavilapalli commented on YARN-4224: --- We should model this around resources (as

[jira] [Commented] (YARN-4399) FairScheduler allocated container should resetSchedulingOpportunities count of its priority

[ https://issues.apache.org/jira/browse/YARN-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052026#comment-15052026 ] Lin Yiqun commented on YARN-4399: - I test the failed unit tests and these error is not related. >

[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=15052038#comment-15052038 ] Li Lu commented on YARN-4224: - And, BTW, under the current resource model of ATS v2, maybe a full path to

[jira] [Commented] (YARN-4350) TestDistributedShell fails

[ https://issues.apache.org/jira/browse/YARN-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051998#comment-15051998 ] Naganarasimha G R commented on YARN-4350: - [~sjlee0] can you cherry pick YARN-2859 into our branch,

[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=15052030#comment-15052030 ] Li Lu commented on YARN-4224: - OK I've got a few references for the discussion. I looked at the WebHDFS REST

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052043#comment-15052043 ] Jun Gong commented on YARN-3998: [~vvasudev] Thanks for the attention and suggestion. We have a patch for

[jira] [Commented] (YARN-4340) Add "list" API to reservation system

[ https://issues.apache.org/jira/browse/YARN-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052096#comment-15052096 ] Subru Krishnan commented on YARN-4340: -- [~seanpo03], I noticed there are couple of minor checkstyle &

[jira] [Commented] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in CS

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051985#comment-15051985 ] Naganarasimha G R commented on YARN-3946: - Hi [~wangda], Java doc, checkstyle and unit test case

[jira] [Updated] (YARN-4440) FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler time

[ https://issues.apache.org/jira/browse/YARN-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated YARN-4440: Attachment: YARN-4440.002.patch Resolve the remained error. > FSAppAttempt#getAllowedLocalityLevelByTime

[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=15052108#comment-15052108 ] Sidharta Seethana commented on YARN-3542: - hi [~vvasudev], thanks for the updated patch. Please see

[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=15052035#comment-15052035 ] Li Lu commented on YARN-4224: - Reformat: OK I've got a few references for the discussion. I looked at the

[jira] [Commented] (YARN-4340) Add "list" API to reservation system

[ https://issues.apache.org/jira/browse/YARN-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052067#comment-15052067 ] Subru Krishnan commented on YARN-4340: -- Thanks for addressing my feedback [~seanpo03]. The latest

[jira] [Updated] (YARN-3226) UI changes for decommissioning node

[ https://issues.apache.org/jira/browse/YARN-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3226: -- Attachment: 0004-YARN-3226.patch Thank You [~rohithsharma] for the comments. Addressing the same in the new

[jira] [Commented] (YARN-4415) Scheduler Web Ui shows max capacity for the queue is 100% but when we submit application doesnt get assigned

[ https://issues.apache.org/jira/browse/YARN-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051245#comment-15051245 ] Naganarasimha G R commented on YARN-4415: - Hi [~wangda], bq. User doesn't need to update

[jira] [Updated] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4416: Description: While debugging in eclipse came across a scenario where in i had to get to know

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051426#comment-15051426 ] Li Lu commented on YARN-3623: - Agree. +1 for the change. > We should have a config to indicate the Timeline

[jira] [Commented] (YARN-4350) TestDistributedShell fails

[ https://issues.apache.org/jira/browse/YARN-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052333#comment-15052333 ] Sangjin Lee commented on YARN-4350: --- I pushed that commit. Let me know if you need anything else. Thanks.

[jira] [Commented] (YARN-4399) FairScheduler allocated container should resetSchedulingOpportunities count of its priority

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

[jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version

[ https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051133#comment-15051133 ] Hudson commented on YARN-3623: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #682 (See

[jira] [Commented] (YARN-4442) create new application operation from the Rest API should be logged in the audit log

[ https://issues.apache.org/jira/browse/YARN-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051136#comment-15051136 ] Varun Vasudev commented on YARN-4442: - Any reason why it should be logged in the REST API but not for

[jira] [Commented] (YARN-4350) TestDistributedShell fails

[ https://issues.apache.org/jira/browse/YARN-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052179#comment-15052179 ] Sangjin Lee commented on YARN-4350: --- You mean commit

[jira] [Commented] (YARN-3432) Cluster metrics have wrong Total Memory when there is reserved memory on CS

[ https://issues.apache.org/jira/browse/YARN-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052251#comment-15052251 ] Akira AJISAKA commented on YARN-3432: - bq. Rethinking this, it's better to change how to calculate

[jira] [Commented] (YARN-4441) Kill application request from the webservice(ui) is showing success even for the finished applications

[ https://issues.apache.org/jira/browse/YARN-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052256#comment-15052256 ] Mohammad Shahid Khan commented on YARN-4441: If an application is already finished, then the

[jira] [Updated] (YARN-4194) Extend Reservation Definition Langauge (RDL) extensions to support node labels

[ https://issues.apache.org/jira/browse/YARN-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Tumanov updated YARN-4194: - Attachment: YARN-4194-v2.patch My patch test returns success: +1 overall __ < Success!

[jira] [Commented] (YARN-4358) Improve relationship between SharingPolicy and ReservationAgent

[ https://issues.apache.org/jira/browse/YARN-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052270#comment-15052270 ] Akira AJISAKA commented on YARN-4358: - +1 pending Jenkins. Thanks Arun, Carlo, and Subru. bq.

Yarn Running Application Logs

Hi, I want to collect running yarn application logs, when I try # yarn logs -applicationId it is giving error "application has not completed logs are only available after an application completes yarn" but I can see the logs through resourcemanager webui Anybody can help me how to collect

[jira] [Reopened] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reopened YARN-3998: - Re-opening - I think this is a useful feature for YARN to support. > Add retry-times to let NM

[jira] [Commented] (YARN-4340) Add "list" API to reservation system

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

[jira] [Commented] (YARN-3876) get_executable() assumes everything is Linux

[ https://issues.apache.org/jira/browse/YARN-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051038#comment-15051038 ] Alan Burlison commented on YARN-3876: - In addition {{get_executable()}} returns a buffer that's never

[jira] [Commented] (YARN-4422) Generic AHS sometimes doesn't show started, node, or logs on App page

[ https://issues.apache.org/jira/browse/YARN-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051061#comment-15051061 ] Eric Payne commented on YARN-4422: -- bq. Thanks! Will this fix address MAPREDUCE-5502 or MAPREDUCE-4428? It

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051024#comment-15051024 ] Varun Vasudev commented on YARN-3998: - [~hex108] - do you wish to work on this? Do you have a patch

[jira] [Created] (YARN-4440) FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler time

Lin Yiqun created YARN-4440: --- Summary: FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler time Key: YARN-4440 URL: https://issues.apache.org/jira/browse/YARN-4440 Project: Hadoop YARN

[jira] [Updated] (YARN-4440) FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler time

[ https://issues.apache.org/jira/browse/YARN-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated YARN-4440: Attachment: YARN-4440.001.patch > FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler

[jira] [Commented] (YARN-4440) FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler time

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

[jira] [Assigned] (YARN-4441) Kill application request from the webservice(ui) is showing success even for the finished applications

[ https://issues.apache.org/jira/browse/YARN-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-4441: - Assignee: Sunil G (was: Mohammad Shahid Khan) > Kill application request from the webservice(ui) is

[jira] [Created] (YARN-4442) create new application operation from the Rest API should be logged in the audit log

Mohammad Shahid Khan created YARN-4442: -- Summary: create new application operation from the Rest API should be logged in the audit log Key: YARN-4442 URL: https://issues.apache.org/jira/browse/YARN-4442

[jira] [Commented] (YARN-4441) Kill application request from the webservice(ui) is showing success even for the finished applications

[ https://issues.apache.org/jira/browse/YARN-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051117#comment-15051117 ] Sunil G commented on YARN-4441: --- Hi [~mohdshahidkhan] This is intentional. If application state is Final

[jira] [Commented] (YARN-3102) Decommisioned Nodes not listed in Web UI

[ https://issues.apache.org/jira/browse/YARN-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051121#comment-15051121 ] Kuhu Shukla commented on YARN-3102: --- Following the discussion from YARN-4402: Given that we consider

[jira] [Created] (YARN-4441) Kill application request from the webservice(ui) is showing success even for the finished applications

Mohammad Shahid Khan created YARN-4441: -- Summary: Kill application request from the webservice(ui) is showing success even for the finished applications Key: YARN-4441 URL:

[jira] [Updated] (YARN-4399) FairScheduler allocated container should resetSchedulingOpportunities count of its priority

[ https://issues.apache.org/jira/browse/YARN-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated YARN-4399: Attachment: YARN-4399.002.patch Resolve the comile error. > FairScheduler allocated container should

[jira] [Updated] (YARN-4441) Kill application request from the webservice(ui) is showing success even for the finished applications

[ https://issues.apache.org/jira/browse/YARN-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4441: -- Assignee: Mohammad Shahid Khan (was: Sunil G) > Kill application request from the webservice(ui) is showing

[jira] [Assigned] (YARN-3876) get_executable() assumes everything is Linux

[ https://issues.apache.org/jira/browse/YARN-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Burlison reassigned YARN-3876: --- Assignee: Alan Burlison > get_executable() assumes everything is Linux >

[jira] [Updated] (YARN-4399) FairScheduler allocated container should resetSchedulingOpportunities count of its priority

[ https://issues.apache.org/jira/browse/YARN-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated YARN-4399: Attachment: YARN-4399.003.patch Resolve the remained compile error > FairScheduler allocated container

[jira] [Commented] (YARN-4100) Add Documentation for Distributed Node Labels feature

[ https://issues.apache.org/jira/browse/YARN-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051180#comment-15051180 ] Naganarasimha G R commented on YARN-4100: - Hi [~dian.fu], [~devaraj.k], [~wangda], &

[jira] [Updated] (YARN-4100) Add Documentation for Distributed and Delegated-Centralized Node Labels feature

[ https://issues.apache.org/jira/browse/YARN-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4100: Summary: Add Documentation for Distributed and Delegated-Centralized Node Labels feature

[jira] [Commented] (YARN-3226) UI changes for decommissioning node

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