[jira] [Updated] (YARN-3202) Improve master container resource release time ICO work preserving restart enabled

[ https://issues.apache.org/jira/browse/YARN-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3202: - Attachment: 0001-YARN-3202.patch Improve master container resource release time ICO work preserving restart

[jira] [Updated] (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:all-tabpanel ] Rohith updated YARN-3222: - Attachment: 0001-YARN-3222.patch RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential

[jira] [Commented] (YARN-3202) Improve master container resource release time ICO work preserving restart enabled

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

[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=14333286#comment-14333286 ] Gururaj Shetty commented on YARN-3168: -- [~aw] Will share the latest patch early

[jira] [Commented] (YARN-3202) Improve master container resource release time ICO work preserving restart enabled

[ https://issues.apache.org/jira/browse/YARN-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333253#comment-14333253 ] Rohith commented on YARN-3202: -- Kindly review the patch, the patch is verified mannually

[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=14333252#comment-14333252 ] Rohith commented on YARN-3222: -- Kindly review the patch, the patch is verified mannually

[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=1406#comment-1406 ] Hadoop QA commented on YARN-3222: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1409#comment-1409 ] Junping Du commented on YARN-3039: -- Thanks [~sjlee0] for comments! bq. I'm also thinking

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

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

[jira] [Assigned] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-3115: Assignee: Junping Du (was: Zhijie Shen) [Aggregator wireup] Work-preserving restarting of

[jira] [Commented] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333529#comment-14333529 ] Junping Du commented on YARN-3115: -- Thanks [~zjshen]! Taking it over. Looks like it

[jira] [Updated] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3115: - Assignee: Zhijie Shen (was: Junping Du) [Aggregator wireup] Work-preserving restarting of per-node

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v3.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Assigned] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-3115: Assignee: Junping Du (was: Zhijie Shen) [Aggregator wireup] Work-preserving restarting of

[jira] [Updated] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3039: - Attachment: YARN-3039-no-test.patch Just finish the first patch with core changes needed in option 2

[jira] [Updated] (YARN-3195) Add -help to yarn logs and nodes CLI command

[ https://issues.apache.org/jira/browse/YARN-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated YARN-3195: --- Attachment: (was: YARN-3195.patch) Add -help to yarn logs and nodes CLI command

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v4.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

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

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333662#comment-14333662 ] Chang Li commented on YARN-3131: [~leftnoteasy] YarnClientImpl should check FAILED and

[jira] [Commented] (YARN-3195) Add -help to yarn logs and nodes CLI command

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

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333658#comment-14333658 ] Chang Li commented on YARN-3131: [~wangda]Thanks for reviewing my work! I have updated my

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

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

[jira] [Updated] (YARN-3195) Add -help to yarn logs and nodes CLI command

[ https://issues.apache.org/jira/browse/YARN-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated YARN-3195: --- Attachment: YARN-3195.20150223-1.patch Updated the failure Test cases Add -help to yarn

[jira] [Commented] (YARN-3239) WebAppProxy does not support a final tracking url which has query fragments and params

[ https://issues.apache.org/jira/browse/YARN-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333626#comment-14333626 ] Jason Lowe commented on YARN-3239: -- the WebProxyServlet does support appending the

[jira] [Commented] (YARN-2986) (Umbrella) Support hierarchical and unified scheduler configuration

[ https://issues.apache.org/jira/browse/YARN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333728#comment-14333728 ] Wangda Tan commented on YARN-2986: -- Hi [~sunilg], Thanks for sharing your thoughts :).

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333737#comment-14333737 ] Wangda Tan commented on YARN-3131: -- Thanks for update, LGTM, +1. YarnClientImpl should

[jira] [Commented] (YARN-3239) WebAppProxy does not support a final tracking url which has query fragments and params

[ https://issues.apache.org/jira/browse/YARN-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333868#comment-14333868 ] Jian He commented on YARN-3239: --- thanks for reviewing, Jason ! bq. However it doesn't look

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333880#comment-14333880 ] Sidharta Seethana commented on YARN-2140: - Hi [~ywskycn] , [~vvasudev] and I have

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333883#comment-14333883 ] Sidharta Seethana commented on YARN-2140: - I have attached the design doc. Thanks!

[jira] [Updated] (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:all-tabpanel ] Li Lu updated YARN-3087: Attachment: YARN-3087-022315.patch Since this issue is blocking some of us on the aggregator side, I did some

[jira] [Updated] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3231: -- Attachment: (was: YARN-3231.v1.patch) FairScheduler changing queueMaxRunningApps on the fly will cause all

[jira] [Updated] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3231: -- Attachment: YARN-3231.v1.patch FairScheduler changing queueMaxRunningApps on the fly will cause all pending

[jira] [Updated] (YARN-3240) [Data Mode] Implement client API to put generic entities

[ https://issues.apache.org/jira/browse/YARN-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3240: -- Attachment: YARN-3240.2.patch Made a new patch: 1. Fix the bugs in the previous one. 2. Add an

[jira] [Updated] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-2140: Attachment: NetworkAsAResourceDesign.pdf Network Bandwidth as a resource in YARN. Add

[jira] [Commented] (YARN-3239) WebAppProxy does not support a final tracking url which has query fragments and params

[ https://issues.apache.org/jira/browse/YARN-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334003#comment-14334003 ] Jason Lowe commented on YARN-3239: -- bq. I was trying to do that, but after doing some

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334159#comment-14334159 ] Zhijie Shen commented on YARN-3039: --- bq. The RM will likely not use the service

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334206#comment-14334206 ] Zhijie Shen commented on YARN-3039: --- One addition issue related the rm state store:

[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 ] zhihai xu updated YARN-2820: Attachment: YARN-2820.004.patch Do retry in FileSystemRMStateStore for better error recovery when

[jira] [Created] (YARN-3245) Find a way to reserve AMContainer resource to launch clean-up container in CapacityScheduler

Xuan Gong created YARN-3245: --- Summary: Find a way to reserve AMContainer resource to launch clean-up container in CapacityScheduler Key: YARN-3245 URL: https://issues.apache.org/jira/browse/YARN-3245

[jira] [Commented] (YARN-3245) Find a way to reserve AMContainer resource to launch clean-up container in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334446#comment-14334446 ] Xuan Gong commented on YARN-3245: - More details here: Currently, we have two directions: *

[jira] [Commented] (YARN-3246) Add a CLEANUP state in RMApp to track the status of clean-up container.

[ https://issues.apache.org/jira/browse/YARN-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334458#comment-14334458 ] Xuan Gong commented on YARN-3246: - More details: We will add a cleanup state for RMApp. If

[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 ] zhihai xu updated YARN-2820: Attachment: (was: YARN-2820.004.patch) Do retry in FileSystemRMStateStore for better error recovery

[jira] [Commented] (YARN-3195) Add -help to yarn logs and nodes CLI command

[ https://issues.apache.org/jira/browse/YARN-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334402#comment-14334402 ] Jagadesh Kiran N commented on YARN-3195: HI the test case failing at

[jira] [Commented] (YARN-3169) drop the useless yarn overview document

[ https://issues.apache.org/jira/browse/YARN-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334229#comment-14334229 ] Allen Wittenauer commented on YARN-3169: index.apt.vm and all the bits that

[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=14334287#comment-14334287 ] Akira AJISAKA commented on YARN-3217: - Thanks [~brahmareddy] for creating the patch.

[jira] [Created] (YARN-3243) CapacityScheduler should pass headroom from parent to children to make sure ParentQueue obey its capacity limits.

Wangda Tan created YARN-3243: Summary: CapacityScheduler should pass headroom from parent to children to make sure ParentQueue obey its capacity limits. Key: YARN-3243 URL:

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

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

[jira] [Updated] (YARN-3244) Add user specified information for clean-up container in ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3244: Attachment: YARN-3244.1.patch Add user specified information for clean-up container in

[jira] [Updated] (YARN-3246) Add a CLEANUP state in RMApp to track the status of clean-up container.

[ https://issues.apache.org/jira/browse/YARN-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3246: Description: The clean-up container will be launched by RM, and we need to keep track the status for it,

[jira] [Commented] (YARN-3243) CapacityScheduler should pass headroom from parent to children to make sure ParentQueue obey its capacity limits.

[ https://issues.apache.org/jira/browse/YARN-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334200#comment-14334200 ] Vinod Kumar Vavilapalli commented on YARN-3243: --- +1, this will greatly simply

[jira] [Created] (YARN-3244) Add user specified information for clean-up container in ApplicationSubmissionContext

Xuan Gong created YARN-3244: --- Summary: Add user specified information for clean-up container in ApplicationSubmissionContext Key: YARN-3244 URL: https://issues.apache.org/jira/browse/YARN-3244 Project:

[jira] [Commented] (YARN-3244) Add user specified information for clean-up container in ApplicationSubmissionContext

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

[jira] [Updated] (YARN-3195) Add -help to yarn logs and nodes CLI command

[ https://issues.apache.org/jira/browse/YARN-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-3195: Hadoop Flags: Reviewed Add -help to yarn logs and nodes CLI command

[jira] [Commented] (YARN-3195) Add -help to yarn logs and nodes CLI command

[ https://issues.apache.org/jira/browse/YARN-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334486#comment-14334486 ] Devaraj K commented on YARN-3195: - +1, latest patch looks good to me. Add -help to yarn

[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=14334188#comment-14334188 ] Li Lu commented on YARN-3087: - Hi [~zjshen], thanks for the feedback! Seems like these two

[jira] [Assigned] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abin Shahab reassigned YARN-3080: - Assignee: Abin Shahab The DockerContainerExecutor could not write the right pid to container

[jira] [Updated] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abin Shahab updated YARN-3080: -- Attachment: YARN-3080.patch Tested on trunk The DockerContainerExecutor could not write the right pid

[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 ] zhihai xu updated YARN-2820: Attachment: YARN-2820.004.patch Do retry in FileSystemRMStateStore for better error recovery when

[jira] [Updated] (YARN-3245) Find a way to reserve AMContainer resource to launch clean-up container in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3245: Description: The clean-up container will be launched after the application is finished/killed/failed.

[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: Labels: refactor (was: ) [Source organization] Refactor timeline aggregator according to new code organization

[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=14334381#comment-14334381 ] zhihai xu commented on YARN-2820: - [~ozawa], Sorry for the delay to update the patch. Your

[jira] [Created] (YARN-3246) Add a CLEANUP state in RMApp to track the status of clean-up container.

Xuan Gong created YARN-3246: --- Summary: Add a CLEANUP state in RMApp to track the status of clean-up container. Key: YARN-3246 URL: https://issues.apache.org/jira/browse/YARN-3246 Project: Hadoop YARN

[jira] [Created] (YARN-3247) TestQueueMappings failure for FairScheduler

zhihai xu created YARN-3247: --- Summary: TestQueueMappings failure for FairScheduler Key: YARN-3247 URL: https://issues.apache.org/jira/browse/YARN-3247 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-3247) TestQueueMappings failure for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3247: Attachment: YARN-3247.000.patch TestQueueMappings failure for FairScheduler

[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=14334179#comment-14334179 ] Zhijie Shen commented on YARN-3087: --- Thanks for the patch. It seems to be a promising

[jira] [Commented] (YARN-2797) TestWorkPreservingRMRestart should use ParametrizedSchedulerTestBase

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

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334056#comment-14334056 ] Jian He commented on YARN-3131: --- looks good overall, some minor comments on my side - the

[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=14334053#comment-14334053 ] Hadoop QA commented on YARN-3087: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334060#comment-14334060 ] Jian He commented on YARN-3131: --- Failed to submit application to YARN : - we may mention the

[jira] [Commented] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

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

[jira] [Commented] (YARN-2986) (Umbrella) Support hierarchical and unified scheduler configuration

[ https://issues.apache.org/jira/browse/YARN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334079#comment-14334079 ] Jian He commented on YARN-2986: --- Regarding the policy-properties take , I have one doubt that