[jira] [Commented] (YARN-3168) Convert site documentation from apt to markdown

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

[jira] [Updated] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3272: -- Attachment: YARN-3272.2.patch thanks for reviewing the patch, Wangda ! Addressed all comments Surface

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341179#comment-14341179 ] Wangda Tan commented on YARN-3265: -- Thanks for your comments, addressed all of them, and:

[jira] [Updated] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3265: - Attachment: YARN-3265.5.patch CapacityScheduler deadlock when computing absolute max avail capacity (fix

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341178#comment-14341178 ] Wangda Tan commented on YARN-3265: -- Thanks for your comments, addressed all of them, and:

[jira] [Commented] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341215#comment-14341215 ] Hadoop QA commented on YARN-3272: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341267#comment-14341267 ] Hadoop QA commented on YARN-3272: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341279#comment-14341279 ] Hadoop QA commented on YARN-3265: - {color:red}-1 overall{color}. Here are the results of

[jira] [Resolved] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-3168. Resolution: Fixed Fix Version/s: 3.0.0 Target Version/s: 3.0.0 (was: 2.7.0)

[jira] [Updated] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3168: --- Affects Version/s: (was: 2.7.0) 3.0.0 Convert site documentation

[jira] [Commented] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341289#comment-14341289 ] Rohit Agarwal commented on YARN-3168: - Sure. I can update the patch on YARN-3199 to be

[jira] [Updated] (YARN-3199) Fair Scheduler documentation improvements

[ https://issues.apache.org/jira/browse/YARN-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Agarwal updated YARN-3199: Attachment: YARN-3199-1.patch [~aw] Updated the patch to markdown. Fair Scheduler documentation

[jira] [Commented] (YARN-3199) Fair Scheduler documentation improvements

[ https://issues.apache.org/jira/browse/YARN-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341360#comment-14341360 ] Hadoop QA commented on YARN-3199: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341185#comment-14341185 ] Li Lu commented on YARN-3276: - Hi [~djp], I totally agree that we should fix this. Patch LGTM.

[jira] [Commented] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

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

[jira] [Commented] (YARN-3255) RM, NM, JobHistoryServer, and WebAppProxyServer's main() should support generic options

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

[jira] [Commented] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340354#comment-14340354 ] Zhijie Shen commented on YARN-3125: --- +1 for the new UT patch. Will commit the DS and the

[jira] [Resolved] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-3125. --- Resolution: Fixed Fix Version/s: YARN-2928 Hadoop Flags: Reviewed Committed to branch

[jira] [Updated] (YARN-2981) DockerContainerExecutor must support a Cluster-wide default Docker image

[ https://issues.apache.org/jira/browse/YARN-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abin Shahab updated YARN-2981: -- Description: This allows the yarn administrator to add a cluster-wide default docker image that will be

[jira] [Commented] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340408#comment-14340408 ] Junping Du commented on YARN-3125: -- Thanks [~gtCarrera9] for adding a UT and [~zjshen] for

[jira] [Created] (YARN-3275) Preemption happening on non-preemptable queues

Eric Payne created YARN-3275: Summary: Preemption happening on non-preemptable queues Key: YARN-3275 URL: https://issues.apache.org/jira/browse/YARN-3275 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340380#comment-14340380 ] Karthik Kambatla commented on YARN-2962: [~varun_saxena] - it will indeed be

[jira] [Commented] (YARN-3167) [Aggregator implementation] Implement the core functionality of the base aggregator service

[ https://issues.apache.org/jira/browse/YARN-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340448#comment-14340448 ] Zhijie Shen commented on YARN-3167: --- Hi Vrushali, FYI, we have an integration test inside

[jira] [Assigned] (YARN-3274) FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY

[ https://issues.apache.org/jira/browse/YARN-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-3274: -- Assignee: Varun Saxena FIFOScheduler should assign the same container number up to

[jira] [Commented] (YARN-3087) [Aggregator implementation] the REST server (web server) for per-node aggregator does not work if it runs inside node manager

[ https://issues.apache.org/jira/browse/YARN-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340392#comment-14340392 ] Junping Du commented on YARN-3087: -- bq. Similar code also appear in v1 timeline object

[jira] [Updated] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3276: - Attachment: YARN-3276.patch Upload a patch to fix it. Fix NPE and refactor in some map cast for

[jira] [Commented] (YARN-3275) Preemption happening on non-preemptable queues

[ https://issues.apache.org/jira/browse/YARN-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340393#comment-14340393 ] Eric Payne commented on YARN-3275: -- This situation can happen under the following

[jira] [Commented] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340427#comment-14340427 ] Tsuyoshi Ozawa commented on YARN-3276: -- [~djp] thank you for taking this issue. Should

[jira] [Commented] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

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

[jira] [Commented] (YARN-3255) RM, NM, JobHistoryServer, and WebAppProxyServer's main() should support generic options

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

[jira] [Updated] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-2820: - Attachment: YARN-2820.007.patch The test failure looks not related. Submitting a patch again. Do

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340148#comment-14340148 ] Hadoop QA commented on YARN-2820: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3167) [Aggregator implementation] Implement the core functionality of the base aggregator service

[ https://issues.apache.org/jira/browse/YARN-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340491#comment-14340491 ] Vrushali C commented on YARN-3167: -- Hi [~zjshen] I see, thanks Zhijie! I will look at that

[jira] [Updated] (YARN-3033) [Aggregator wireup] Implement NM starting the standalone ATS writer companion

[ https://issues.apache.org/jira/browse/YARN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3033: Summary: [Aggregator wireup] Implement NM starting the standalone ATS writer companion (was: [Aggregator wireup]

[jira] [Updated] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3265: - Attachment: YARN-3265.2.patch Attached patch addressed all comments from [~vinodkv]: bq. It's very

[jira] [Updated] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3265: - Issue Type: Sub-task (was: Bug) Parent: YARN-1198 CapacityScheduler deadlock when computing

[jira] [Commented] (YARN-3262) Surface application outstanding resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340529#comment-14340529 ] Wangda Tan commented on YARN-3262: -- Thanks for updating, my only comment is

[jira] [Updated] (YARN-3033) [Aggregator wireup] Implement NM starting the standalone ATS writer companion

[ https://issues.apache.org/jira/browse/YARN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3033: Description: Per design in YARN-2928, implement node managers starting the ATS writer companion. In YARN-2928, we

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340576#comment-14340576 ] Wangda Tan commented on YARN-3265: -- Patch is huge because it changes

[jira] [Updated] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3265: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-3243) CapacityScheduler deadlock when

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1809: -- Target Version/s: 2.7.0 (was: 2.6.0) Synchronize RM and Generic History Service Web-UIs

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340618#comment-14340618 ] Jian He commented on YARN-3222: --- lgtm, are the test failures related ?

[jira] [Updated] (YARN-3262) Surface application outstanding resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3262: -- Attachment: YARN-3262.5.patch Surface application outstanding resource requests table

[jira] [Updated] (YARN-3033) [Aggregator wireup] Implement NM starting the standalone ATS writer companion

[ https://issues.apache.org/jira/browse/YARN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3033: Description: Per design in YARN-2928, implement node managers starting the ATS writer companion. In YARN-2928, we

[jira] [Updated] (YARN-3033) [Aggregator wireup] Implement NM starting the standalone ATS writer companion

[ https://issues.apache.org/jira/browse/YARN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3033: Description: Per design in YARN-2928, implement node managers starting the ATS writer companion. In YARN-2928, we

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340596#comment-14340596 ] Wangda Tan commented on YARN-3265: -- Instead of making this as a sub JIRA of YARN-3243, I

[jira] [Commented] (YARN-3255) RM, NM, JobHistoryServer, and WebAppProxyServer's main() should support generic options

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

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340307#comment-14340307 ] Tsuyoshi Ozawa commented on YARN-2820: -- +1, committing this shortly. Do retry in

[jira] [Updated] (YARN-2820) Retry in FileSystemRMStateStore when FS's operations fail due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-2820: - Summary: Retry in FileSystemRMStateStore when FS's operations fail due to IOException. (was: Do

[jira] [Updated] (YARN-3274) FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY

[ https://issues.apache.org/jira/browse/YARN-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3274: - Description: Per discussion in MAPREDUCE-5583, FifoScheduler should assign containers that up to the

[jira] [Resolved] (YARN-2592) Preemption can kill containers to fulfil need of already over-capacity queue.

[ https://issues.apache.org/jira/browse/YARN-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne resolved YARN-2592. -- Resolution: Invalid Preemption can kill containers to fulfil need of already over-capacity queue.

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340304#comment-14340304 ] Tsuyoshi Ozawa commented on YARN-2820: -- [~zxu] My bad. Closeable should be idempotent,

[jira] [Commented] (YARN-3255) RM, NM, JobHistoryServer, and WebAppProxyServer's main() should support generic options

[ https://issues.apache.org/jira/browse/YARN-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340290#comment-14340290 ] Hudson commented on YARN-3255: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2067 (See

[jira] [Updated] (YARN-3274) FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY

[ https://issues.apache.org/jira/browse/YARN-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3274: - Summary: FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY (was:

[jira] [Commented] (YARN-2592) Preemption can kill containers to fulfil need of already over-capacity queue.

[ https://issues.apache.org/jira/browse/YARN-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340241#comment-14340241 ] Eric Payne commented on YARN-2592: -- Closing this, since it is expected that as long as

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340265#comment-14340265 ] Tsuyoshi Ozawa commented on YARN-2820: -- [~zxu] Thank you for updating. I rethink abut

[jira] [Commented] (YARN-2820) Retry in FileSystemRMStateStore when FS's operations fail due to IOException.

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

[jira] [Commented] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

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

[jira] [Commented] (YARN-3217) Remove httpclient dependency from hadoop-yarn-server-web-proxy

[ https://issues.apache.org/jira/browse/YARN-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340283#comment-14340283 ] Hudson commented on YARN-3217: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2067 (See

[jira] [Created] (YARN-3274) FIFOScheduler should assign the same container number equal to ResourceRequest ask for ANY

Junping Du created YARN-3274: Summary: FIFOScheduler should assign the same container number equal to ResourceRequest ask for ANY Key: YARN-3274 URL: https://issues.apache.org/jira/browse/YARN-3274

[jira] [Commented] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340625#comment-14340625 ] Rohit Agarwal commented on YARN-3168: - [~gururaj] Please also incorporate YARN-3199.

[jira] [Updated] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3276: - Attachment: YARN-3276-v2.patch Thanks [~ozawa] for review and comments! Just add test cases in v2 patch.

[jira] [Commented] (YARN-3275) Preemption happening on non-preemptable queues

[ https://issues.apache.org/jira/browse/YARN-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340702#comment-14340702 ] Vinod Kumar Vavilapalli commented on YARN-3275: --- bq. also over its absolute

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340732#comment-14340732 ] Wangda Tan commented on YARN-3197: -- Patch looks good to me, I'm OK with both with/without

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340630#comment-14340630 ] Hadoop QA commented on YARN-3265: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-964) Give a parameter that can set AM retry interval

[ https://issues.apache.org/jira/browse/YARN-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340718#comment-14340718 ] Vinod Kumar Vavilapalli commented on YARN-964: -- Old JIRA. The right solution is

[jira] [Commented] (YARN-3280) Findbug issue in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340769#comment-14340769 ] Varun Saxena commented on YARN-3280: [~xgong], duplicate of YARN-3204 ? Findbug issue

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340653#comment-14340653 ] Jian He commented on YARN-3222: --- actually, we may not need to send the NODE_USABLE event, if

[jira] [Created] (YARN-3277) Queue's current-max-limit should be updated before allocate reserved container.

Wangda Tan created YARN-3277: Summary: Queue's current-max-limit should be updated before allocate reserved container. Key: YARN-3277 URL: https://issues.apache.org/jira/browse/YARN-3277 Project: Hadoop

[jira] [Commented] (YARN-3278) Queue's current-max-limit should be updated when container allocated/released in another queue

[ https://issues.apache.org/jira/browse/YARN-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340711#comment-14340711 ] Wangda Tan commented on YARN-3278: -- One possible solution is forced update

[jira] [Updated] (YARN-3275) Preemption happening on non-preemptable queues

[ https://issues.apache.org/jira/browse/YARN-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-3275: - Description: YARN-2056 introduced the ability to turn preemption on and off at the queue level. In cases

[jira] [Updated] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3265: - Attachment: YARN-3265.3.patch A stupid typo in the patch, updated. CapacityScheduler deadlock when

[jira] [Updated] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3276: - Target Version/s: YARN-2928 Fix NPE and refactor in some map cast for TimelineEntity

[jira] [Commented] (YARN-2423) TimelineClient should wrap all GET APIs to facilitate Java users

[ https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340691#comment-14340691 ] Robert Kanter commented on YARN-2423: - If we're concerned that this Java API would

[jira] [Created] (YARN-3278) Queue's current-max-limit should be updated when container allocated/released in another queue

Wangda Tan created YARN-3278: Summary: Queue's current-max-limit should be updated when container allocated/released in another queue Key: YARN-3278 URL: https://issues.apache.org/jira/browse/YARN-3278

[jira] [Commented] (YARN-2820) Retry in FileSystemRMStateStore when FS's operations fail due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340714#comment-14340714 ] zhihai xu commented on YARN-2820: - Thanks [~ozawa] for valuable feedback and committing the

[jira] [Commented] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

[ https://issues.apache.org/jira/browse/YARN-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340716#comment-14340716 ] Wangda Tan commented on YARN-1198: -- While working on YARN-3265, I found there're several

[jira] [Commented] (YARN-3111) Fix ratio problem on FairScheduler page

[ https://issues.apache.org/jira/browse/YARN-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340720#comment-14340720 ] Ashwin Shankar commented on YARN-3111: -- Hey [~kasha], When you get a chance, can you

[jira] [Commented] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340727#comment-14340727 ] Hadoop QA commented on YARN-3210: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3262) Surface application outstanding resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340735#comment-14340735 ] Hadoop QA commented on YARN-3262: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340736#comment-14340736 ] Vinod Kumar Vavilapalli commented on YARN-3197: --- Yeah, I meant no need for

[jira] [Commented] (YARN-3262) Surface application outstanding resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340627#comment-14340627 ] Jian He commented on YARN-3262: --- changed the name to nodeLabelExpression, thanks ! Surface

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1809: Attachment: YARN-1809.14.patch change tab name from Master Container to AM Container Synchronize RM and

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340682#comment-14340682 ] Hadoop QA commented on YARN-3265: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3210: Attachment: YARN-3210-022715.patch In this patch I refactored the timeline aggregators according to our discussion

[jira] [Created] (YARN-3279) AvailableResource of QueueMetrics should consider queue's current-max-limit

Wangda Tan created YARN-3279: Summary: AvailableResource of QueueMetrics should consider queue's current-max-limit Key: YARN-3279 URL: https://issues.apache.org/jira/browse/YARN-3279 Project: Hadoop YARN

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340748#comment-14340748 ] Xuan Gong commented on YARN-1809: - -1 on findbug is un-related. Filed a separate ticket to

[jira] [Created] (YARN-3280) Findbug issue in FairScheduler

Xuan Gong created YARN-3280: --- Summary: Findbug issue in FairScheduler Key: YARN-3280 URL: https://issues.apache.org/jira/browse/YARN-3280 Project: Hadoop YARN Issue Type: Bug Components:

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340797#comment-14340797 ] Hadoop QA commented on YARN-1809: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3275) Preemption happening on non-preemptable queues

[ https://issues.apache.org/jira/browse/YARN-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-3275: - Attachment: YARN-3275.v1.txt Preemption happening on non-preemptable queues

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340837#comment-14340837 ] Chang Li commented on YARN-3267: [~pramachandran] Could you take a look at my solution in

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN_3267_WIP.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340894#comment-14340894 ] Zhijie Shen commented on YARN-1809: --- Xuan, thanks for updating the patch. It looks good

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340830#comment-14340830 ] Hadoop QA commented on YARN-3265: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340893#comment-14340893 ] Hadoop QA commented on YARN-3267: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN_3267_WIP1.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340914#comment-14340914 ] Hadoop QA commented on YARN-3267: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2820) Do retry in FileSystemRMStateStore for better error recovery when update/store failure due to IOException.

[ https://issues.apache.org/jira/browse/YARN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14339910#comment-14339910 ] Tsuyoshi Ozawa commented on YARN-2820: -- [~zxu] try-with-resources statement is a new

[jira] [Updated] (YARN-2693) Priority Label Manager in RM to manage application priority based on configuration

[ https://issues.apache.org/jira/browse/YARN-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2693: -- Attachment: 0006-YARN-2693.patch Rebasing and uploading the patch. Priority Label Manager in RM to manage

[jira] [Updated] (YARN-2693) Priority Label Manager in RM to manage application priority based on configuration

[ https://issues.apache.org/jira/browse/YARN-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2693: -- Attachment: (was: 0006-YARN-2693.patch) Priority Label Manager in RM to manage application priority based

  1   2   >