Open onnimonni opened 7 years ago
Why not build the timeout into your script running Cavalcade Runner instead? (sleep 10 && cavalcade
) It seems like a system-specific thing if your MySQL instance hasn't yet started, rather than something specific to Cavalcade.
I think it would be better to have it in cavalcade itself so it can also automatically retry few times before failing. There must be other environments where this is preferable default behaviour too.
I agree with @rmccue here. If mysql isn't ready yet, then your scheduler or your other orchestration/infrastructure management tools should take into account that a dependent resource isn't available before starting the container, or work it out that the container fails and the scheduler restarts it. Hopefully you've worked out a workaround!
I'm running this in local docker environment and I'm hitting an error which says that database refuses connection:
This happens because my mysql is not ready yet. Could we add a default timeout which could be adjusted with an flag like
--timeout=10
?