[jira] [Commented] (YARN-4604) TimelineDataManager should return gracefully when one entity's id or type is empty

[ https://issues.apache.org/jira/browse/YARN-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106344#comment-15106344 ] Naganarasimha G R commented on YARN-4604: - [~varun_saxena], Thanks for correcting i

[jira] [Resolved] (YARN-4604) TimelineDataManager should return gracefully when one entity's id or type is empty

[ https://issues.apache.org/jira/browse/YARN-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu resolved YARN-4604. - Resolution: Won't Fix > TimelineDataManager should return gracefully when one entity's id or type is > empty > ---

[jira] [Commented] (YARN-4604) TimelineDataManager should return gracefully when one entity's id or type is empty

[ https://issues.apache.org/jira/browse/YARN-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106342#comment-15106342 ] Li Lu commented on YARN-4604: - Yes you're right. I missed the preprocess part. Close this as wo

[jira] [Commented] (YARN-4604) TimelineDataManager should return gracefully when one entity's id or type is empty

[ https://issues.apache.org/jira/browse/YARN-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106338#comment-15106338 ] Varun Saxena commented on YARN-4604: Copying over my comment from YARN-4596. bq. It sh

[jira] [Commented] (YARN-4596) SystemMetricPublisher should not swallow error messages from TimelineClient#putEntities

[ https://issues.apache.org/jira/browse/YARN-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106332#comment-15106332 ] Varun Saxena commented on YARN-4596: [~Naganarasimha], [~gtCarrera9], Regarding below

[jira] [Commented] (YARN-4219) New levelDB cache storage for timeline v1.5

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

[jira] [Assigned] (YARN-4605) Spelling mistake in the help message of "yarn applicationattempt" command

[ https://issues.apache.org/jira/browse/YARN-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang reassigned YARN-4605: - Assignee: Weiwei Yang > Spelling mistake in the help message of "yarn applicationattempt" command

[jira] [Updated] (YARN-4605) Spelling mistake in the help message of "yarn applicationattempt" command

[ https://issues.apache.org/jira/browse/YARN-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YARN-4605: -- Attachment: YARN-4605.001.patch I do see several places having such typo, changes is trivial, just submit

[jira] [Commented] (YARN-4603) FairScheduler should mention user requested queuename in error message when failed in queue ACL check

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

[jira] [Updated] (YARN-4605) Spelling mistake in the help message of "yarn applicationattempt" command

[ https://issues.apache.org/jira/browse/YARN-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjunath Ballur updated YARN-4605: --- Description: Using YARN CLI, when the user types "yarn applicationattempt", the help message f

[jira] [Created] (YARN-4605) Spelling mistake in the help message of "yarn applicationattempt" command

Manjunath Ballur created YARN-4605: -- Summary: Spelling mistake in the help message of "yarn applicationattempt" command Key: YARN-4605 URL: https://issues.apache.org/jira/browse/YARN-4605 Project: Ha

[jira] [Commented] (YARN-4565) When sizeBasedWeight enabled for FairOrderingPolicy in CapacityScheduler, Sometimes lead to situation where all queue resources consumed by AMs only

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

[jira] [Updated] (YARN-4557) Improper Queues sorting in PartitionedQueueComparator when accessible node labels is configured as ANY

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4557: Attachment: YARN-4557.v3.002.patch Thanks for the review [~wangda], yes it was a typo, have c

[jira] [Commented] (YARN-4596) SystemMetricPublisher should not swallow error messages from TimelineClient#putEntities

[ https://issues.apache.org/jira/browse/YARN-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106248#comment-15106248 ] Naganarasimha G R commented on YARN-4596: - Thanks [~gtCarrera] for considering them

[jira] [Commented] (YARN-4596) SystemMetricPublisher should not swallow error messages from TimelineClient#putEntities

[ https://issues.apache.org/jira/browse/YARN-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106240#comment-15106240 ] Li Lu commented on YARN-4596: - I've created YARN-4604 and MAPREDUCE-6610 to trace the two probl

[jira] [Created] (YARN-4604) TimelineDataManager should return gracefully when one entity's id or type is empty

Li Lu created YARN-4604: --- Summary: TimelineDataManager should return gracefully when one entity's id or type is empty Key: YARN-4604 URL: https://issues.apache.org/jira/browse/YARN-4604 Project: Hadoop YARN

[jira] [Updated] (YARN-4380) TestResourceLocalizationService.testDownloadingResourcesOnContainerKill fails intermittently

[ https://issues.apache.org/jira/browse/YARN-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-4380: Release Note: (was: Committed this to trunk, branch-2, and branch-2.7. Thanks Varun Saxena for your

[jira] [Updated] (YARN-4219) New levelDB cache storage for timeline v1.5

[ https://issues.apache.org/jira/browse/YARN-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4219: Attachment: YARN-4219-trunk.005.patch Thanks [~xgong] for the comment! Upload a new patch to address the findbugs wa

[jira] [Updated] (YARN-3692) Allow REST API to set a user generated message when killing an application

[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3692: Target Version/s: 2.9.0 > Allow REST API to set a user generated message when killing an appl

[jira] [Commented] (YARN-4219) New levelDB cache storage for timeline v1.5

[ https://issues.apache.org/jira/browse/YARN-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106213#comment-15106213 ] Xuan Gong commented on YARN-4219: - Thanks for the patch. [~gtCarrera9]. The latest patch l

[jira] [Commented] (YARN-4559) Make leader elector and zk store share the same curator client

[ https://issues.apache.org/jira/browse/YARN-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106212#comment-15106212 ] Xuan Gong commented on YARN-4559: - The last patch looks good to me. Looks like the test c

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106204#comment-15106204 ] Wangda Tan commented on YARN-4465: -- Hi [~bibinchundatt] Thanks for working on this, some c

[jira] [Comment Edited] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106191#comment-15106191 ] Wangda Tan edited comment on YARN-3945 at 1/19/16 3:31 AM: --- bq. i

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106191#comment-15106191 ] Wangda Tan commented on YARN-3945: -- bq. i feel better not to consider userLimit and userLi

[jira] [Commented] (YARN-4557) Improper Queues sorting in PartitionedQueueComparator when accessible node labels is configured as ANY

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106186#comment-15106186 ] Wangda Tan commented on YARN-4557: -- Looks good, +1. Thanks [~Naganarasimha], One nit is:

[jira] [Updated] (YARN-4603) FairScheduler should mention user requested queuename in error message when failed in queue ACL check

[ https://issues.apache.org/jira/browse/YARN-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4603: -- Attachment: YARN-4603.001.patch > FairScheduler should mention user requested queuename in error message when >

[jira] [Created] (YARN-4603) FairScheduler should mention user requested queuename in error message when failed in queue ACL check

Tao Jie created YARN-4603: - Summary: FairScheduler should mention user requested queuename in error message when failed in queue ACL check Key: YARN-4603 URL: https://issues.apache.org/jira/browse/YARN-4603 P

[jira] [Commented] (YARN-4502) Fix two AM containers get allocated when AM restart

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

[jira] [Resolved] (YARN-4502) Fix two AM containers get allocated when AM restart

[ https://issues.apache.org/jira/browse/YARN-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-4502. -- Resolution: Fixed Thanks [~vinodkv], just reverted & committed it to branch-2/2.8/trunk. > Fix two AM co

[jira] [Commented] (YARN-4596) SystemMetricPublisher should not swallow error messages from TimelineClient#putEntities

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

[jira] [Assigned] (YARN-4597) Add SCHEDULE to NM container lifecycle

[ https://issues.apache.org/jira/browse/YARN-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-4597: - Assignee: Arun Suresh > Add SCHEDULE to NM container lifecycle > -

[jira] [Commented] (YARN-4224) Support fetching entities by UID and change the REST interface to conform to current REST APIs' in YARN

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

[jira] [Commented] (YARN-4596) SystemMetricPublisher should not swallow error messages from TimelineClient#putEntities

[ https://issues.apache.org/jira/browse/YARN-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105838#comment-15105838 ] Li Lu commented on YARN-4596: - Ah I've got your point. Yes we can definitely improve the logic

[jira] [Updated] (YARN-4224) Support fetching entities by UID and change the REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4224: --- Attachment: YARN-4224-feature-YARN-2928.04.patch > Support fetching entities by UID and change the REST

[jira] [Commented] (YARN-4219) New levelDB cache storage for timeline v1.5

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

[jira] [Commented] (YARN-4601) HA as a general YARN service to highlighted container by application.

[ https://issues.apache.org/jira/browse/YARN-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105791#comment-15105791 ] Junping Du commented on YARN-4601: -- I believe it is potentially to be critical in prospect

[jira] [Reopened] (YARN-4502) Fix two AM containers get allocated when AM restart

[ https://issues.apache.org/jira/browse/YARN-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened YARN-4502: --- [~leftnoteasy], looks like you committed the wrong patch, likely because of the wr

[jira] [Updated] (YARN-4219) New levelDB cache storage for timeline v1.5

[ https://issues.apache.org/jira/browse/YARN-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4219: Attachment: YARN-4219-trunk.004.patch Rebase the patch to latest trunk. > New levelDB cache storage for timeline v1

[jira] [Commented] (YARN-4601) HA as a general YARN service to highlighted container by application.

[ https://issues.apache.org/jira/browse/YARN-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105698#comment-15105698 ] Allen Wittenauer commented on YARN-4601: Critical priority? That's a bit surprisin

[jira] [Commented] (YARN-4599) Set OOM control for memory cgroups

[ https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105694#comment-15105694 ] Allen Wittenauer commented on YARN-4599: bq. We should also explicitly set OOM cont

[jira] [Commented] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

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

[jira] [Commented] (YARN-4557) Improper Queues sorting in PartitionedQueueComparator when accessible node labels is configured as ANY

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

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105561#comment-15105561 ] Xuan Gong commented on YARN-4577: - [~sjlee0] bq. how important is it to support non-local

[jira] [Commented] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

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

[jira] [Commented] (YARN-4545) Allow YARN distributed shell to use ATS v1.5 APIs

[ https://issues.apache.org/jira/browse/YARN-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105508#comment-15105508 ] Junping Du commented on YARN-4545: -- Thanks for uploading a patch, [~gtCarrera9]. Given YAR

[jira] [Updated] (YARN-4465) SchedulerUtils#validateRequest for Label check should happen only when nodelabel enabled

[ https://issues.apache.org/jira/browse/YARN-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4465: --- Attachment: 0001-YARN-4465.patch Hi [~sunilg]/[~leftnoteasy] Attaching patch for review. Patch

[jira] [Updated] (YARN-4600) More general services provided to application/container by YARN

[ https://issues.apache.org/jira/browse/YARN-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4600: - Assignee: (was: Junping Du) > More general services provided to application/container by YARN > ---

[jira] [Created] (YARN-4602) Message/notification service between containers

Junping Du created YARN-4602: Summary: Message/notification service between containers Key: YARN-4602 URL: https://issues.apache.org/jira/browse/YARN-4602 Project: Hadoop YARN Issue Type: Sub-tas

[jira] [Created] (YARN-4601) HA as a general YARN service to highlighted container by application.

Junping Du created YARN-4601: Summary: HA as a general YARN service to highlighted container by application. Key: YARN-4601 URL: https://issues.apache.org/jira/browse/YARN-4601 Project: Hadoop YARN

[jira] [Assigned] (YARN-4600) More general services provided to application/container by YARN

[ https://issues.apache.org/jira/browse/YARN-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-4600: Assignee: Junping Du > More general services provided to application/container by YARN > ---

[jira] [Created] (YARN-4600) More general services provided to application/container by YARN

Junping Du created YARN-4600: Summary: More general services provided to application/container by YARN Key: YARN-4600 URL: https://issues.apache.org/jira/browse/YARN-4600 Project: Hadoop YARN Is

[jira] [Updated] (YARN-4598) Invalid event: RESOURCE_FAILED at CONTAINER_CLEANEDUP_AFTER_KILL

[ https://issues.apache.org/jira/browse/YARN-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4598: --- Attachment: YARN-4598.1.patch I submitted a patch > Invalid event: RESOURCE_FAILED at CONTAINER_CLEANE

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

[ https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105410#comment-15105410 ] Naganarasimha G R commented on YARN-4183: - Hi [~sjlee0], Any updates/reviews for th

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

[ https://issues.apache.org/jira/browse/YARN-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105408#comment-15105408 ] Naganarasimha G R commented on YARN-4307: - Hi [~vvasudev], if you some cycles can y

[jira] [Updated] (YARN-4557) Improper Queues sorting in PartitionedQueueComparator when accessible node labels is configured as ANY

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4557: Attachment: YARN-4557.v3.001.patch Hi [~wangda], Have removed modifications for bq. When ap

[jira] [Updated] (YARN-4557) Improper Queues sorting in PartitionedQueueComparator when accessible node labels is configured as ANY

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4557: Summary: Improper Queues sorting in PartitionedQueueComparator when accessible node labels is

[jira] [Updated] (YARN-4557) Few issues in scheduling with Node Labels

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4557: Description: * When queue has * as accessibility, then the queue ordering was not happening

[jira] [Updated] (YARN-4557) Few issues in scheduling with Node Labels

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4557: Description: * When queue has * as accessibility, then the queue ordering was not happening

[jira] [Updated] (YARN-4557) Few issues in scheduling with Node Labels

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4557: Description: * When queue has * as accessibility, then the queue ordering was not happening

[jira] [Updated] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3215: Attachment: YARN-3215.v2.001.patch Hi [~wangda], Have done following modifications from the p

[jira] [Commented] (YARN-4598) Invalid event: RESOURCE_FAILED at CONTAINER_CLEANEDUP_AFTER_KILL

[ https://issues.apache.org/jira/browse/YARN-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105369#comment-15105369 ] tangshangwen commented on YARN-4598: I think we should add a transition , have any Sugg

[jira] [Commented] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105238#comment-15105238 ] Junping Du commented on YARN-4265: -- It is weird that my build on branch-2/branch-2.8 local

[jira] [Commented] (YARN-4502) Fix two AM containers get allocated when AM restart

[ https://issues.apache.org/jira/browse/YARN-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105191#comment-15105191 ] Rohith Sharma K S commented on YARN-4502: - branch-2/branch-2.8 was broken by YARN-4

[jira] [Commented] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105166#comment-15105166 ] Rohith Sharma K S commented on YARN-4265: - Committed addendum patch to branch-2 and

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

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

[jira] [Updated] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4265: Attachment: YANR-4265-branch-2.8-addendum.patch YARN-4265-branch-2-addendum.pa

[jira] [Commented] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105094#comment-15105094 ] Rohith Sharma K S commented on YARN-4265: - The same issue is there in branch-2 also

[jira] [Commented] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105089#comment-15105089 ] Rohith Sharma K S commented on YARN-4265: - I found the issue, failure is because ne

[jira] [Updated] (YARN-4599) Set OOM control for memory cgroups

[ https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4599: --- Affects Version/s: 2.9.0 > Set OOM control for memory cgroups > ---

[jira] [Updated] (YARN-4599) Set OOM control for memory cgroups

[ https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4599: --- Description: YARN-1856 adds memory cgroups enforcing support. We should also explicitly set OOM

[jira] [Created] (YARN-4599) Set OOM control for memory cgroups

Karthik Kambatla created YARN-4599: -- Summary: Set OOM control for memory cgroups Key: YARN-4599 URL: https://issues.apache.org/jira/browse/YARN-4599 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4526) Make SystemClock singleton so AppSchedulingInfo could use it

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

[jira] [Commented] (YARN-4502) Fix two AM containers get allocated when AM restart

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

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

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

[jira] [Updated] (YARN-4502) Fix two AM containers get allocated when AM restart

[ https://issues.apache.org/jira/browse/YARN-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4502: - Fix Version/s: (was: 2.9.0) 2.8.0 > Fix two AM containers get allocated when AM rest

[jira] [Updated] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2885: -- Attachment: YARN-2885-yarn-2877.v6.patch Thanks for the comments [~kishorch] and [~giovanni.fumarola]. I

[jira] [Updated] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4524: - Fix Version/s: (was: 2.9.0) 2.8.0 > Cleanup AppSchedulingInfo >

[jira] [Commented] (YARN-4502) Fix two AM containers get allocated when AM restart

[ https://issues.apache.org/jira/browse/YARN-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104966#comment-15104966 ] Wangda Tan commented on YARN-4502: -- [~kasha], Thanks for reply, I tried to compile branch

[jira] [Commented] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104958#comment-15104958 ] Karthik Kambatla commented on YARN-4265: This seems to break branch-2.8 compilation

[jira] [Commented] (YARN-4526) Make SystemClock singleton so AppSchedulingInfo could use it

[ https://issues.apache.org/jira/browse/YARN-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104956#comment-15104956 ] Karthik Kambatla commented on YARN-4526: Will check this in soon, based on Arun's +

[jira] [Commented] (YARN-4526) Make SystemClock singleton so AppSchedulingInfo could use it

[ https://issues.apache.org/jira/browse/YARN-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104955#comment-15104955 ] Karthik Kambatla commented on YARN-4526: The test failures seem unrelated, and the

[jira] [Commented] (YARN-4597) Add SCHEDULE to NM container lifecycle

[ https://issues.apache.org/jira/browse/YARN-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104950#comment-15104950 ] Karthik Kambatla commented on YARN-4597: Makes a lot of sense. Thanks for filing th

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104930#comment-15104930 ] Bibin A Chundatt commented on YARN-4584: [~rohithsharma] # Attached patch after upd

[jira] [Updated] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4584: --- Attachment: 0003-YARN-4584.patch > RM startup failure when AM attempts greater than max-attempt

[jira] [Commented] (YARN-4502) Fix two AM containers get allocated when AM restart

[ https://issues.apache.org/jira/browse/YARN-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104925#comment-15104925 ] Karthik Kambatla commented on YARN-4502: I tried backporting YARN-4524 to branch-2.

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

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