[jira] [Commented] (YARN-3553) TreeSet is not a nice container for organizing schedulableEntities.

[ https://issues.apache.org/jira/browse/YARN-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526295#comment-14526295 ] Xianyin Xin commented on YARN-3553: --- Thanks, [~leftnoteasy] and [~cwelch]. Now that it is

[jira] [Commented] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526296#comment-14526296 ] Chen He commented on YARN-1612: --- Thank you for reviewing, Karthik, I will update the patch

[jira] [Commented] (YARN-3523) Cleanup ResourceManagerAdministrationProtocol interface audience

[ https://issues.apache.org/jira/browse/YARN-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526301#comment-14526301 ] Naganarasimha G R commented on YARN-3523: - Hi [~vinodkv], Point noted :), as per my

[jira] [Updated] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3018: Attachment: YARN-3018-1.patch Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and

[jira] [Commented] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526307#comment-14526307 ] nijel commented on YARN-3018: - Thanks [~leftnoteasy] Uploaded the patch Unify the default

[jira] [Commented] (YARN-3069) Document missing properties in yarn-default.xml

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

[jira] [Commented] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

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

[jira] [Commented] (YARN-1971) WindowsLocalWrapperScriptBuilder does not check for errors in generated script

[ https://issues.apache.org/jira/browse/YARN-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526344#comment-14526344 ] Remus Rusanu commented on YARN-1971: The problem is that there is no error check in the

[jira] [Commented] (YARN-2775) There is no close method in NMWebServices#getLogs()

[ https://issues.apache.org/jira/browse/YARN-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526366#comment-14526366 ] Tsuyoshi Ozawa commented on YARN-2775: -- [~skrho], thank you for taking this issue. I

[jira] [Commented] (YARN-3557) Support Intel Trusted Execution Technology(TXT) in YARN scheduler

[ https://issues.apache.org/jira/browse/YARN-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526399#comment-14526399 ] Sunil G commented on YARN-3557: --- bq.Currently for centralized node label configuration, it

[jira] [Commented] (YARN-3557) Support Intel Trusted Execution Technology(TXT) in YARN scheduler

[ https://issues.apache.org/jira/browse/YARN-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526416#comment-14526416 ] Dian Fu commented on YARN-3557: --- Hi [~sunilg], Thanks for your comments. {quote}Apart from

[jira] [Commented] (YARN-2305) When a container is in reserved state then total cluster memory is displayed wrongly.

[ https://issues.apache.org/jira/browse/YARN-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526423#comment-14526423 ] Sunil G commented on YARN-2305: --- Yes. This is can be closed. I have checked, and it was not

[jira] [Updated] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3018: Attachment: YARN-3018-2.patch Updated the patch to remove the white spaces Unify the default value for

[jira] [Commented] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

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

[jira] [Commented] (YARN-2293) Scoring for NMs to identify a better candidate to launch AMs

[ https://issues.apache.org/jira/browse/YARN-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526441#comment-14526441 ] Sunil G commented on YARN-2293: --- Hi [~zjshen] This work is moved to YARN-2005, I will share a

[jira] [Resolved] (YARN-2293) Scoring for NMs to identify a better candidate to launch AMs

[ https://issues.apache.org/jira/browse/YARN-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G resolved YARN-2293. --- Resolution: Duplicate Scoring for NMs to identify a better candidate to launch AMs

[jira] [Commented] (YARN-2256) Too many nodemanager and resourcemanager audit logs are generated

[ https://issues.apache.org/jira/browse/YARN-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526445#comment-14526445 ] Varun Saxena commented on YARN-2256: [~zjshen], just to brief you on the issue; in our

[jira] [Commented] (YARN-2267) Auxiliary Service support in RM

[ https://issues.apache.org/jira/browse/YARN-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526446#comment-14526446 ] Sunil G commented on YARN-2267: --- It would be a good feature if we can plugin few resource

[jira] [Commented] (YARN-3148) allow CORS related headers to passthrough in WebAppProxyServlet

[ https://issues.apache.org/jira/browse/YARN-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526447#comment-14526447 ] Varun Saxena commented on YARN-3148: Thanks [~gtCarrera] for looking at this. Will

[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-tabpanelfocusedCommentId=14526452#comment-14526452 ] Varun Saxena commented on YARN-2902: [~leftnoteasy], sorry for the delay. Was on long

[jira] [Updated] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3018: Attachment: YARN-3018-3.patch Re trigger the CIS. Patch was wrongly generated sorry for the noise Unify the

[jira] [Commented] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526466#comment-14526466 ] Hadoop QA commented on YARN-3018: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Resolved] (YARN-1662) Capacity Scheduler reservation issue cause Job Hang

[ https://issues.apache.org/jira/browse/YARN-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G resolved YARN-1662. --- Resolution: Invalid Capacity Scheduler reservation issue cause Job Hang

[jira] [Commented] (YARN-1662) Capacity Scheduler reservation issue cause Job Hang

[ https://issues.apache.org/jira/browse/YARN-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526473#comment-14526473 ] Sunil G commented on YARN-1662: --- Yes [~jianhe] we can close this issue. After YARN-1769, we

[jira] [Commented] (YARN-3097) Logging of resource recovery on NM restart has redundancies

[ https://issues.apache.org/jira/browse/YARN-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526577#comment-14526577 ] Eric Payne commented on YARN-3097: -- {quote} -1 The patch doesn't appear to include

[jira] [Commented] (YARN-3562) unit tests failures and issues found from findbug from earlier ATS checkins

[ https://issues.apache.org/jira/browse/YARN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526578#comment-14526578 ] Naganarasimha G R commented on YARN-3562: - Seems to be some issue with Jenkins,

[jira] [Commented] (YARN-3474) Add a way to let NM wait RM to come back, not kill running containers

[ https://issues.apache.org/jira/browse/YARN-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526588#comment-14526588 ] Jun Gong commented on YARN-3474: [~vinodkv] Thank you for the explanation. Closing it now.

[jira] [Resolved] (YARN-3474) Add a way to let NM wait RM to come back, not kill running containers

[ https://issues.apache.org/jira/browse/YARN-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong resolved YARN-3474. Resolution: Invalid Add a way to let NM wait RM to come back, not kill running containers

[jira] [Commented] (YARN-2729) Support script based NodeLabelsProvider Interface in Distributed Node Label Configuration Setup

[ https://issues.apache.org/jira/browse/YARN-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526623#comment-14526623 ] Naganarasimha G R commented on YARN-2729: - Thanks for the review comments

[jira] [Commented] (YARN-3565) NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object instead of String

[ https://issues.apache.org/jira/browse/YARN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526629#comment-14526629 ] Naganarasimha G R commented on YARN-3565: - Thanks for the review comments

[jira] [Updated] (YARN-3523) Cleanup ResourceManagerAdministrationProtocol interface audience

[ https://issues.apache.org/jira/browse/YARN-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3523: Attachment: YARN-3523.20150504-1.patch Have checked the 2.7.0 api docs and neither this

[jira] [Updated] (YARN-2622) RM should put the application related timeline data into a secured domain

[ https://issues.apache.org/jira/browse/YARN-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2622: - Target Version/s: (was: 2.6.0) RM should put the application related timeline data into a secured

[jira] [Commented] (YARN-2618) Avoid over-allocation of disk resources

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

[jira] [Commented] (YARN-3523) Cleanup ResourceManagerAdministrationProtocol interface audience

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

[jira] [Commented] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526747#comment-14526747 ] Sunil G commented on YARN-3521: --- 1. bq.Should be exclusivity. Yes. I updated the same 2.

[jira] [Updated] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3521: -- Attachment: 0004-YARN-3521.patch [~vinodkv] and [~leftnoteasy] Pls share your thoughts on this updated patch.

[jira] [Commented] (YARN-3097) Logging of resource recovery on NM restart has redundancies

[ https://issues.apache.org/jira/browse/YARN-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526755#comment-14526755 ] Jason Lowe commented on YARN-3097: -- +1, committing this. Logging of resource recovery on

[jira] [Commented] (YARN-3388) Allocation in LeafQueue could get stuck because DRF calculator isn't well supported when computing user-limit

[ https://issues.apache.org/jira/browse/YARN-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526763#comment-14526763 ] Nathan Roberts commented on YARN-3388: -- Yes. I have a patch which I think is close. I

[jira] [Commented] (YARN-3097) Logging of resource recovery on NM restart has redundancies

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

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526775#comment-14526775 ] Jason Lowe commented on YARN-3554: -- YARN-3518 is a separate concern with different

[jira] [Commented] (YARN-2618) Avoid over-allocation of disk resources

[ https://issues.apache.org/jira/browse/YARN-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526791#comment-14526791 ] Wei Yan commented on YARN-2618: --- Thanks, [~djp], I'll rebase the patch. Avoid

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526934#comment-14526934 ] Naganarasimha G R commented on YARN-3554: - Hi [~jlowe], earlier my query of ideal

[jira] [Commented] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526957#comment-14526957 ] Wilfred Spiegelenburg commented on YARN-3491: - Can we clean up the

[jira] [Commented] (YARN-1564) add some basic workflow YARN services

[ https://issues.apache.org/jira/browse/YARN-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526963#comment-14526963 ] Zhijie Shen commented on YARN-1564: --- YARN-2928 is going to support flow as the first

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526983#comment-14526983 ] Jason Lowe commented on YARN-3554: -- Ah, thanks [~Naganarasimha], sorry I missed that. We

[jira] [Commented] (YARN-3422) relatedentities always return empty list when primary filter is set

[ https://issues.apache.org/jira/browse/YARN-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527012#comment-14527012 ] Zhijie Shen commented on YARN-3422: --- [~billie.rina...@gmail.com], thanks for explaining

[jira] [Commented] (YARN-2618) Avoid over-allocation of disk resources

[ https://issues.apache.org/jira/browse/YARN-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527020#comment-14527020 ] Vinod Kumar Vavilapalli commented on YARN-2618: --- Haven't looked at this so

[jira] [Created] (YARN-3573) MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated

Mit Desai created YARN-3573: --- Summary: MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated Key: YARN-3573 URL: https://issues.apache.org/jira/browse/YARN-3573

[jira] [Commented] (YARN-2618) Avoid over-allocation of disk resources

[ https://issues.apache.org/jira/browse/YARN-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527035#comment-14527035 ] Vinod Kumar Vavilapalli commented on YARN-2618: --- Okay, quickly scanned. Seems

[jira] [Assigned] (YARN-3573) MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated

[ https://issues.apache.org/jira/browse/YARN-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai reassigned YARN-3573: --- Assignee: Mit Desai MiniMRYarnCluster constructor that starts the timeline server using a boolean

[jira] [Updated] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-1612: -- Attachment: YARN-1612-003.patch patch updated. FairScheduler: Enable delay scheduling by default

[jira] [Updated] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-1612: -- Attachment: (was: YARN-1612-003.patch) FairScheduler: Enable delay scheduling by default

[jira] [Updated] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-1612: -- Attachment: YARN-1612-003.patch FairScheduler: Enable delay scheduling by default

[jira] [Updated] (YARN-3573) MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated

[ https://issues.apache.org/jira/browse/YARN-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-3573: Assignee: (was: Mit Desai) MiniMRYarnCluster constructor that starts the timeline server using a

[jira] [Commented] (YARN-3480) Make AM max attempts stored in RMAppImpl and RMStateStore to be configurable

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527069#comment-14527069 ] Jian He commented on YARN-3480: --- [~hex108], generally, it's better to avoid a global config

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527072#comment-14527072 ] Vinod Kumar Vavilapalli commented on YARN-3554: --- HADOOP-11398 and YARN-3238

[jira] [Commented] (YARN-2267) Auxiliary Service support in RM

[ https://issues.apache.org/jira/browse/YARN-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527084#comment-14527084 ] Zhijie Shen commented on YARN-2267: --- Sunil, my 2 cents: if you can have some detailed

[jira] [Updated] (YARN-1621) Add CLI to list rows of task attempt ID, container ID, host of container, state of container

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Ługowski updated YARN-1621: --- Attachment: (was: YARN-1621.6.patch) Add CLI to list rows of task attempt ID, container

[jira] [Updated] (YARN-1621) Add CLI to list rows of task attempt ID, container ID, host of container, state of container

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Ługowski updated YARN-1621: --- Attachment: YARN-1621.6.patch Add CLI to list rows of task attempt ID, container ID, host of

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527087#comment-14527087 ] Vinod Kumar Vavilapalli commented on YARN-3554: --- bq. Are there still

[jira] [Updated] (YARN-3518) default rm/am expire interval should not less than default resourcemanager connect wait time

[ https://issues.apache.org/jira/browse/YARN-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3518: -- Assignee: sandflee default rm/am expire interval should not less than default

[jira] [Commented] (YARN-3518) default rm/am expire interval should not less than default resourcemanager connect wait time

[ https://issues.apache.org/jira/browse/YARN-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527100#comment-14527100 ] Vinod Kumar Vavilapalli commented on YARN-3518: --- We need to be careful here.

[jira] [Commented] (YARN-3562) unit tests failures and issues found from findbug from earlier ATS checkins

[ https://issues.apache.org/jira/browse/YARN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527614#comment-14527614 ] Naganarasimha G R commented on YARN-3562: - Thanks [~sjlee0], yes lately seeing some

[jira] [Commented] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527612#comment-14527612 ] Jian He commented on YARN-3018: --- hi [~nijel], below code in CapacitySchedulerConfiguration

[jira] [Commented] (YARN-2725) Adding test cases of retrying requests about ZKRMStateStore

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

[jira] [Commented] (YARN-3375) NodeHealthScriptRunner.shouldRun() check is performing 3 times for starting NodeHealthScriptRunner

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

[jira] [Commented] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527802#comment-14527802 ] zhihai xu commented on YARN-3491: - thanks [~wilfreds] for the review. I uploaded a new

[jira] [Updated] (YARN-3573) MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated

[ https://issues.apache.org/jira/browse/YARN-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3573: --- Attachment: YARN-3573.patch MiniMRYarnCluster constructor that starts the timeline

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527639#comment-14527639 ] Wangda Tan commented on YARN-3514: -- [~cnauroth], I think this causes other problems in

[jira] [Commented] (YARN-3343) TestCapacitySchedulerNodeLabelUpdate.testNodeUpdate sometime fails in trunk

[ https://issues.apache.org/jira/browse/YARN-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527640#comment-14527640 ] Jian He commented on YARN-3343: --- [~rohithsharma], is this still reproducible ? seems not on

[jira] [Commented] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527697#comment-14527697 ] Wangda Tan commented on YARN-3521: -- [~sunilg], Make sense to me, bq. IMO I also feel

[jira] [Updated] (YARN-3574) RM hangs on stopping MetricsSinkAdapter when transitioning to standby

[ https://issues.apache.org/jira/browse/YARN-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3574: -- Description: We've seen a situation that one RM hangs on stopping the MetricsSinkAdapter {code}

[jira] [Commented] (YARN-3574) RM hangs on stopping MetricsSinkAdapter when transitioning to standby

[ https://issues.apache.org/jira/browse/YARN-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527698#comment-14527698 ] Jian He commented on YARN-3574: --- [~brahmareddy], I'm also not able to repro.. I wondered if

[jira] [Commented] (YARN-1612) FairScheduler: Enable delay scheduling by default

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

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527835#comment-14527835 ] Hadoop QA commented on YARN-3134: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3480) Make AM max attempts stored in RMAppImpl and RMStateStore to be configurable

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527847#comment-14527847 ] Jun Gong commented on YARN-3480: [~jianhe], sorry for not specifying our scenario: RM HA is

[jira] [Commented] (YARN-2921) MockRM#waitForState methods can be too slow and flaky

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527855#comment-14527855 ] Tsuyoshi Ozawa commented on YARN-2921: -- [~leftnoteasy] thank you for pinging me. Yes,

[jira] [Commented] (YARN-3574) RM hangs on stopping MetricsSinkAdapter when transitioning to standby

[ https://issues.apache.org/jira/browse/YARN-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527616#comment-14527616 ] Brahma Reddy Battula commented on YARN-3574: [~jianhe] I would like to work on

[jira] [Assigned] (YARN-3574) RM hangs on stopping MetricsSinkAdapter when transitioning to standby

[ https://issues.apache.org/jira/browse/YARN-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula reassigned YARN-3574: -- Assignee: Brahma Reddy Battula RM hangs on stopping MetricsSinkAdapter when

[jira] [Commented] (YARN-3573) MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated

[ https://issues.apache.org/jira/browse/YARN-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527619#comment-14527619 ] Brahma Reddy Battula commented on YARN-3573: [~mitdesai] Thanks for reporting,

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Attachment: YARN-3134-YARN-2928.003.patch Updated my patch according to the latest comments. I've rebased the patch

[jira] [Commented] (YARN-3523) Cleanup ResourceManagerAdministrationProtocol interface audience

[ https://issues.apache.org/jira/browse/YARN-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527649#comment-14527649 ] Naganarasimha G R commented on YARN-3523: - in that case better to remove @Stable

[jira] [Commented] (YARN-3557) Support Intel Trusted Execution Technology(TXT) in YARN scheduler

[ https://issues.apache.org/jira/browse/YARN-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527699#comment-14527699 ] Dian Fu commented on YARN-3557: --- Hi [~leftnoteasy], Thanks a lot for your comments. What

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527702#comment-14527702 ] Vinod Kumar Vavilapalli commented on YARN-3514: --- I also doubt if this (the

[jira] [Commented] (YARN-3523) Cleanup ResourceManagerAdministrationProtocol interface audience

[ https://issues.apache.org/jira/browse/YARN-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527705#comment-14527705 ] Vinod Kumar Vavilapalli commented on YARN-3523: --- Makes sense. Cleanup

[jira] [Commented] (YARN-3562) unit tests failures and issues found from findbug from earlier ATS checkins

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

[jira] [Updated] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3491: Attachment: YARN-3491.004.patch PublicLocalizer#addResource is too slow.

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527632#comment-14527632 ] Li Lu commented on YARN-3134: - And, one more thing: I'm closing all PreparedStatements

[jira] [Commented] (YARN-3518) default rm/am expire interval should not less than default resourcemanager connect wait time

[ https://issues.apache.org/jira/browse/YARN-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527706#comment-14527706 ] sandflee commented on YARN-3518: agree, we should set nm, am, client separately default

[jira] [Commented] (YARN-3069) Document missing properties in yarn-default.xml

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

[jira] [Commented] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

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

[jira] [Commented] (YARN-3491) PublicLocalizer#addResource is too slow.

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

[jira] [Commented] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527904#comment-14527904 ] Sunil G commented on YARN-3521: --- [~leftnoteasy] Yes, Its not a valid point.

[jira] [Commented] (YARN-3573) MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated

[ https://issues.apache.org/jira/browse/YARN-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527906#comment-14527906 ] Hadoop QA commented on YARN-3573: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527907#comment-14527907 ] Chris Nauroth commented on YARN-3514: - Looking at the original description, I see

[jira] [Commented] (YARN-3560) Not able to navigate to the cluster from tracking url (proxy) generated after submission of job

[ https://issues.apache.org/jira/browse/YARN-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527917#comment-14527917 ] Mohammad Shahid Khan commented on YARN-3560: The issue is happening due to the

[jira] [Commented] (YARN-3343) TestCapacitySchedulerNodeLabelUpdate.testNodeUpdate sometime fails in trunk

[ https://issues.apache.org/jira/browse/YARN-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527929#comment-14527929 ] Rohith commented on YARN-3343: -- [~jianhe] I was able to reproduce it. When I debug this issue,

[jira] [Updated] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3491: Attachment: (was: YARN-3491.004.patch) PublicLocalizer#addResource is too slow.

[jira] [Updated] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3491: Attachment: YARN-3491.004.patch PublicLocalizer#addResource is too slow.

[jira] [Updated] (YARN-3552) RM Web UI shows -1 running containers for completed apps

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3552: - Attachment: (was: 0001-YARN-3552.patch) RM Web UI shows -1 running containers for completed apps

  1   2   >