[jira] [Commented] (YARN-4162) Scheduler info in REST, is currently not displaying partition specific queue information similar to UI

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

[jira] [Updated] (YARN-4215) RMNodeLabels Manager Need to verify and replace node labels for the only modified Node Label Mappings in the request

[ https://issues.apache.org/jira/browse/YARN-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4215: Attachment: YARN-4215.v1.002.patch Hi [~wangda] I have updated the test cases please check >

[jira] [Updated] (YARN-4215) RMNodeLabels Manager Need to verify and replace node labels for the only modified Node Label Mappings in the request

[ https://issues.apache.org/jira/browse/YARN-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4215: Attachment: (was: YARN-4215.v1.002.patch) > RMNodeLabels Manager Need to verify and repla

[jira] [Updated] (YARN-4228) FileSystemRMStateStore use IOUtils on fs#close

[ https://issues.apache.org/jira/browse/YARN-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4228: --- Attachment: 0001-YARN-4228.patch Attaching patch for the same > FileSystemRMStateStore use IOU

[jira] [Created] (YARN-4228) FileSystemRMStateStore use IOUtils on fs#close

Bibin A Chundatt created YARN-4228: -- Summary: FileSystemRMStateStore use IOUtils on fs#close Key: YARN-4228 URL: https://issues.apache.org/jira/browse/YARN-4228 Project: Hadoop YARN Issue Ty

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM periodically for distributed nodelabels

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

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944524#comment-14944524 ] Bibin A Chundatt commented on YARN-4216: {quote} That is intentional. Decommission

[jira] [Updated] (YARN-4215) RMNodeLabels Manager Need to verify and replace node labels for the only modified Node Label Mappings in the request

[ https://issues.apache.org/jira/browse/YARN-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4215: Attachment: YARN-4215.v1.002.patch > RMNodeLabels Manager Need to verify and replace node lab

[jira] [Updated] (YARN-4227) FairScheduler: RM quits processing expired container from a removed node

[ https://issues.apache.org/jira/browse/YARN-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-4227: Attachment: YARN-4227.patch > FairScheduler: RM quits processing expired container fr

[jira] [Created] (YARN-4227) FairScheduler: RM quits processing expired container from a removed node

Wilfred Spiegelenburg created YARN-4227: --- Summary: FairScheduler: RM quits processing expired container from a removed node Key: YARN-4227 URL: https://issues.apache.org/jira/browse/YARN-4227 Pr

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944501#comment-14944501 ] Rohith Sharma K S commented on YARN-4209: - patch apply for branch-2.7.2 is failing.

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944498#comment-14944498 ] Rohith Sharma K S commented on YARN-4209: - committing shortly > RMStateStore FENCE

[jira] [Commented] (YARN-4162) Scheduler info in REST, is currently not displaying partition specific queue information similar to UI

[ https://issues.apache.org/jira/browse/YARN-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944484#comment-14944484 ] Naganarasimha G R commented on YARN-4162: - Thanks [~wangda] for the comments, have

[jira] [Updated] (YARN-4162) Scheduler info in REST, is currently not displaying partition specific queue information similar to UI

[ https://issues.apache.org/jira/browse/YARN-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4162: Attachment: YARN-4162.v2.003.patch > Scheduler info in REST, is currently not displaying part

[jira] [Updated] (YARN-4162) Scheduler info in REST, is currently not displaying partition specific queue information similar to UI

[ https://issues.apache.org/jira/browse/YARN-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4162: Attachment: (was: YARN-4162.v2.003.patch) > Scheduler info in REST, is currently not disp

[jira] [Updated] (YARN-4162) Scheduler info in REST, is currently not displaying partition specific queue information similar to UI

[ https://issues.apache.org/jira/browse/YARN-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4162: Attachment: YARN-4162.v2.003.patch > Scheduler info in REST, is currently not displaying part

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM periodically for distributed nodelabels

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

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944416#comment-14944416 ] Sunil G commented on YARN-3216: --- Thank you [~leftnoteasy] for sharing the comments. bq.Pleas

[jira] [Commented] (YARN-4185) Retry interval delay for NM client can be improved from the fixed static retry

[ https://issues.apache.org/jira/browse/YARN-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944384#comment-14944384 ] Neelesh Srinivas Salian commented on YARN-4185: --- [~adhoot], thanks for the cl

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM periodically for distributed nodelabels

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

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

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

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM periodically for distributed nodelabels

[ https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944336#comment-14944336 ] Hudson commented on YARN-4176: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #1222 (See [https://

[jira] [Commented] (YARN-4215) RMNodeLabels Manager Need to verify and replace node labels for the only modified Node Label Mappings in the request

[ https://issues.apache.org/jira/browse/YARN-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944313#comment-14944313 ] Wangda Tan commented on YARN-4215: -- Thanks [~Naganarasimha]! Patch generally looks good to

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944292#comment-14944292 ] Wangda Tan commented on YARN-3216: -- And forgot to mention: 5. About am-resource-percent pe

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944289#comment-14944289 ] Wangda Tan commented on YARN-3216: -- Thanks [~sunilg]. Went through the patch, some commen

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM periodically for distributed nodelabels

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

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM periodically for distributed nodelabels

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

[jira] [Commented] (YARN-4061) [Fault tolerance] Fault tolerant writer for timeline v2

[ https://issues.apache.org/jira/browse/YARN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944200#comment-14944200 ] Sangjin Lee commented on YARN-4061: --- I don't think the MR JHS is an apt comparison. First

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM periodically for distributed nodelabels

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

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

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

[jira] [Updated] (YARN-4176) Resync NM nodelabels with RM periodically for distributed nodelabels

[ https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4176: - Summary: Resync NM nodelabels with RM periodically for distributed nodelabels (was: Resync NM nodelabels w

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM every x interval for distributed nodelabels

[ https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944179#comment-14944179 ] Wangda Tan commented on YARN-4176: -- Latest patch LGTM, committing.. > Resync NM nodelabel

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944169#comment-14944169 ] Wangda Tan commented on YARN-3964: -- Thanks [~dian.fu] working on this patch and reviews fr

[jira] [Commented] (YARN-4162) Scheduler info in REST, is currently not displaying partition specific queue information similar to UI

[ https://issues.apache.org/jira/browse/YARN-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944144#comment-14944144 ] Wangda Tan commented on YARN-4162: -- Thanks [~Naganarasimha] working on this! Sample REST r

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944130#comment-14944130 ] Varun Saxena commented on YARN-4178: New patch updated. > [storage implementation] app

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

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

[jira] [Updated] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4178: --- Attachment: YARN-4178-YARN-2928.04.patch > [storage implementation] app id as string in row keys can ca

[jira] [Updated] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4178: --- Attachment: (was: YARN-4178-YARN-2928.04.patch) > [storage implementation] app id as string in row

[jira] [Updated] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4178: --- Attachment: YARN-4178-YARN-2928.04.patch [~sjlee0], rebased the patch > [storage implementation] app i

[jira] [Commented] (YARN-4061) [Fault tolerance] Fault tolerant writer for timeline v2

[ https://issues.apache.org/jira/browse/YARN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944067#comment-14944067 ] Li Lu commented on YARN-4061: - Thanks for the review [~sjlee0]! bq. Since the actual storage

[jira] [Commented] (YARN-4162) Scheduler info in REST, is currently not displaying partition specific queue information similar to UI

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

[jira] [Commented] (YARN-4175) Example of use YARN-1197

[ https://issues.apache.org/jira/browse/YARN-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944039#comment-14944039 ] MENG DING commented on YARN-4175: - I am using the example application to test the container

[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&focusedCommentId=14944028#comment-14944028 ] Sangjin Lee commented on YARN-3367: --- bq. Yes i agree with this, but what should be the be

[jira] [Commented] (YARN-4061) [Fault tolerance] Fault tolerant writer for timeline v2

[ https://issues.apache.org/jira/browse/YARN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944009#comment-14944009 ] Sangjin Lee commented on YARN-4061: --- Another thing to consider is also the throughput of

[jira] [Commented] (YARN-4061) [Fault tolerance] Fault tolerant writer for timeline v2

[ https://issues.apache.org/jira/browse/YARN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943999#comment-14943999 ] Sangjin Lee commented on YARN-4061: --- Sorry it took me a while to get to this. Thanks for

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

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

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943957#comment-14943957 ] Sangjin Lee commented on YARN-4178: --- I just committed YARN-3864. Could you please rebase

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943918#comment-14943918 ] Varun Saxena commented on YARN-2902: The new patch does the following over the last pat

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943863#comment-14943863 ] Varun Saxena commented on YARN-4178: Depending on order in which patches go in, YARN-41

[jira] [Updated] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4178: --- Attachment: YARN-4178-YARN-2928.03.patch Updating a patch after merging Writer and Reader utils > [sto

[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&focusedCommentId=14943849#comment-14943849 ] Naganarasimha G R commented on YARN-3367: - Thanks for the feed back [~sjlee0], bq.

[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&focusedCommentId=14943832#comment-14943832 ] Jonathan Eagles commented on YARN-4183: --- [~xgong], this issue is two-fold. 1) The web

[jira] [Updated] (YARN-4162) Scheduler info in REST, is currently not displaying partition specific queue information similar to UI

[ https://issues.apache.org/jira/browse/YARN-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4162: Attachment: YARN-4162.v2.002.patch Hi [~wangda], I have updated the patch with test cases and

[jira] [Commented] (YARN-4185) Retry interval delay for NM client can be improved from the fixed static retry

[ https://issues.apache.org/jira/browse/YARN-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943809#comment-14943809 ] Anubhav Dhoot commented on YARN-4185: - I don't think option 2 where you restart from 1

[jira] [Commented] (YARN-4170) AM need to be notified with priority in AllocateResponse

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

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

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

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943785#comment-14943785 ] Li Lu commented on YARN-4220: - Sure. We can fix it here. Right now I'm passing flow and flowrun

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943781#comment-14943781 ] Jason Lowe commented on YARN-4216: -- The container logs should not be uploaded on NM stop i

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943778#comment-14943778 ] Vrushali C commented on YARN-4178: -- bq. I think we can have a single class TimelineStorage

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943773#comment-14943773 ] Varun Saxena commented on YARN-4220: This wont work even after YARN-3864. /entities end

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943771#comment-14943771 ] Sangjin Lee commented on YARN-3864: --- The latest patch (v.4) LGTM. Unless there are additi

[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&focusedCommentId=14943760#comment-14943760 ] Sangjin Lee commented on YARN-3367: --- Sorry for my late reply. {quote} Timelineclient asy

[jira] [Commented] (YARN-4224) Change the REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943751#comment-14943751 ] Allen Wittenauer commented on YARN-4224: If this is an incompatible change, then th

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943741#comment-14943741 ] Li Lu commented on YARN-4220: - Oh Thanks [~varun_saxena]. Having looked at the code I can see w

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943729#comment-14943729 ] Varun Saxena commented on YARN-4220: [~gtCarrera9] Oh I get it. Even I was wondering wh

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943721#comment-14943721 ] Li Lu commented on YARN-4220: - Well this may be the thing I'm missing now: I made a call {{htt

[jira] [Updated] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3864: --- Attachment: YARN-3864-YARN-2928.04.patch Updating a patch addressing [~sjlee0]'s comments > Implement

[jira] [Updated] (YARN-4170) AM need to be notified with priority in AllocateResponse

[ https://issues.apache.org/jira/browse/YARN-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4170: -- Attachment: 0003-YARN-4170.patch Yes [~rohithsharma] Thank you for sharing the thoughts. Yes, we could send "null

[jira] [Commented] (YARN-4178) [storage implementation] app id as string in row keys can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943703#comment-14943703 ] Sangjin Lee commented on YARN-4178: --- +1 with consolidating WriterUtils and ReaderUtils.

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943702#comment-14943702 ] Varun Saxena commented on YARN-3864: [~sjlee0], thanks for the review. Will address you

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943700#comment-14943700 ] Sangjin Lee commented on YARN-4220: --- Hmm, for any application or generic entity queries,

[jira] [Commented] (YARN-3769) Preemption occurring unnecessarily because preemption doesn't consider user limit

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

[jira] [Commented] (YARN-4221) Store user in app to flow table

[ https://issues.apache.org/jira/browse/YARN-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943668#comment-14943668 ] Sangjin Lee commented on YARN-4221: --- Thanks for turning around and creating this patch qu

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943648#comment-14943648 ] Sangjin Lee commented on YARN-3864: --- Should have refreshed the page first. :) The jenkins

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943645#comment-14943645 ] Sangjin Lee commented on YARN-3864: --- I kicked off another jenkins build. I have reviewed

[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: --- Target Version/s: 2.7.2 (was: 2.8.0) > Killing a container that is localizing can orphan resources in

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

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

Re: [jira] [Commented] (YARN-4185) Retry interval delay for NM client can be improved from the fixed static retry

I don't think option 2 where you restart from 1 makes sense. Its also not a goal to minimize the total wait time. He goal should minimize the time to recover for short intermittent failure while also waiting long enough for long failures before giving up. On Oct 3, 2015 6:43 PM, "Neelesh Srinivas

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943587#comment-14943587 ] MENG DING commented on YARN-1509: - * release audit is not related * will apply for exceptio

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943574#comment-14943574 ] Bibin A Chundatt commented on YARN-4216: When yarn.nodemanager.recovery.supervised=

[jira] [Updated] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3216: -- Attachment: 0003-YARN-3216.patch Hi [~leftnoteasy] Attaching v2 version of patch addressing the major comments. K

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

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

[jira] [Updated] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-4225: - Summary: Add preemption status to yarn queue -status for capacity scheduler (was: Add preemption status to

[jira] [Created] (YARN-4226) Make capacity scheduler queue's preemption status REST API consistent with GUI

Eric Payne created YARN-4226: Summary: Make capacity scheduler queue's preemption status REST API consistent with GUI Key: YARN-4226 URL: https://issues.apache.org/jira/browse/YARN-4226 Project: Hadoop YA

[jira] [Updated] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-4225: - Component/s: capacity scheduler > Add preemption status to yarn queue -status for capacity scheduler >

[jira] [Updated] (YARN-4225) Add preemption status to yarn queue -status

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-4225: - Summary: Add preemption status to yarn queue -status (was: Add preemption status to {{yarn queue -status}}

[jira] [Created] (YARN-4225) Add preemption status to {{yarn queue -status}}

Eric Payne created YARN-4225: Summary: Add preemption status to {{yarn queue -status}} Key: YARN-4225 URL: https://issues.apache.org/jira/browse/YARN-4225 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-3769) Preemption occurring unnecessarily because preemption doesn't consider user limit

[ https://issues.apache.org/jira/browse/YARN-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-3769: - Attachment: YARN-3769-branch-2.002.patch > Preemption occurring unnecessarily because preemption doesn't co

[jira] [Updated] (YARN-3769) Preemption occurring unnecessarily because preemption doesn't consider user limit

[ https://issues.apache.org/jira/browse/YARN-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-3769: - Attachment: (was: YARN-3769-branch-2.002.patch) > Preemption occurring unnecessarily because preemption

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.4.patch Submit the new patch that fixes the whitespace issue > Make AMRMClient support

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943425#comment-14943425 ] Sunil G commented on YARN-3216: --- Hi [~eepayne] Thank you for sharing the comments. As Naga me

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943406#comment-14943406 ] MENG DING commented on YARN-1510: - * The release audit is not related. * The failed test pa

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943368#comment-14943368 ] Jason Lowe commented on YARN-4216: -- Yes, the document should be updated to cover that prop

[jira] [Commented] (YARN-4223) Findbugs warnings in hadoop-yarn-server-nodemanager project

[ https://issues.apache.org/jira/browse/YARN-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943328#comment-14943328 ] Varun Saxena commented on YARN-4223: Release audit warning is unrelated. There is HDFS-

[jira] [Commented] (YARN-4224) Change the REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943320#comment-14943320 ] Varun Saxena commented on YARN-4224: My proposal would be as under * *Query flows* Cu

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943315#comment-14943315 ] Varun Vasudev commented on YARN-4009: - The release audit and findbugs issues are unrela

[jira] [Commented] (YARN-4224) Change the REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943298#comment-14943298 ] Varun Saxena commented on YARN-4224: [~sjlee0] raised this point on YARN-3864. Current

[jira] [Created] (YARN-4224) Change the REST interface to conform to current REST APIs' in YARN

Varun Saxena created YARN-4224: -- Summary: Change the REST interface to conform to current REST APIs' in YARN Key: YARN-4224 URL: https://issues.apache.org/jira/browse/YARN-4224 Project: Hadoop YARN

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

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

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943124#comment-14943124 ] Bibin A Chundatt commented on YARN-4216: [Document|https://hadoop.apache.org/docs/c

  1   2   >