[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

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

[jira] [Commented] (YARN-2740) Fix NodeLabelsManager to properly handle node label modifications when distributed node label configuration enabled

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

[jira] [Updated] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

[ https://issues.apache.org/jira/browse/YARN-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2619: Attachment: YARN-2619.003.patch {quote} YarnConfiguration.java There seem to be a bunch of unrelated

[jira] [Commented] (YARN-3552) RMServerUtils#DUMMY_APPLICATION_RESOURCE_USAGE_REPORT has negative numbers

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517030#comment-14517030 ] Jason Lowe commented on YARN-3552: -- I believe the negative numbers were to indicate that

[jira] [Created] (YARN-3552) RMServerUtils#DUMMY_APPLICATION_RESOURCE_USAGE_REPORT has negative numbers

Rohith created YARN-3552: Summary: RMServerUtils#DUMMY_APPLICATION_RESOURCE_USAGE_REPORT has negative numbers Key: YARN-3552 URL: https://issues.apache.org/jira/browse/YARN-3552 Project: Hadoop YARN

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

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

[jira] [Commented] (YARN-2176) CapacityScheduler loops over all running applications rather than actively requesting apps

[ https://issues.apache.org/jira/browse/YARN-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517043#comment-14517043 ] Jason Lowe commented on YARN-2176: -- It is less efficient to lump them all together. As

[jira] [Updated] (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:all-tabpanel ] Xianyin Xin updated YARN-3553: -- Description: For TreeSet, element is identified by comparator, not the object reference. If any

[jira] [Commented] (YARN-3381) A typographical error in InvalidStateTransitonException

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517068#comment-14517068 ] Tsuyoshi Ozawa commented on YARN-3381: -- [~brahmareddy] could you rebase your patch

[jira] [Commented] (YARN-3552) RMServerUtils#DUMMY_APPLICATION_RESOURCE_USAGE_REPORT has negative numbers

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517094#comment-14517094 ] Rohith commented on YARN-3552: -- I agree to the internal logic, but concern is when the

[jira] [Commented] (YARN-2176) CapacityScheduler loops over all running applications rather than actively requesting apps

[ https://issues.apache.org/jira/browse/YARN-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14516808#comment-14516808 ] Xianyin Xin commented on YARN-2176: --- Hi [~jlowe] and [~leftnoteasy], in YARN-3361, all

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14516812#comment-14516812 ] Naganarasimha G R commented on YARN-3543: - Hi [~rohithsharma] can we include in ATS

[jira] [Updated] (YARN-3539) Compatibility doc to state that ATS v1 is a stable REST API

[ https://issues.apache.org/jira/browse/YARN-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-3539: - Attachment: YARN-3539-004.patch Patch -004 this merges in YARN-1876, converting that to Markdown

[jira] [Updated] (YARN-3555) Incorrect format for the container log url returned by ContainerReport.

[ https://issues.apache.org/jira/browse/YARN-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spandan Dutta updated YARN-3555: Description: Assume that we have a ContainerReport obj cr. When we do cr.getLogUrl() on it to get

[jira] [Created] (YARN-3556) Yarn REST to submit application fails with NPE if the environment element has empty entries

Rajesh Kartha created YARN-3556: --- Summary: Yarn REST to submit application fails with NPE if the environment element has empty entries Key: YARN-3556 URL: https://issues.apache.org/jira/browse/YARN-3556

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518360#comment-14518360 ] Li Lu commented on YARN-3551: - Hi [~sjlee0]! I agree it would be nice to have more strict type

[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=14518480#comment-14518480 ] Sangjin Lee commented on YARN-3134: --- {{conn.close()}} is called again on l.222 in the

[jira] [Updated] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3044: Attachment: YARN-3044-YARN-2928.004.patch updated the patch name and resubmitting it

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518494#comment-14518494 ] Sangjin Lee commented on YARN-3551: --- I don't think those two things are mutually

[jira] [Updated] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3044: Attachment: (was: YARN-3044.20150429-1.patch) [Event producers] Implement RM writing

[jira] [Commented] (YARN-3363) add localization and container launch time to ContainerMetrics at NM to show these timing information for each active container.

[ https://issues.apache.org/jira/browse/YARN-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518538#comment-14518538 ] zhihai xu commented on YARN-3363: - It looks like the checkstyle issues are not related to

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518576#comment-14518576 ] Vinod Kumar Vavilapalli commented on YARN-2942: --- Tx for the updated docs,

[jira] [Updated] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3044: Attachment: YARN-3044.20150429-1.patch Hi [~sjlee0] [~djp], If you guys have bandwidth,

[jira] [Updated] (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:all-tabpanel ] Naganarasimha G R updated YARN-3554: Attachment: YARN-3554.20150429-1.patch Hi [~jlowe], as it was simple fix i have assigned to

[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=14518383#comment-14518383 ] Sangjin Lee commented on YARN-3134: --- Thanks for the patch [~gtCarrera9]! Some quick

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518450#comment-14518450 ] Li Lu commented on YARN-3551: - OK, I didn't say it clear enough but this is the solution I was

[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=14518559#comment-14518559 ] Hadoop QA commented on YARN-3554: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518583#comment-14518583 ] Vrushali C commented on YARN-3551: -- + 1 to the constructor and templated code above. bq.

[jira] [Created] (YARN-3555) Incorrect format for the container log url returned by ContainerReport.

Spandan Dutta created YARN-3555: --- Summary: Incorrect format for the container log url returned by ContainerReport. Key: YARN-3555 URL: https://issues.apache.org/jira/browse/YARN-3555 Project: Hadoop

[jira] [Updated] (YARN-3555) Incorrect format for the container log url returned by ContainerReport.

[ https://issues.apache.org/jira/browse/YARN-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spandan Dutta updated YARN-3555: Description: Assume that we have a ContainerReport obj cr. When we do cr.getLogUrl() to get the log

[jira] [Updated] (YARN-3555) Incorrect format for the container log url returned by ContainerReport.

[ https://issues.apache.org/jira/browse/YARN-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spandan Dutta updated YARN-3555: Description: Assume that we have a ContainerReport obj cr. When we do cr.getLogUrl() to get the log

[jira] [Assigned] (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:all-tabpanel ] Naganarasimha G R reassigned YARN-3554: --- Assignee: Naganarasimha G R Default value for maximum nodemanager connect wait time

[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=14518458#comment-14518458 ] Li Lu commented on YARN-3134: - Hi [~sjlee0], thanks for the review! We do not need to call

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518338#comment-14518338 ] Sangjin Lee commented on YARN-3551: --- Thanks for the patch [~zjshen]! How about making

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518414#comment-14518414 ] Sangjin Lee commented on YARN-3551: --- I was going to follow up. The generics alone is not

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518486#comment-14518486 ] Sangjin Lee commented on YARN-3044: --- Sorry Naga for falling back on the review. I'll take

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518569#comment-14518569 ] Vrushali C commented on YARN-3551: -- Thanks [~zjshen] for the jira and the patch. I was

[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=14518573#comment-14518573 ] Dian Fu commented on YARN-3557: --- Will post a design doc ASAP. Support Intel Trusted

[jira] [Updated] (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:all-tabpanel ] Dian Fu updated YARN-3557: -- Issue Type: New Feature (was: Bug) Support Intel Trusted Execution Technology(TXT) in YARN scheduler

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

Dian Fu created YARN-3557: - Summary: Support Intel Trusted Execution Technology(TXT) in YARN scheduler Key: YARN-3557 URL: https://issues.apache.org/jira/browse/YARN-3557 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

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

[jira] [Updated] (YARN-3556) Yarn REST to submit application fails with NPE if the environment element has empty entries

[ https://issues.apache.org/jira/browse/YARN-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Kartha updated YARN-3556: Attachment: wc-no-cp-NPE.xml Here is the XML request submitted for running Yarn REST to submit

[jira] [Updated] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2893: Attachment: YARN-2893.004.patch AMLaucher: sporadic job failures due to EOFException in

[jira] [Commented] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

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

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518575#comment-14518575 ] Vrushali C commented on YARN-3551: -- Hmm, yes, we do need a datatype per metric to be

[jira] [Commented] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

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

[jira] [Commented] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

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

[jira] [Commented] (YARN-2740) Fix NodeLabelsManager to properly handle node label modifications when distributed node label configuration enabled

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

[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

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

[jira] [Commented] (YARN-3465) Use LinkedHashMap to preserve order of resource requests

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

[jira] [Commented] (YARN-3530) ATS throws exception on trying to filter results without otherinfo.

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

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner kills localizer before localizing all resources

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

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517022#comment-14517022 ] Peng Zhang commented on YARN-3535: -- Attached patch to restore ResourceRequest for

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Updated] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3535: - Attachment: YARN-3535-001.patch ResourceRequest should be restored back to scheduler when RMContainer is

[jira] [Updated] (YARN-3552) RMServerUtils#DUMMY_APPLICATION_RESOURCE_USAGE_REPORT has negative numbers

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3552: - Attachment: yarn-3352.PNG 0001-YARN-3552.patch

[jira] [Commented] (YARN-3530) ATS throws exception on trying to filter results without otherinfo.

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

[jira] [Commented] (YARN-3465) Use LinkedHashMap to preserve order of resource requests

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

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner kills localizer before localizing all resources

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

[jira] [Commented] (YARN-3530) ATS throws exception on trying to filter results without otherinfo.

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

[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

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

[jira] [Commented] (YARN-2740) Fix NodeLabelsManager to properly handle node label modifications when distributed node label configuration enabled

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

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner kills localizer before localizing all resources

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

[jira] [Commented] (YARN-3465) Use LinkedHashMap to preserve order of resource requests

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

[jira] [Commented] (YARN-3465) Use LinkedHashMap to preserve order of resource requests

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

[jira] [Commented] (YARN-2740) Fix NodeLabelsManager to properly handle node label modifications when distributed node label configuration enabled

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

[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

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

[jira] [Commented] (YARN-3530) ATS throws exception on trying to filter results without otherinfo.

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

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner kills localizer before localizing all resources

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

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

Xianyin Xin created YARN-3553: - Summary: TreeSet is not a nice container for organizing schedulableEntities. Key: YARN-3553 URL: https://issues.apache.org/jira/browse/YARN-3553 Project: Hadoop YARN

[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: SettingupPhoenixstorageforatimelinev2end-to-endtest.pdf I just finished a simple write up to introduce

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

[ https://issues.apache.org/jira/browse/YARN-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518551#comment-14518551 ] Vinod Kumar Vavilapalli commented on YARN-2619: --- A very clean patch! This is

[jira] [Commented] (YARN-2740) Fix NodeLabelsManager to properly handle node label modifications when distributed node label configuration enabled

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

[jira] [Commented] (YARN-3530) ATS throws exception on trying to filter results without otherinfo.

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

[jira] [Commented] (YARN-3465) Use LinkedHashMap to preserve order of resource requests

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

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

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

[jira] [Commented] (YARN-3552) RMServerUtils#DUMMY_APPLICATION_RESOURCE_USAGE_REPORT has negative numbers

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517146#comment-14517146 ] Jason Lowe commented on YARN-3552: -- This also appears in the REST service, so this is an

[jira] [Commented] (YARN-3530) ATS throws exception on trying to filter results without otherinfo.

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

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner kills localizer before localizing all resources

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

[jira] [Commented] (YARN-2740) Fix NodeLabelsManager to properly handle node label modifications when distributed node label configuration enabled

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

[jira] [Commented] (YARN-3465) Use LinkedHashMap to preserve order of resource requests

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

[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

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

[jira] [Commented] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517252#comment-14517252 ] Eric Payne commented on YARN-2004: -- [~sunilg], Thanks for all of the work you are doing

[jira] [Commented] (YARN-3516) killing ContainerLocalizer action doesn't take effect when private localizer receives FETCH_FAILURE status.

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

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner kills localizer before localizing all resources

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

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517272#comment-14517272 ] Peng Zhang commented on YARN-3535: -- Sorry, I only run all tests in FairScheduler package,

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518654#comment-14518654 ] Zhijie Shen commented on YARN-3551: --- bq. Also, think along with singleData, we also need

[jira] [Updated] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2893: Attachment: (was: YARN-2893.004.patch) AMLaucher: sporadic job failures due to EOFException in

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

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

[jira] [Commented] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

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

[jira] [Resolved] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

[ https://issues.apache.org/jira/browse/YARN-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-3485. Resolution: Fixed Fix Version/s: 2.7.1 Hadoop Flags: Reviewed Committed to

[jira] [Commented] (YARN-3381) A typographical error in InvalidStateTransitonException

[ https://issues.apache.org/jira/browse/YARN-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518739#comment-14518739 ] Brahma Reddy Battula commented on YARN-3381: Can you please kick-off jenkins

[jira] [Commented] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518742#comment-14518742 ] Hadoop QA commented on YARN-2893: - (!) The patch artifact directory on has been removed!

[jira] [Updated] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

[ https://issues.apache.org/jira/browse/YARN-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3485: --- Attachment: yarn-3485-3.patch Thanks for the review, Sandy. Uploaded patch addresses the nit.

[jira] [Updated] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2893: Attachment: YARN-2893.004.patch AMLaucher: sporadic job failures due to EOFException in

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

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

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517334#comment-14517334 ] Vrushali C commented on YARN-3411: -- Hi [~djp] Thanks for the feedback! bq. Do each put

[jira] [Commented] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517310#comment-14517310 ] Sunil G commented on YARN-2004: --- Yes [~jlowe] You are correct. We cannot compare highest

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517323#comment-14517323 ] Vrushali C commented on YARN-3411: -- Hi Sangjin, Thank you for the comments! bq. I’m sure

[jira] [Commented] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517317#comment-14517317 ] Sunil G commented on YARN-2004: --- Extremely sorry [~eepayne] I mistyped your name as Jason.

  1   2   >