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] [Work logged] (HDDS-1668) Add liveness probe to the example
k8s resources files
[ https://issues.apache.org/jira/browse/HDDS-1668?focusedWorklogId=257561&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-257561 ]
ASF GitHub Bot logged work on HDDS-1668:
----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Jun/19 09:39
Start Date: 11/Jun/19 09:39
Worklog Time Spent: 10m
Work Description: elek commented on pull request #944: HDDS-1668. Add liveness probe to the example k8s resources files
URL: https://github.com/apache/hadoop/pull/944
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
See: https://issues.apache.org/jira/browse/HDDS-1668
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 257561)
Time Spent: 10m
Remaining Estimate: 0h
> 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
> Time Spent: 10m
> 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.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org