# Helm chart - readinessProbe failure without errors

**URL:** https://discuss.elastic.co/t/helm-chart-readinessprobe-failure-without-errors/295091
**Category:** Beats
**Tags:** filebeat
**Created:** [January 21, 2022, 5:47pm UTC](https://discuss.elastic.co/t/helm-chart-readinessprobe-failure-without-errors/295091 "2022-01-21T17:47:14Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![aumthanki](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aumthanki/32/100697_2.png) [@aumthanki](https://discuss.elastic.co/u/aumthanki)
#### Post date: [January 21, 2022, 5:47pm UTC](https://discuss.elastic.co/t/helm-chart-readinessprobe-failure-without-errors/295091/1 "2022-01-21T17:47:14Z")

</div>

Hi,

Has anyone been forced to tweak the readinessprobe for the filebeat chart?

readinessProbe:  
exec:  
command:  
- sh  
- -c  
- |  
#!/usr/bin/env bash -e  
filebeat test output  
failureThreshold: 3  
initialDelaySeconds: 10  
periodSeconds: 10  
timeoutSeconds: 5

Seeing pods fail the readiness probe check but without any errors:  
3m12s Warning Unhealthy pod/filebeat-filebeat-2rfcf Readiness probe failed:

The only workaround I've found is to increase the failurethreshold, periodseconds and timeoutseconds.

Regards,  
Aum

---

<div class="post-metadata">

### Author: ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)
#### Post date: [January 24, 2022, 2:02pm UTC](https://discuss.elastic.co/t/helm-chart-readinessprobe-failure-without-errors/295091/2 "2022-01-24T14:02:58Z")

</div>

Hi,

could you please format this post using `code tags`? Thanks in advance!

---

<div class="post-metadata">

### Author: ![aumthanki](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aumthanki/32/100697_2.png) [@aumthanki](https://discuss.elastic.co/u/aumthanki)
#### Post date: [January 24, 2022, 2:21pm UTC](https://discuss.elastic.co/t/helm-chart-readinessprobe-failure-without-errors/295091/3 "2022-01-24T14:21:39Z")

</div>

I can't edit the post, apologises. Here is the readiness probe settings formatted correctly:

```auto
readinessProbe:
exec:
command:
- sh
- -c
- |
#!/usr/bin/env bash -e
filebeat test output
failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5

```

Our elastic cluster is hosted on Azure. It has two nodes (one master) and a tiebreaker node. The master node seems to be heavily utilised whereas the other node is not. Is this configured on the filebeat level or inside of the node config? How does log balancing work?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 21, 2022, 4:22pm UTC](https://discuss.elastic.co/t/helm-chart-readinessprobe-failure-without-errors/295091/4 "2022-02-21T16:22:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
