bokeh serve exception handling

–

On Mar 6, 2017, at 13:04, josh@hoblitt.com wrote:

Hello,

I am running a bokeh server instance which is managed directly by systemd[1]. Occasionally, an exception is thrown which leaves the server in a broken state until until it is restarted. This is an undesirable failure mode as it requires external monitoring of either websocket responses or logs in order to detect a fault. Ideally, unhandled app exceptions would cause the server instance to die, which in my case would be immediately restarted by systemd. A definitive failure mode would also be preferable when load-balancing between multiple instances.

I am clueless about the workings of tornado but after a quick skim of `bokeh/server/server.py`, I suspect that exceptions are being caught by default in the tornado event loop? Is there a reasonably straight forward path to add support for app generation exceptions to be a fatal error? Any pointers would be greatly appreciated.

Cheers,

-Josh

--
[1]: https://github.com/lsst-sqre/sandbox-jenkins-demo/blob/master/jenkins_demo/templates/squash/squash-bokeh%40.service.epp

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+unsubscribe@continuum.io.
To post to this group, send email to bokeh@continuum.io.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/42bb354e-fd05-4ee7-91c5-1c0dcbfa8eb1%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

On Monday, 6 March 2017 16:09:04 UTC-3, Joshua Hoblitt wrote:

Hello,

I am running a bokeh server instance which is managed directly by systemd1. Occasionally, an exception is thrown which leaves the server in a broken state until until it is restarted. This is an undesirable failure mode as it requires external monitoring of either websocket responses or logs in order to detect a fault. Ideally, unhandled app exceptions would cause the server instance to die, which in my case would be immediately restarted by systemd. A definitive failure mode would also be preferable when load-balancing between multiple instances.

I am clueless about the workings of tornado but after a quick skim of bokeh/server/server.py, I suspect that exceptions are being caught by default in the tornado event loop? Is there a reasonably straight forward path to add support for app generation exceptions to be a fatal error? Any pointers would be greatly appreciated.

Cheers,

-Josh

–