Skip to content

/ graylog2-server

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

dashboard / widget in load balanced setup #2732

Closed
jalogisch opened this issue Aug 23, 2016 · 0 comments
Closed

dashboard / widget in load balanced setup #2732

jalogisch opened this issue Aug 23, 2016 · 0 comments
Assignees
@dennisoelkers
Labels
P3 S2 bug triaged
Milestone
2.1.0

Comments

@jalogisch
Copy link
Contributor

@jalogisch jalogisch commented Aug 23, 2016

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

  1. Loadbalanced Graylog (two nodes behind a load balancer)
  2. Create a Dashboard Widget
  3. Load the Widget Configuration and change time relative time

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

  • Graylog Version: 2.X
@dennisoelkers dennisoelkers self-assigned this Aug 24, 2016
dennisoelkers added a commit that referenced this issue Aug 25, 2016
@dennisoelkers
Invalidating widget result cache cluster wide when a widget changes.
Verified
This commit was signed with a verified signature.
dennisoelkers Dennis Oelkers
GPG key ID: 26B2C114209DC497 Learn about signing commits
a992a13 
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.
@dennisoelkers dennisoelkers mentioned this issue Aug 25, 2016
Merged
4 of 9 tasks complete
@joschi joschi added this to the 2.1.0 milestone Aug 29, 2016
@joschi joschi added bug S2 P3 labels Aug 29, 2016
@joschi joschi closed this in #2745 Aug 29, 2016
joschi added a commit that referenced this issue Aug 29, 2016
@dennisoelkers @joschi
Invalidate widget result cache cluster-wide when a widget changes (#2745
Loading status checks…
00881b9 
)

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
@kroepke kroepke added the triaged label Sep 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dennisoelkers dennisoelkers

Labels
P3 S2 bug triaged
Projects
None yet
Milestone
2.1.0
Linked pull requests

Successfully merging a pull request may close this issue.

Invalidating widget result cache cluster wide when a widget changes.
4 participants
@dennisoelkers @joschi @kroepke @jalogisch