[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

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

[jira] [Commented] (YARN-3579) CommonNodeLabelsManager should support NodeLabel instead of string label name when getting node-to-label/label-to-label mappings

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

[jira] [Updated] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

[ https://issues.apache.org/jira/browse/YARN-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3457: - Fix Version/s: (was: 2.8.0) 2.7.1 I pulled this into branch-2.7 as well. NPE when

[jira] [Updated] (YARN-3537) NPE when NodeManager.serviceInit fails and stopRecoveryStore invoked

[ https://issues.apache.org/jira/browse/YARN-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3537: - Description: 2015-04-23 19:30:34,961 INFO [main] service.AbstractService

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542559#comment-14542559 ] Craig Welch commented on YARN-3626: --- Checkstyle looks unimportant, everything else OK

[jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI

[ https://issues.apache.org/jira/browse/YARN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542570#comment-14542570 ] Wangda Tan commented on YARN-3362: -- [~Naganarasimha], Thanks for pointing YARN-3638, I

[jira] [Commented] (YARN-2921) Fix MockRM/MockAM#waitForState sleep too long

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

[jira] [Updated] (YARN-3541) Add version info on timeline service / generic history web UI and RES API

[ https://issues.apache.org/jira/browse/YARN-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3541: -- Attachment: YARN-3541.2.patch Addressed Steve comments including moving TimelineAbout to API and marked

[jira] [Updated] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3638: --- Component/s: (was: yarn) (was: scheduler) (was:

[jira] [Commented] (YARN-3306) [Umbrella] Proposing per-queue Policy driven scheduling in YARN

[ https://issues.apache.org/jira/browse/YARN-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542746#comment-14542746 ] Craig Welch commented on YARN-3306: --- I don't think it's really necessary at this point,

[jira] [Commented] (YARN-3625) RollingLevelDBTimelineStore Incorrectly Forbids Related Entity in Same Put

[ https://issues.apache.org/jira/browse/YARN-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542582#comment-14542582 ] Zhijie Shen commented on YARN-3625: --- bq. To handle this scenario, I relax the domain

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542692#comment-14542692 ] Karthik Kambatla commented on YARN-3630: Sounds like a reasonable idea. YARN

[jira] [Commented] (YARN-3306) [Umbrella] Proposing per-queue Policy driven scheduling in YARN

[ https://issues.apache.org/jira/browse/YARN-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542718#comment-14542718 ] Karthik Kambatla commented on YARN-3306: As I was asking earlier, can we work on a

[jira] [Updated] (YARN-2408) Resource Request REST API for YARN

[ https://issues.apache.org/jira/browse/YARN-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renan DelValle updated YARN-2408: - Attachment: YARN-2408-6.patch Fixing problems to be able to take advantage of Jenkins Resource

[jira] [Commented] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542771#comment-14542771 ] Wangda Tan commented on YARN-1197: -- I agree to what [~kasha] mentioned, increasing Xmx

[jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI

[ https://issues.apache.org/jira/browse/YARN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542574#comment-14542574 ] Wangda Tan commented on YARN-3362: -- Last call for comments, as I'm planning to commit

[jira] [Commented] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542587#comment-14542587 ] Jason Lowe commented on YARN-3638: -- Ah, got it. I originally thought the complaint was

[jira] [Commented] (YARN-3579) getLabelsToNodes in CommonNodeLabelsManager should support NodeLabel instead of label name as String

[ https://issues.apache.org/jira/browse/YARN-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542633#comment-14542633 ] Wangda Tan commented on YARN-3579: -- [~sunilg], Thanks for updating, latest patch LGTM,

[jira] [Updated] (YARN-2408) Resource Request REST API for YARN

[ https://issues.apache.org/jira/browse/YARN-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renan DelValle updated YARN-2408: - Attachment: (was: YARN-2408-5.patch) Resource Request REST API for YARN

[jira] [Commented] (YARN-3541) Add version info on timeline service / generic history web UI and RES API

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

[jira] [Commented] (YARN-3625) RollingLevelDBTimelineStore Incorrectly Forbids Related Entity in Same Put

[ https://issues.apache.org/jira/browse/YARN-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542444#comment-14542444 ] Jonathan Eagles commented on YARN-3625: --- Do have any more thoughts on this [~zjshen]?

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542447#comment-14542447 ] Jason Lowe commented on YARN-3641: -- +1 for the patch. Will commit this later today, and

[jira] [Commented] (YARN-3489) RMServerUtils.validateResourceRequests should only obtain queue info once

[ https://issues.apache.org/jira/browse/YARN-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542586#comment-14542586 ] Wangda Tan commented on YARN-3489: -- [~varun_saxena], patch doesn't apply to latest

[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=14542592#comment-14542592 ] Wangda Tan commented on YARN-2921: -- Thanks for explanation, [~ozawa]. Latest patch LGTM,

[jira] [Commented] (YARN-3537) NPE when NodeManager.serviceInit fails and stopRecoveryStore invoked

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

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

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

[jira] [Commented] (YARN-3306) [Umbrella] Proposing per-queue Policy driven scheduling in YARN

[ https://issues.apache.org/jira/browse/YARN-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542755#comment-14542755 ] Karthik Kambatla commented on YARN-3306: The branch is not only to avoid

[jira] [Commented] (YARN-3170) YARN architecture document needs updating

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

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542929#comment-14542929 ] Rohit Agarwal commented on YARN-3633: - Actually, I like the idea of not enforcing the

[jira] [Updated] (YARN-3170) YARN architecture document needs updating

[ https://issues.apache.org/jira/browse/YARN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3170: --- Attachment: YARN-3170-007.patch YARN architecture document needs updating

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542855#comment-14542855 ] Karthik Kambatla commented on YARN-3633: Thanks for reporting this, Rohit.

[jira] [Commented] (YARN-3585) Nodemanager cannot exit when decommission with NM recovery enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542858#comment-14542858 ] Rohith commented on YARN-3585: -- I am able to reproduce it always, testing of any patch I will

[jira] [Commented] (YARN-3585) Nodemanager cannot exit when decommission with NM recovery enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542857#comment-14542857 ] Rohith commented on YARN-3585: -- bq. Could you check the NM logs for the case where it hung and

[jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI

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

[jira] [Commented] (YARN-3170) YARN architecture document needs updating

[ https://issues.apache.org/jira/browse/YARN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542842#comment-14542842 ] Brahma Reddy Battula commented on YARN-3170: [~aw] thanks for review..Updated

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542897#comment-14542897 ] Sandy Ryza commented on YARN-3633: -- Another thought is that we could say the max AM share

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

[jira] [Updated] (YARN-1519) check if sysconf is implemented before using it

[ https://issues.apache.org/jira/browse/YARN-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-1519: - Attachment: YARN-1519.003.patch [~hsn], since I didn't hear back, I will go ahead and post the patch with

[jira] [Commented] (YARN-2408) Resource Request REST API for YARN

[ https://issues.apache.org/jira/browse/YARN-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542804#comment-14542804 ] Wangda Tan commented on YARN-2408: -- [~rdelvalle], Thanks for updating, I took at look at

[jira] [Commented] (YARN-3306) [Umbrella] Proposing per-queue Policy driven scheduling in YARN

[ https://issues.apache.org/jira/browse/YARN-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542829#comment-14542829 ] Craig Welch commented on YARN-3306: --- bq. Integration points being narrow is probably more

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542895#comment-14542895 ] Rohit Agarwal commented on YARN-3633: - Can you elaborate the scenario where the AMs

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542902#comment-14542902 ] Rohit Agarwal commented on YARN-3633: - [~sandyr] If we do that and have no cluster-wide

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-3411: - Attachment: YARN-3411.poc.7.txt Attaching v7 patch. Addresses the review suggestions and includes the

[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=14542950#comment-14542950 ] Sangjin Lee commented on YARN-3411: --- [~vrushalic], could you ensure the patch applies

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

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

[jira] [Updated] (YARN-3585) NodeManager cannot exit on SHUTDOWN event triggered and NM recovery is enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3585: - Summary: NodeManager cannot exit on SHUTDOWN event triggered and NM recovery is enabled (was: Nodemanager cannot

[jira] [Commented] (YARN-3616) determine how to generate YARN container events

[ https://issues.apache.org/jira/browse/YARN-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542900#comment-14542900 ] Sangjin Lee commented on YARN-3616: --- Yes, I agree that we should emit some events from RM

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-3411: - Attachment: YARN-3411.poc.7.txt Re-attaching patch to submit [Storage implementation] explore the native

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-3411: - Attachment: (was: YARN-3411.poc.7.txt) [Storage implementation] explore the native HBase write schema

[jira] [Updated] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-3642: - Description: There is an issue with Hadoop 2.7.0 when in distributed operation the datanode is

[jira] [Commented] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

[ https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542086#comment-14542086 ] Chang Li commented on YARN-2421: The check style is not related to my change. [~jlowe]

[jira] [Commented] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14542158#comment-14542158 ] Hudson commented on YARN-3539: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2142 (See

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

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

[jira] [Commented] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542171#comment-14542171 ] Hari Sekhon commented on YARN-3638: --- Sorry the wording of these fields is sub-optimal, I

[jira] [Commented] (YARN-3634) TestMRTimelineEventHandling and TestApplication are broken

[ https://issues.apache.org/jira/browse/YARN-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542177#comment-14542177 ] Sangjin Lee commented on YARN-3634: --- Thanks for the feedback [~djp]! Actually

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542192#comment-14542192 ] Devaraj K commented on YARN-41: --- Thanks Vinod, Junping and Jason for the discussion here. bq.

[jira] [Commented] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542105#comment-14542105 ] Allen Wittenauer commented on YARN-3639: bq. on the same node I don't see what

[jira] [Commented] (YARN-3170) YARN architecture document needs updating

[ https://issues.apache.org/jira/browse/YARN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542132#comment-14542132 ] Allen Wittenauer commented on YARN-3170: {code} split up the two major

[jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI

[ https://issues.apache.org/jira/browse/YARN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542151#comment-14542151 ] Naganarasimha G R commented on YARN-3362: - Thanks for the comment [~Wangda], This

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14542113#comment-14542113 ] Hudson commented on YARN-3539: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #194 (See

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

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

[jira] [Commented] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

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

[jira] [Updated] (YARN-3628) ContainerMetrics should support always-flush mode.

[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Description: ContainerMetrics should support always-flush mode. It will be good to set ContainerMetrics as

[jira] [Commented] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543040#comment-14543040 ] Xianyin Xin commented on YARN-3639: --- Sorry [~aw], i didn't make it clearly. On the same

[jira] [Updated] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3583: -- Issue Type: Sub-task (was: Bug) Parent: YARN-2492 Support of NodeLabel object instead of plain String

[jira] [Updated] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3635: - Attachment: YARN-3635.2.patch Fixed test failure (ver.2) Get-queue-mapping should be a common interface

[jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI

[ https://issues.apache.org/jira/browse/YARN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543009#comment-14543009 ] Naganarasimha G R commented on YARN-3362: - Thanks for reviewing and committing the

[jira] [Commented] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543053#comment-14543053 ] Xianyin Xin commented on YARN-3639: --- Maybe we can fix this problem in the following way:

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543071#comment-14543071 ] Xianyin Xin commented on YARN-3630: --- Thanks [~kasha] and [~leftnoteasy]. Indeed the

[jira] [Updated] (YARN-3609) Move load labels from storage from serviceInit to serviceStart to make it works with RM HA case.

[ https://issues.apache.org/jira/browse/YARN-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3609: - Attachment: YARN-3609.1.preliminary.patch Uploaded ver.1 preliminary patch to see how much tests it

[jira] [Updated] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-3639: -- Attachment: YARN-3639-recovery_log_1_app.txt Attach recovery log for 1 app. In the log, there's a

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

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543066#comment-14543066 ] Sunil G commented on YARN-3521: --- Thank you [~wangda] for committing the patch and thank you

[jira] [Commented] (YARN-3579) CommonNodeLabelsManager should support NodeLabel instead of string label name when getting node-to-label/label-to-label mappings

[ https://issues.apache.org/jira/browse/YARN-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543064#comment-14543064 ] Sunil G commented on YARN-3579: --- Thank You very much [~leftnoteasy] for reviewing and

[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

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

[jira] [Commented] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543082#comment-14543082 ] Allen Wittenauer commented on YARN-3639: bq. On the same node means the original

[jira] [Commented] (YARN-2238) filtering on UI sticks even if I move away from the page

[ https://issues.apache.org/jira/browse/YARN-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543143#comment-14543143 ] Naganarasimha G R commented on YARN-2238: - Same problems still exist in trunk,

[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=14542980#comment-14542980 ] Sangjin Lee commented on YARN-3411: --- Here is some quick initial feedback:

[jira] [Commented] (YARN-3628) ContainerMetrics should support always-flush mode.

[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542988#comment-14542988 ] zhihai xu commented on YARN-3628: - Sorry for the confusion. It is jmx. The following is

[jira] [Commented] (YARN-3609) Move load labels from storage from serviceInit to serviceStart to make it works with RM HA case.

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

[jira] [Commented] (YARN-2921) Fix MockRM/MockAM#waitForState sleep too long

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543080#comment-14543080 ] Tsuyoshi Ozawa commented on YARN-2921: -- Thanks for your review and comments, Wangda

[jira] [Commented] (YARN-2921) Fix MockRM/MockAM#waitForState sleep too long

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543077#comment-14543077 ] Tsuyoshi Ozawa commented on YARN-2921: -- Yeah, TestRMRestart speeded up about 30

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543236#comment-14543236 ] Tsuyoshi Ozawa commented on YARN-2336: -- I'd like to review it. Please ping me after

[jira] [Assigned] (YARN-3601) Fix UT TestRMFailover.testRMWebAppRedirect

[ https://issues.apache.org/jira/browse/YARN-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang reassigned YARN-3601: - Assignee: Weiwei Yang Fix UT TestRMFailover.testRMWebAppRedirect

[jira] [Commented] (YARN-2821) Distributed shell app master becomes unresponsive sometimes

[ https://issues.apache.org/jira/browse/YARN-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543206#comment-14543206 ] Jian He commented on YARN-2821: --- The current patch makes sense because there's no way to

[jira] [Commented] (YARN-3170) YARN architecture document needs updating

[ https://issues.apache.org/jira/browse/YARN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543243#comment-14543243 ] Tsuyoshi Ozawa commented on YARN-3170: -- One additional comment from me: {quote} This

[jira] [Created] (YARN-3644) Node manager shuts down if unable to connect with RM

Srikanth Sundarrajan created YARN-3644: -- Summary: Node manager shuts down if unable to connect with RM Key: YARN-3644 URL: https://issues.apache.org/jira/browse/YARN-3644 Project: Hadoop YARN

[jira] [Updated] (YARN-3634) TestMRTimelineEventHandling and TestApplication are broken

[ https://issues.apache.org/jira/browse/YARN-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-3634: -- Attachment: YARN-3634-YARN-2928.004.patch Patch v.4 posted. Yes, you're right. I missed that second

[jira] [Commented] (YARN-3611) Support Docker Containers In LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542235#comment-14542235 ] Abin Shahab commented on YARN-3611: --- I agree with [~vinodkv]. Both Jiras have the same

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542291#comment-14542291 ] Lavkesh Lahngir commented on YARN-3591: --- [~vvasudev] Thanks for the review: This is a

[jira] [Commented] (YARN-3634) TestMRTimelineEventHandling and TestApplication are broken

[ https://issues.apache.org/jira/browse/YARN-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542271#comment-14542271 ] Junping Du commented on YARN-3634: -- Thanks [~sjlee0] for updating the patch! Latest patch

[jira] [Commented] (YARN-2221) WebUI: RM scheduler page's queue filter status will affect appllication page

[ https://issues.apache.org/jira/browse/YARN-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542206#comment-14542206 ] Xuan Gong commented on YARN-2221: - Link https://issues.apache.org/jira/browse/YARN-2238, i

[jira] [Commented] (YARN-3634) TestMRTimelineEventHandling and TestApplication are broken

[ https://issues.apache.org/jira/browse/YARN-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542217#comment-14542217 ] Junping Du commented on YARN-3634: -- bq. The initialization of the NMCollectorService RPC

[jira] [Updated] (YARN-3541) Add version info on timeline service / generic history web UI and RES API

[ https://issues.apache.org/jira/browse/YARN-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3541: -- Labels: (was: BB2015-05-TBR) Add version info on timeline service / generic history web UI and RES

[jira] [Updated] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3505: - Target Version/s: 2.7.1 (was: 2.8.0) Node's Log Aggregation Report with SUCCEED should not cached in

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542139#comment-14542139 ] Junping Du commented on YARN-41: bq. I think avoiding the unregister during shutdown if the

[jira] [Updated] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3051: --- Attachment: YARN-3051.wip.02.YARN-2928.patch [Storage abstraction] Create backing storage read

[jira] [Commented] (YARN-3634) TestMRTimelineEventHandling and TestApplication are broken

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

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542347#comment-14542347 ] zhihai xu commented on YARN-3591: - [~vvasudev], that is a good suggestion, which will give

[jira] [Updated] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3635: - Attachment: YARN-3635.1.patch Attached ver.1 patch. With changes of RMAppManager, added interface in

<    1   2   3   >