[jira] [Created] (YARN-1155) RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips

yeshavora created YARN-1155: --- Summary: RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips Key: YARN-1155 URL: https://issues.apache.org/jira/browse/YARN-1155

[jira] [Created] (YARN-1154) RM should check do reverse lookup of NM hostname on registration and disallow registration if lookup fails

yeshavora created YARN-1154: --- Summary: RM should check do reverse lookup of NM hostname on registration and disallow registration if lookup fails Key: YARN-1154 URL: https://issues.apache.org/jira/browse/YARN-1154

[jira] [Updated] (YARN-1154) RM should check do reverse lookup of NM hostname on registration and disallow registration if lookup fails

[ https://issues.apache.org/jira/browse/YARN-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshavora updated YARN-1154: Description: RM should be able to do reverse lookup when NM tries to register. NM registration should fail

[jira] [Updated] (YARN-1155) RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips

[ https://issues.apache.org/jira/browse/YARN-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshavora updated YARN-1155: Description: RM should be able to support both hostnames and ips RM should resolve hostnames/ips in

[jira] [Updated] (YARN-1155) RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips

[ https://issues.apache.org/jira/browse/YARN-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshavora updated YARN-1155: Description: RM should be able to resolve both ips and host names from include and exclude files. (was:

[jira] [Updated] (YARN-1154) RM should check do reverse lookup of NM hostname on registration and disallow registration if lookup fails

[ https://issues.apache.org/jira/browse/YARN-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshavora updated YARN-1154: Description: While new nodemanager is being added (adding nodename in yarn include file), RM should be able

[jira] [Created] (YARN-1129) Job hungs when any node is blacklisted after RMrestart

yeshavora created YARN-1129: --- Summary: Job hungs when any node is blacklisted after RMrestart Key: YARN-1129 URL: https://issues.apache.org/jira/browse/YARN-1129 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

[ https://issues.apache.org/jira/browse/YARN-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13753992#comment-13753992 ] yeshavora commented on YARN-1057: - Hitesh, the usecase will be when invalid hosts are added

[jira] [Created] (YARN-1090) Job does not get into Pending State

yeshavora created YARN-1090: --- Summary: Job does not get into Pending State Key: YARN-1090 URL: https://issues.apache.org/jira/browse/YARN-1090 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-1086) reducer of sort job restarts from scratch in between after RM restart

yeshavora created YARN-1086: --- Summary: reducer of sort job restarts from scratch in between after RM restart Key: YARN-1086 URL: https://issues.apache.org/jira/browse/YARN-1086 Project: Hadoop YARN

[jira] [Created] (YARN-1087) Succeed job tries to restart after RMrestart

yeshavora created YARN-1087: --- Summary: Succeed job tries to restart after RMrestart Key: YARN-1087 URL: https://issues.apache.org/jira/browse/YARN-1087 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-1083) ResourceManager should fail when yarn.nm.liveness-monitor.expiry-interval-ms is set less than heartbeat interval

yeshavora created YARN-1083: --- Summary: ResourceManager should fail when yarn.nm.liveness-monitor.expiry-interval-ms is set less than heartbeat interval Key: YARN-1083 URL:

[jira] [Updated] (YARN-1083) ResourceManager should fail when yarn.nm.liveness-monitor.expiry-interval-ms is set less than heartbeat interval

[ https://issues.apache.org/jira/browse/YARN-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshavora updated YARN-1083: Affects Version/s: 2.1.0-beta ResourceManager should fail when

[jira] [Created] (YARN-1084) RM restart does not work for map only job

yeshavora created YARN-1084: --- Summary: RM restart does not work for map only job Key: YARN-1084 URL: https://issues.apache.org/jira/browse/YARN-1084 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

yeshavora created YARN-1057: --- Summary: Add mechanism to check validity of a Node to be Added/Excluded Key: YARN-1057 URL: https://issues.apache.org/jira/browse/YARN-1057 Project: Hadoop YARN

[jira] [Commented] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

[ https://issues.apache.org/jira/browse/YARN-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737030#comment-13737030 ] yeshavora commented on YARN-1057: - By 'Invalide hostname/node', I mean the incorrect name

[jira] [Commented] (YARN-775) stream jobs are not cleaning the Yarn local-dirs after container is released

[ https://issues.apache.org/jira/browse/YARN-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13678174#comment-13678174 ] yeshavora commented on YARN-775: Setting yarn.nodemanager.delete.debug-delay-sec solves the

[jira] [Resolved] (YARN-775) stream jobs are not cleaning the Yarn local-dirs after container is released

[ https://issues.apache.org/jira/browse/YARN-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshavora resolved YARN-775. Resolution: Invalid stream jobs are not cleaning the Yarn local-dirs after container is released

[jira] [Created] (YARN-775) stream jobs are not cleaning the Yarn local-dirs after container is released

yeshavora created YARN-775: -- Summary: stream jobs are not cleaning the Yarn local-dirs after container is released Key: YARN-775 URL: https://issues.apache.org/jira/browse/YARN-775 Project: Hadoop YARN

[jira] [Commented] (YARN-775) stream jobs are not cleaning the Yarn local-dirs after container is released

[ https://issues.apache.org/jira/browse/YARN-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677636#comment-13677636 ] yeshavora commented on YARN-775: I was not setting yarn.nodemanager.delete.debug-delay-sec