[
https://issues.apache.org/jira/browse/YARN-11463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713129#comment-17713129
]
ASF GitHub Bot commented on YARN-11463:
---------------------------------------
ashutoshcipher opened a new pull request, #5562:
URL: https://github.com/apache/hadoop/pull/5562
### Description of PR
Node Labels root directory creation doesn't have a retry logic
JIRA - YARN-11463
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Node Labels root directory creation doesn't have a retry logic
> --------------------------------------------------------------
>
> Key: YARN-11463
> URL: https://issues.apache.org/jira/browse/YARN-11463
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
> Reporter: Benjamin Teke
> Assignee: Ashutosh Gupta
> Priority: Major
>
> When CS is initialized, it'll [try to create the configured node labels root
> dir|https://github.com/apache/hadoop/blob/7169ec450957e5602775c3cd6fe1bf0b95773dfb/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/nodelabels/store/AbstractFSNodeStore.java#L69].
> This however doesn't implement any kind of retry logic (in contrast to the
> RM FS state store or ZK state store), hence if the distributed file system is
> unavailable at the exact moment CS tries to start it'll fail. A retry logic
> could be implemented to improve the robustness of the startup process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
