[
https://issues.apache.org/jira/browse/YARN-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437469#comment-16437469
]
Gour Saha commented on YARN-8060:
---------------------------------
{quote} let's open a separate ticket to discuss allowing multiple checks
{quote}
Totally makes sense
{quote} ...it is allowing you to adjust the system-wide default instead of
having all systems stuck with the default of 10...
{quote}
This is a great point and I did not think along this line. This is a nice way
to allow and consume cluster level defaults than every service having to
specify them if they don't like dev-chosen defaults. I think we should add a
new section in {{Configurations.md}} listing all these system overridable
configurations.
> Create default readiness check for service components
> -----------------------------------------------------
>
> Key: YARN-8060
> URL: https://issues.apache.org/jira/browse/YARN-8060
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn-native-services
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Priority: Major
> Attachments: YARN-8060.1.patch, YARN-8060.2.patch, YARN-8060.3.patch
>
>
> It is currently possible for a component instance to have READY status before
> the AM retrieves an IP for the container. We should make sure the IP has been
> retrieved before marking the instance as READY.
> This default probe could also have an option to check for a DNS entry for the
> instance's hostname if a DNS address is provided.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
