You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/06/11 09:40:00 UTC

[jira] [Updated] (HDDS-1668) Add liveness probe to the example k8s resources files

     [ https://issues.apache.org/jira/browse/HDDS-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HDDS-1668:
---------------------------------
    Labels: pull-request-available  (was: )

> 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
>
> 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.3#76005)

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