onyx

FYI: alternative Onyx :onyx: chat is at <https://gitter.im/onyx-platform/onyx> ; log can be found at <https://clojurians-log.clojureverse.org/onyx/index.html>
sparkofreason 2018-07-09T04:03:30.000111Z

Whittling down the production issues. Recently got a "host not found" exception from S3, which I assume is just S3 being flakey. Looks like onyx tried several times to connect and eventually gave up and shut everything down. Is there a setting or something to avoid full shutdown in this case (or some pattern for auto restart of the jobs)?

lucasbradstreet 2018-07-09T04:08:58.000027Z

If you return :restart from your handle-exception lifecycle it should just keep rebooting the peer until it comes back up.

lucasbradstreet 2018-07-09T04:09:53.000076Z

I’ve seen some of those transient host not found issues and I was never sure if it was S3 or whether it was some DNS issues within the container.

sparkofreason 2018-07-09T04:11:11.000043Z

Thanks, completely blanked on the handle-exception lifecycle.

jasonbell 2018-07-09T09:29:09.000104Z

@dave.dixon I found that S3 becomes unreachable quite a lot, Lucas has already answered it but yes the lifecycle restart on handle exception is a life saver 🙂

👍 1