[
https://issues.apache.org/jira/browse/YARN-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437969#comment-16437969
]
Eric Yang commented on YARN-8060:
---------------------------------
[~billie.rinaldi] Thank you for the patch. Readiness check works as
advertised. I ran into a scenario that net=host. Two docker containers ran on
the same host and trying to grab the same port. Readiness checks for both
containers were responded healthy by the first container that grab the port.
This is basically a user error that user can work around by defining placement
policy, or use multiple components to define different ports to prevent
conflicts. Readiness check can not compensate for user errors. Therefore, it
is a good idea to document readiness check would not compensate for this type
of user errors to set expectations correctly.
> 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,
> YARN-8060.4.patch, YARN-8060.5.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: [email protected]
For additional commands, e-mail: [email protected]
