You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2018/08/30 17:37:00 UTC

[jira] [Commented] (YARN-8733) Readiness check for remote component

    [ https://issues.apache.org/jira/browse/YARN-8733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597715#comment-16597715 ] 

Billie Rinaldi commented on YARN-8733:
--------------------------------------

It seems like we could generalize the HTTP and PORT checks to be able to check an arbitrary remote URL or port. We would probably need to allow a list of checks that would be performed. One question I have is whether the checks should be at the component level (where dependency checks are currently), or whether it would be sufficient to have them at the service level, preventing all components from starting.

> Readiness check for remote component
> ------------------------------------
>
>                 Key: YARN-8733
>                 URL: https://issues.apache.org/jira/browse/YARN-8733
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: yarn-native-services
>            Reporter: Eric Yang
>            Priority: Major
>
> When a service is deploying, there can be remote component dependency between services.  For example, Hive server 2 can depend on Hive metastore, which depends on a remote MySQL database.  It would be great to have ability to check the remote server and port to make sure MySQL is available before deploying Hive LLAP service.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org