dashboard / widget in load balanced setup #2732
Closed
Comments
dennisoelkers
added a commit
that referenced
this issue
Aug 25, 2016
Before this, a change to a widget done on one node was not reflected correctly on other nodes, due to the widget being cached in the WidgetResultsCache. This change now creates and tracks widget update events cluster-wide and invalidates the local caches accordingly. Fixes #2732.
joschi
added a commit
that referenced
this issue
Aug 29, 2016
) Before this, a change to a widget done on one node was not reflected correctly on other nodes, due to the widget being cached in the WidgetResultsCache. This change now creates and tracks widget update events cluster-wide and invalidates the local caches accordingly. Fixes #2732
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
If you run a widget on a dashboard and change the search relative time this should be propagated to all nodes.
Current Behavior
The search relative time is not set on all nodes instant. This leads to flipping widgets for different users that are not usable.
Possible Solution
Propagate the changed relative time via cluster event to all nodes in the cluster.
Steps to Reproduce
Context
Having a Load balanced Environment of Graylog Nodes to shift the load of the Web Interface. No sticky connection let the people "jump" between the configured nodes. But every request is then served with the new (changed) relative time or the old that is not propagated to all nodes instant.
Your Environment
The text was updated successfully, but these errors were encountered: