[
https://issues.apache.org/jira/browse/YARN-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16624319#comment-16624319
]
Gour Saha commented on YARN-8734:
---------------------------------
In that case may be a simpler approach will be to call this property
"dependencies". It is already at the service level so it implies service level
dependencies. Just like dependencies at the component level implies component
dependencies and is simply called "dependencies". Additionally, avoiding the
remote or external keywords helps avoid confusion or limitations in service
owner's mind. Just like component "dependencies" validate that the values are
valid component names, expectation would be that service level "dependencies"
will be valid YARN services only. At least that's exactly what the code does.
One code review comment:
Is {{remote_service_dependencies}} defined outside the properties section in
YAML swagger spec?
> Readiness check for remote service
> ----------------------------------
>
> Key: YARN-8734
> URL: https://issues.apache.org/jira/browse/YARN-8734
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: yarn-native-services
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Attachments: Dependency check vs.pdf, YARN-8734.001.patch,
> YARN-8734.002.patch, YARN-8734.003.patch, YARN-8734.004.patch,
> YARN-8734.005.patch
>
>
> When a service is deploying, there can be remote service dependency. It
> would be nice to describe ZooKeeper as a dependent service, and the service
> has reached a stable state, then deploy HBase.
--
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
