[jira] [Commented] (YARN-4316) Make NM's version information useful for upgrade

[ https://issues.apache.org/jira/browse/YARN-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980491#comment-14980491 ] Jason Lowe commented on YARN-4316: -- I don't think this is the right way to approach the problem. Having a

[jira] [Created] (YARN-4316) Make NM's version information useful for upgrade

Jun Gong created YARN-4316: -- Summary: Make NM's version information useful for upgrade Key: YARN-4316 URL: https://issues.apache.org/jira/browse/YARN-4316 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-4288) NodeManager restart should keep retrying to register to RM while connection exception happens during RM failed over.

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

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

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

[jira] [Commented] (YARN-4287) Capacity Scheduler: Rack Locality improvement

[ https://issues.apache.org/jira/browse/YARN-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980503#comment-14980503 ] Nathan Roberts commented on YARN-4287: -- +1 on percentages. My only concern is that node-locality-delay

[jira] [Created] (YARN-4317) Test failure: TestResourceTrackerService

Tsuyoshi Ozawa created YARN-4317: Summary: Test failure: TestResourceTrackerService Key: YARN-4317 URL: https://issues.apache.org/jira/browse/YARN-4317 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4316) Make NM's version information useful for upgrade

[ https://issues.apache.org/jira/browse/YARN-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980683#comment-14980683 ] Jun Gong commented on YARN-4316: [~jlowe] Thanks very much for the info. It is very reasonable and

[jira] [Created] (YARN-4318) Test failure: TestAMAuthorization

Tsuyoshi Ozawa created YARN-4318: Summary: Test failure: TestAMAuthorization Key: YARN-4318 URL: https://issues.apache.org/jira/browse/YARN-4318 Project: Hadoop YARN Issue Type: Bug

[jira] [Resolved] (YARN-4316) Make NM's version information useful for upgrade

[ https://issues.apache.org/jira/browse/YARN-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong resolved YARN-4316. Resolution: Implemented > Make NM's version information useful for upgrade >

[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=14980704#comment-14980704 ] Steve Loughran commented on YARN-4309: -- I mean all the environment variables of the container > Add

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980875#comment-14980875 ] Li Lu commented on YARN-4313: - Latest change LGTM. Could any committers please review this change? Thanks! >

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980915#comment-14980915 ] Xuan Gong commented on YARN-4313: - +1 lgtm. Will commit the patch after Jenkins says OK > Race condition

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980727#comment-14980727 ] Li Lu commented on YARN-4313: - Well wait, quick question---why do we need to initialize a customized job

[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=14980749#comment-14980749 ] Hudson commented on YARN-2902: -- FAILURE: Integrated in Hadoop-trunk-Commit #8724 (See

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980720#comment-14980720 ] Li Lu commented on YARN-4313: - Oh I overlooked that. Yes in this case we can use an atomic boolean. +1 for the

[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=14980888#comment-14980888 ] Hudson commented on YARN-2902: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #601 (See

[jira] [Commented] (YARN-4287) Capacity Scheduler: Rack Locality improvement

[ https://issues.apache.org/jira/browse/YARN-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980886#comment-14980886 ] MENG DING commented on YARN-4287: - Looking at this issue, I have to admit that I had been frustrated with

[jira] [Commented] (YARN-4287) Capacity Scheduler: Rack Locality improvement

[ https://issues.apache.org/jira/browse/YARN-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980816#comment-14980816 ] Wangda Tan commented on YARN-4287: -- I think maybe it's better not deprecate original option, we can

[jira] [Updated] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4313: -- Attachment: YARN-4313.2.patch thanks Li for reviewing , updated the patch accordingly. > Race condition in

[jira] [Commented] (YARN-4315) NaN in Queue percentage for cluster apps page

[ https://issues.apache.org/jira/browse/YARN-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981023#comment-14981023 ] Varun Vasudev commented on YARN-4315: - [~bibinchundatt] - is this temporary, while all the NMs are

[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=14981070#comment-14981070 ] Hudson commented on YARN-2902: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #613 (See

[jira] [Commented] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

[ https://issues.apache.org/jira/browse/YARN-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981133#comment-14981133 ] Tomas F. Pena commented on YARN-4319: - That is supposed to be. But when I put in the include list the

[jira] [Commented] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

[ https://issues.apache.org/jira/browse/YARN-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981091#comment-14981091 ] Jason Lowe commented on YARN-4319: -- If the include list is provided it specifies the list of nodes that

[jira] [Updated] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

[ https://issues.apache.org/jira/browse/YARN-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas F. Pena updated YARN-4319: Environment: Hadoop 2.7.1 Amazon Linux AMI 2015.09 (HVM) java version "1.7.0_85" OpenJDK Runtime

[jira] [Commented] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

[ https://issues.apache.org/jira/browse/YARN-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981149#comment-14981149 ] Jason Lowe commented on YARN-4319: -- Ah, it wasn't clear to me from the log above that the file had the

[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=14981164#comment-14981164 ] Varun Saxena commented on YARN-2902: Thanks [~jlowe] for the review and commit. > Killing a container

[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=14981001#comment-14981001 ] Hudson commented on YARN-2902: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2543 (See

[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=14981055#comment-14981055 ] Hudson commented on YARN-2902: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1336 (See

[jira] [Created] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

Tomas F. Pena created YARN-4319: --- Summary: Nodemanagers are decommissioned when the the list of included hosts is not empty Key: YARN-4319 URL: https://issues.apache.org/jira/browse/YARN-4319 Project:

[jira] [Resolved] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

[ https://issues.apache.org/jira/browse/YARN-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas F. Pena resolved YARN-4319. - Resolution: Fixed > Nodemanagers are decommissioned when the the list of included hosts is not >

[jira] [Updated] (YARN-4132) Nodemanagers should try harder to connect to the RM

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4132: --- Attachment: YARN-4132.3.patch Thanks [~djp] for review and proposal! have updated .3 patch which let

[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=14981233#comment-14981233 ] Hudson commented on YARN-2902: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2489 (See

[jira] [Resolved] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

[ https://issues.apache.org/jira/browse/YARN-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-4319. -- Resolution: Invalid > Nodemanagers are decommissioned when the the list of included hosts is not >

[jira] [Reopened] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

[ https://issues.apache.org/jira/browse/YARN-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reopened YARN-4319: -- Reopening to fix resolution type. Fixed is normally reserved for JIRAs that have corresponding code

[jira] [Commented] (YARN-4287) Capacity Scheduler: Rack Locality improvement

[ https://issues.apache.org/jira/browse/YARN-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981181#comment-14981181 ] Wangda Tan commented on YARN-4287: -- I'm fine with either direction, but for the 4287-minimal.patch, I

[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=14981177#comment-14981177 ] Hudson commented on YARN-2902: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #551 (See

[jira] [Commented] (YARN-4319) Nodemanagers are decommissioned when the the list of included hosts is not empty

[ https://issues.apache.org/jira/browse/YARN-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981202#comment-14981202 ] Tomas F. Pena commented on YARN-4319: - Thank you! Using FQDM is working. > Nodemanagers are

[jira] [Commented] (YARN-4287) Capacity Scheduler: Rack Locality improvement

[ https://issues.apache.org/jira/browse/YARN-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981232#comment-14981232 ] MENG DING commented on YARN-4287: - Agreed. > Capacity Scheduler: Rack Locality improvement >

[jira] [Updated] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

[ https://issues.apache.org/jira/browse/YARN-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4310: -- Fix Version/s: 2.8.0 > FairScheduler: Log skipping reservation messages at DEBUG level >

[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=14981381#comment-14981381 ] Li Lu commented on YARN-4265: - We need to use the finalized APIs in YARN-4234 to build the reading code

[jira] [Created] (YARN-4320) TestJobHistoryEventHandler fails on trunk as MiniYarnCluster no longer binds to default port 8188

Varun Saxena created YARN-4320: -- Summary: TestJobHistoryEventHandler fails on trunk as MiniYarnCluster no longer binds to default port 8188 Key: YARN-4320 URL: https://issues.apache.org/jira/browse/YARN-4320

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

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

[jira] [Commented] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

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

[jira] [Commented] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

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

[jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token

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

[jira] [Commented] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

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

[jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token

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

[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.poc_001.patch This is a proof-of-concept patch for the proposed improvement. This patch

[jira] [Updated] (YARN-4320) TestJobHistoryEventHandler fails on trunk as MiniYarnCluster no longer binds to default port 8188

[ https://issues.apache.org/jira/browse/YARN-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4320: --- Attachment: YARN-4320.01.patch > TestJobHistoryEventHandler fails on trunk as MiniYarnCluster no

[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=14981505#comment-14981505 ] Li Lu commented on YARN-4265: - Another key addition in this patch, compare to YARN-3942, is a "cache id

[jira] [Commented] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

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

[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=14980729#comment-14980729 ] Jason Lowe commented on YARN-2902: -- +1 latest patch lgtm. Committing this. > Killing a container that 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-trunk.002.patch New patch addressing Jenkins -1s. > New levelDB cache storage for timeline

[jira] [Commented] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

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

[jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token

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

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981647#comment-14981647 ] Xuan Gong commented on YARN-4313: - Thanks, [~jianhe] for the verification. Checking this in > Race

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981651#comment-14981651 ] Xuan Gong commented on YARN-4313: - Committed into trunk/branch-2/branch-2.7. Thanks, Jian ! > Race

[jira] [Commented] (YARN-4127) RM fail with noAuth error if switched from failover mode to non-failover mode

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

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

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

[jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token

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

[jira] [Commented] (YARN-4127) RM fail with noAuth error if switched from failover mode to non-failover mode

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

[jira] [Commented] (YARN-4127) RM fail with noAuth error if switched from failover mode to non-failover mode

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

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

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

[jira] [Commented] (YARN-4132) Nodemanagers should try harder to connect to the RM

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

[jira] [Commented] (YARN-4314) Adding container wait time as a metric at queue level and application level.

[ https://issues.apache.org/jira/browse/YARN-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981613#comment-14981613 ] Karthik Kambatla commented on YARN-4314: I was thinking of filing a JIRA for the same. We would

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981535#comment-14981535 ] Jian He commented on YARN-4313: --- TestMRTimelineEventHandling failed without the patch, other tests pass

[jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token

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

[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=14981540#comment-14981540 ] Li Lu commented on YARN-4265: - This patch relies on YARN-3942.002 and YARN-4234.3 patches. > Provide new

[jira] [Commented] (YARN-4127) RM fail with noAuth error if switched from failover mode to non-failover mode

[ https://issues.apache.org/jira/browse/YARN-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981568#comment-14981568 ] Jian He commented on YARN-4127: --- [~varun_saxena], I committed the patch into trunk and branch-2, however for

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Summary: AM max resource configuration per partition to be displayed/updated correctly in UI and in various

[jira] [Updated] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

[ https://issues.apache.org/jira/browse/YARN-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4130: Summary: Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

[ https://issues.apache.org/jira/browse/YARN-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979938#comment-14979938 ] Rohith Sharma K S commented on YARN-4130: - +1 LGTM > Duplicate declaration of ApplicationId in

[jira] [Commented] (YARN-4312) TestSubmitApplicationWithRMHA fails on branch-2.7 and branch-2.6 as some of the test cases time out

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

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

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

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

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

[jira] [Commented] (YARN-4288) NodeManager restart should keep retrying to register to RM while connection exception happens during RM failed over.

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

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

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

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Description: As we are supporting per-partition level max AM resource percentage configuration, UI and various

[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: -- Summary: AM max resource configuration per partition to be displayed/updated correctly in UI and in various

[jira] [Commented] (YARN-4288) NodeManager restart should keep retrying to register to RM while connection exception happens during RM failed over.

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

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

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

[jira] [Commented] (YARN-4313) Race condition in MiniMRYarnCluster when getting history server address

[ https://issues.apache.org/jira/browse/YARN-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979956#comment-14979956 ] Jian He commented on YARN-4313: --- [~gtCarrera9], thanks for taking a look at this. This variable needs to be

[jira] [Updated] (YARN-4288) NodeManager restart should keep retrying to register to RM while connection exception happens during RM failed over.

[ https://issues.apache.org/jira/browse/YARN-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4288: -- Fix Version/s: 2.8.0 > NodeManager restart should keep retrying to register to RM while connection > exception

[jira] [Updated] (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:all-tabpanel ] Varun Saxena updated YARN-2902: --- Attachment: YARN-2902.11.patch > Killing a container that is localizing can orphan resources in the >

[jira] [Commented] (YARN-4288) NodeManager restart should keep retrying to register to RM while connection exception happens during RM failed over.

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

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

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

[jira] [Created] (YARN-4314) Adding container wait time as a metric at queue level and application level.

Lavkesh Lahngir created YARN-4314: - Summary: Adding container wait time as a metric at queue level and application level. Key: YARN-4314 URL: https://issues.apache.org/jira/browse/YARN-4314 Project:

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

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

[jira] [Commented] (YARN-4288) NodeManager restart should keep retrying to register to RM while connection exception happens during RM failed over.

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

[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=14980225#comment-14980225 ] Steve Loughran commented on YARN-4309: -- +1 for ls, -1 for contents. That can include keytabs.

[jira] [Updated] (YARN-4315) NaN in Queue percentage for cluster apps page

[ https://issues.apache.org/jira/browse/YARN-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4315: --- Attachment: Snap1.jpg > NaN in Queue percentage for cluster apps page >

[jira] [Created] (YARN-4315) NaN in Queue percentage for cluster apps page

Bibin A Chundatt created YARN-4315: -- Summary: NaN in Queue percentage for cluster apps page Key: YARN-4315 URL: https://issues.apache.org/jira/browse/YARN-4315 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-4288) NodeManager restart should keep retrying to register to RM while connection exception happens during RM failed over.

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

[jira] [Commented] (YARN-4130) Duplicate declaration of ApplicationId in RMAppManager#submitApplication method

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

[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=14980163#comment-14980163 ] Hadoop QA commented on YARN-2902: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-4308) ContainersAggregated CPU resource utilization reports negative usage in first few heartbeats

[ https://issues.apache.org/jira/browse/YARN-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980243#comment-14980243 ] Junping Du commented on YARN-4308: -- I think the long discussion was happening in YARN-3304. As most people

[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=14980259#comment-14980259 ] Varun Saxena commented on YARN-2902: Fixed. > Killing a container that is localizing can orphan

[jira] [Comment Edited] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980271#comment-14980271 ] Varun Vasudev edited comment on YARN-4307 at 10/29/15 11:12 AM: No - they

[jira] [Commented] (YARN-4307) Blacklisted nodes for AM container is not getting displayed in the Web UI

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980271#comment-14980271 ] Varun Vasudev commented on YARN-4307: - No - they should be separate. One refers to nodes blacklisted by

[jira] [Commented] (YARN-4308) ContainersAggregated CPU resource utilization reports negative usage in first few heartbeats

[ https://issues.apache.org/jira/browse/YARN-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980275#comment-14980275 ] Sunil G commented on YARN-4308: --- Thanks [~kasha] and [~djp] for clarifying the same. As part of YARN-4292, we

  1   2   >