[jira] [Updated] (YARN-1696) Document RM HA

[ https://issues.apache.org/jira/browse/YARN-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1696: Target Version/s: 2.4.1 (was: 2.4.0) Document RM HA -- Key:

[jira] [Commented] (YARN-1696) Document RM HA

[ https://issues.apache.org/jira/browse/YARN-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955015#comment-13955015 ] Arun C Murthy commented on YARN-1696: - [~kasha] - I'm almost done with rc0, moving this

[jira] [Updated] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1879: - Attachment: YARN-1879.1.patch Mark Idempotent/AtMostOnce annotations to

[jira] [Commented] (YARN-1893) Make ApplicationMasterProtocol#allocate AtMostOnce

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

[jira] [Commented] (YARN-1893) Make ApplicationMasterProtocol#allocate AtMostOnce

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

[jira] [Commented] (YARN-1696) Document RM HA

[ https://issues.apache.org/jira/browse/YARN-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955331#comment-13955331 ] Karthik Kambatla commented on YARN-1696: [~acmurthy] - sorry, I was not checking

[jira] [Resolved] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

[ https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong resolved YARN-808. Resolution: Won't Fix Close this ticket as won't fix. Because we already have apis/cli to get

[jira] [Commented] (YARN-1763) Handle RM failovers during the submitApplication call.

[ https://issues.apache.org/jira/browse/YARN-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955426#comment-13955426 ] Xuan Gong commented on YARN-1763: - already fixed with YARN-1521 Handle RM failovers

[jira] [Commented] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

[ https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955438#comment-13955438 ] Bikas Saha commented on YARN-808: - We should atleast change the app report response to

[jira] [Assigned] (YARN-1892) Excessive logging in RM

[ https://issues.apache.org/jira/browse/YARN-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-1892: - Assignee: Jian He Excessive logging in RM --- Key: YARN-1892

[jira] [Updated] (YARN-1892) Excessive logging in RM

[ https://issues.apache.org/jira/browse/YARN-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1892: -- Attachment: YARN-1892.1.patch Simple patch to clean some CS loggings. These logs will become more excessive if

[jira] [Updated] (YARN-1870) FileInputStream is not closed in ProcfsBasedProcessTree#constructProcessSMAPInfo()

[ https://issues.apache.org/jira/browse/YARN-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-1870: -- Assignee: Fengdong Yu FileInputStream is not closed in

[jira] [Commented] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

[ https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955513#comment-13955513 ] Zhijie Shen commented on YARN-808: -- IMHO, it's a different issue. The N/A string is not

[jira] [Commented] (YARN-1892) Excessive logging in RM

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

[jira] [Updated] (YARN-221) NM should provide a way for AM to tell it not to aggregate logs.

[ https://issues.apache.org/jira/browse/YARN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated YARN-221: - Attachment: YARN-221-trunk-v2.patch Here is the patch to support log aggregation sampling at yarn layer. Yarn

[jira] [Commented] (YARN-85) Allow per job log aggregation configuration

[ https://issues.apache.org/jira/browse/YARN-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955601#comment-13955601 ] Ming Ma commented on YARN-85: - Regarding Seth's comment of container exit status is not

[jira] [Commented] (YARN-221) NM should provide a way for AM to tell it not to aggregate logs.

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

[jira] [Commented] (YARN-1889) avoid creating new objects on each fair scheduler call to AppSchedulable comparator

[ https://issues.apache.org/jira/browse/YARN-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955762#comment-13955762 ] Sandy Ryza commented on YARN-1889: -- +1 avoid creating new objects on each fair scheduler

[jira] [Updated] (YARN-1889) avoid creating new objects on each fair scheduler call to AppSchedulable comparator

[ https://issues.apache.org/jira/browse/YARN-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1889: - Assignee: Hong Zhiguo avoid creating new objects on each fair scheduler call to AppSchedulable

[jira] [Updated] (YARN-1889) avoid creating new objects on each fair scheduler call to AppSchedulable comparator

[ https://issues.apache.org/jira/browse/YARN-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1889: - Description: In fair scheduler, in each scheduling attempt, a full sort is performed on List of

[jira] [Commented] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955817#comment-13955817 ] Tsuyoshi OZAWA commented on YARN-1879: -- I'm adding RetryCache support and tests to

[jira] [Resolved] (YARN-904) Enable multiple QOP for ResourceManager

[ https://issues.apache.org/jira/browse/YARN-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony resolved YARN-904. --- Resolution: Duplicate resolved via HDFS_5910 and HADOOP-10221 Enable multiple QOP for

[jira] [Commented] (YARN-1889) In Fair Scheduler, avoid creating objects on each call to AppSchedulable comparator

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

[jira] [Commented] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955925#comment-13955925 ] Jian He commented on YARN-1879: --- +1 with the RetryCache approach Mark Idempotent/AtMostOnce

[jira] [Created] (YARN-1896) For FairScheduler expose MinimumQueueResource of each queu in QueueMetrics

Siqi Li created YARN-1896: - Summary: For FairScheduler expose MinimumQueueResource of each queu in QueueMetrics Key: YARN-1896 URL: https://issues.apache.org/jira/browse/YARN-1896 Project: Hadoop YARN

[jira] [Updated] (YARN-1896) For FairScheduler expose MinimumQueueResource of each queu in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1896: -- Attachment: YARN-1896.v1.patch For FairScheduler expose MinimumQueueResource of each queu in QueueMetrics

[jira] [Commented] (YARN-1896) For FairScheduler expose MinimumQueueResource of each queu in QueueMetrics

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

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955960#comment-13955960 ] Sandy Ryza commented on YARN-596: - Thanks. The patch is looking almost done. I like that

[jira] [Created] (YARN-1897) Define SignalContainerRequest and SignalContainerResponse

Ming Ma created YARN-1897: - Summary: Define SignalContainerRequest and SignalContainerResponse Key: YARN-1897 URL: https://issues.apache.org/jira/browse/YARN-1897 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1726: -- Attachment: YARN-1726.patch A new patch: (1) Fix the problem because of the AbstractYarnScheduler. (2) Add

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

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

[jira] [Commented] (YARN-1872) TestDistributedShell occasionally fails in trunk

[ https://issues.apache.org/jira/browse/YARN-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13956122#comment-13956122 ] Hong Zhiguo commented on YARN-1872: --- I met the timeout too. But I can't reproduce it.