As part of
DM-5844, it was attempt to run multiple instances of the bokeh server using nginx as a reverse proxy/load balancer between instance. However, this is unreliable in practice. The qa dashboard connects to bokeh and establishes a session which is passed to the u-a. The u-a then makes a direct websocket connection to bokeh with this connection information. As there appears to be no state sharing mechanism between bokeh instances, this only "works" if both the qa dashboard and the u-a connect to the same bokeh instance.
An nginx module to add "sticky" cookie based http routing to nginx was tested as working:
If qa dashboard is modified to pass on a cookie from the u-a to it's connection with the bokeh server, this should ensure the dashboard and u-a are connecting to the same bokeh instance.