[jira] [Updated] (YARN-4060) Revisit default retry config for connection with RM
[ https://issues.apache.org/jira/browse/YARN-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated YARN-4060: --- Target Version/s: 2.7.4, 2.6.6 (was: 2.6.5, 2.7.4) Moving this issue to 2.6.6. Please move back if you feel otherwise. > Revisit default retry config for connection with RM > > > Key: YARN-4060 > URL: https://issues.apache.org/jira/browse/YARN-4060 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jian He >Assignee: Jian He > > 15 minutes timeout for AM/NM connection with RM in non-ha scenario turns out > to be short in production environment. The suggestion is to increase that > to 30 min. Also, the retry-interval is set to 30 seconds which appears too > long. We may reduce that to 10 seconds ? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-4060) Revisit default retry config for connection with RM
[ https://issues.apache.org/jira/browse/YARN-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-4060: -- Target Version/s: 2.6.5, 2.7.4 (was: 2.7.3, 2.6.5) 2.7.3 is under release process, changing target-version to 2.7.4. > Revisit default retry config for connection with RM > > > Key: YARN-4060 > URL: https://issues.apache.org/jira/browse/YARN-4060 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jian He >Assignee: Jian He > > 15 minutes timeout for AM/NM connection with RM in non-ha scenario turns out > to be short in production environment. The suggestion is to increase that > to 30 min. Also, the retry-interval is set to 30 seconds which appears too > long. We may reduce that to 10 seconds ? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-4060) Revisit default retry config for connection with RM
[ https://issues.apache.org/jira/browse/YARN-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4060: - Target Version/s: 2.7.3, 2.6.5 (was: 2.7.3, 2.6.4) > Revisit default retry config for connection with RM > > > Key: YARN-4060 > URL: https://issues.apache.org/jira/browse/YARN-4060 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jian He >Assignee: Jian He > > 15 minutes timeout for AM/NM connection with RM in non-ha scenario turns out > to be short in production environment. The suggestion is to increase that > to 30 min. Also, the retry-interval is set to 30 seconds which appears too > long. We may reduce that to 10 seconds ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4060) Revisit default retry config for connection with RM
[ https://issues.apache.org/jira/browse/YARN-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4060: - Target Version/s: 2.7.3, 2.6.4 (was: 2.6.3, 2.7.3) > Revisit default retry config for connection with RM > > > Key: YARN-4060 > URL: https://issues.apache.org/jira/browse/YARN-4060 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jian He >Assignee: Jian He > > 15 minutes timeout for AM/NM connection with RM in non-ha scenario turns out > to be short in production environment. The suggestion is to increase that > to 30 min. Also, the retry-interval is set to 30 seconds which appears too > long. We may reduce that to 10 seconds ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4060) Revisit default retry config for connection with RM
[ https://issues.apache.org/jira/browse/YARN-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-4060: -- Target Version/s: 2.6.3, 2.7.3 (was: 2.7.2, 2.6.3) Moving out all non-critical / non-blocker issues that didn't make it out of 2.7.2 into 2.7.3. > Revisit default retry config for connection with RM > > > Key: YARN-4060 > URL: https://issues.apache.org/jira/browse/YARN-4060 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jian He >Assignee: Jian He > > 15 minutes timeout for AM/NM connection with RM in non-ha scenario turns out > to be short in production environment. The suggestion is to increase that > to 30 min. Also, the retry-interval is set to 30 seconds which appears too > long. We may reduce that to 10 seconds ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4060) Revisit default retry config for connection with RM
[ https://issues.apache.org/jira/browse/YARN-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4060: -- Target Version/s: 2.7.2, 2.6.3 (was: 2.7.2, 2.6.2) Targeting 2.6.3 now that 2.6.2 has shipped. > Revisit default retry config for connection with RM > > > Key: YARN-4060 > URL: https://issues.apache.org/jira/browse/YARN-4060 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jian He >Assignee: Jian He > > 15 minutes timeout for AM/NM connection with RM in non-ha scenario turns out > to be short in production environment. The suggestion is to increase that > to 30 min. Also, the retry-interval is set to 30 seconds which appears too > long. We may reduce that to 10 seconds ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
