[jira] [Assigned] (YARN-261) Ability to kill AM attempts

[ https://issues.apache.org/jira/browse/YARN-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-261: -- Assignee: Rohith Sharma K S > Ability to kill AM attempts > ---

[jira] [Commented] (YARN-261) Ability to kill AM attempts

[ https://issues.apache.org/jira/browse/YARN-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731837#comment-14731837 ] Rohith Sharma K S commented on YARN-261: Thanks [~aklochkov] for information.. :-) > Ability to

[jira] [Commented] (YARN-4091) Improvement: Introduce more debug/diagnostics information to detail out scheduler activity

[ https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731875#comment-14731875 ] Sunil G commented on YARN-4091: --- Thank you [~leftnoteasy] for the detailed information shared. From your

[jira] [Commented] (YARN-3367) Replace starting a separate thread for post entity with event loop in TimelineClient

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

[jira] [Updated] (YARN-3367) Replace starting a separate thread for post entity with event loop in TimelineClient

[ https://issues.apache.org/jira/browse/YARN-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3367: Attachment: YARN-3367.YARN-2928.001.patch Uploading an initial patch with no test case for

[jira] [Commented] (YARN-4107) Both RM becomes Active if all zookeepers can not connect to active RM

[ https://issues.apache.org/jira/browse/YARN-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732143#comment-14732143 ] Karthik Kambatla commented on YARN-4107: If it fails to connect to ZK, the fencing thread should

[jira] [Commented] (YARN-4113) RM should respect retry-interval when uses RetryPolicies.RETRY_FOREVER

[ https://issues.apache.org/jira/browse/YARN-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732144#comment-14732144 ] Karthik Kambatla commented on YARN-4113: Good catch. Do we have a common JIRA to track the updates

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

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3591: --- Summary: Resource localization on a bad disk causes subsequent containers failure (was:

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732176#comment-14732176 ] He Tianyi commented on YARN-2005: - Hi, I've seen AM failures due to java dependency problem or misinput of

[jira] [Created] (YARN-4119) Expose the NM bind address as an env, so that AM can make use of it for exposing tracking URL

Naganarasimha G R created YARN-4119: --- Summary: Expose the NM bind address as an env, so that AM can make use of it for exposing tracking URL Key: YARN-4119 URL: https://issues.apache.org/jira/browse/YARN-4119