[
https://issues.apache.org/jira/browse/HDDS-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885626#comment-16885626
]
Anu Engineer commented on HDDS-1668:
------------------------------------
Cherry-picked to 0.4.1
> Add liveness probe to the example k8s resources files
> -----------------------------------------------------
>
> Key: HDDS-1668
> URL: https://issues.apache.org/jira/browse/HDDS-1668
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0, 0.4.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In kubernetes resources we can define livebess probes which can help to
> detect any failure. If the define port is not available the pod will be
> rescheduled.
> We need to add the liveness probes to our k8s resource files.
> Note: We shouldn't add readiness probes. Readiness probe is about the service
> availability. The service/dns can be available only after the service is
> restarted. This is not good for us as:
> * We need DNS resolution during the startup (See
> OzoneManager.loadOMHAConfigs)
> * We already implemented retry in case of missing DNS entries
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
