backup cronjob never never completes
Looks like the cronjob that does snapshots is getting stuck somewhere:
2018/04/27 23:07:55 [elasticsearch-cron] is up and running! 2018-04-27 23:07:55.208610306 +0000 UTC m=+0.001643516
time="2018-04-27T23:07:55Z" level=info msg="About to create snapshot..."
Its been in a running state for two days with only the above in the logs
@wjimenez5271 What the version of your es operator?
@gianrubio sorry for the late reply. upmcenterprises/elasticsearch-operator:0.0.12
Check if you are using the latest cronjob , also paste the logs from the master node during the snapshot execution
Interesting, I actually don't even have that key in my resource
On Fri, May 25, 2018, 6:28 AM Giancarlo Rubio [email protected] wrote:
Check if you are using the latest cronjob https://github.com/upmc-enterprises/elasticsearch-operator/blob/master/example/example-es-cluster.yaml#L23, also paste the logs from the master node during the snapshot execution
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/upmc-enterprises/elasticsearch-operator/issues/189#issuecomment-392057549, or mute the thread https://github.com/notifications/unsubscribe-auth/AATtEucYd4lhlSCmNh-PKuPvoew2W1nOks5t2AbhgaJpZM4TtOnG .
Sorry for delay in getting back to you @wjimenez5271, are you still having issues with this?