You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I enabled elasticsearch with the default values and found the system stuck in a CrashLoopBackOff. After investigating, it turns out neither the readiness nor live probe were able to return true; delaying or disabling both of them allowed the cluster to live and take requests from rails.
It turns out this was a bug with bitnami/elasticsearch, and was fixed about a month ago. I upgraded the chart and the problem was resolved.
I have implemented the change in my fork. PR to follow shortly.
The text was updated successfully, but these errors were encountered:
I enabled elasticsearch with the default values and found the system stuck in a CrashLoopBackOff. After investigating, it turns out neither the readiness nor live probe were able to return true; delaying or disabling both of them allowed the cluster to live and take requests from rails.
It turns out this was a bug with bitnami/elasticsearch, and was fixed about a month ago. I upgraded the chart and the problem was resolved.
I have implemented the change in my fork. PR to follow shortly.
The text was updated successfully, but these errors were encountered: