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

Extractor creation cannot load input in multi-node setup #2580

Closed
kroepke opened this issue Aug 2, 2016 · 0 comments
Closed

Extractor creation cannot load input in multi-node setup #2580

kroepke opened this issue Aug 2, 2016 · 0 comments
Assignees
@bernd
Labels
P1 S1 bug triaged
Milestone
2.1.0

Comments

@kroepke
Copy link
Member

@kroepke kroepke commented Aug 2, 2016

Problem description

When creating an extractor for a non-global input in a multi node setup, the extractor creation will fail if the input is not running on the node the web interface is being served from.

The REST resource checks its local input states for a running input, which it does not have and then fails the request.

Steps to reproduce the problem

  1. Start at least two nodes (A and B)
  2. Use the web interface from node A
  3. Create an input on a node B
  4. Send a message, search and create an extractor for a field
  5. Configure arbitrary extractor
  6. Save that extractor
  7. Server returns 404 "no such input"

Environment

  • Graylog Version: 2.1.0-beta.2 SNAPSHOT
  • Elasticsearch Version: n/a
  • MongoDB Version: n/a
  • Operating System: n/a
  • Browser version: n/a
@kroepke kroepke added the bug label Aug 2, 2016
@kroepke kroepke added this to the 2.1.0 milestone Aug 2, 2016
@bernd bernd added S1 P1 labels Aug 2, 2016
@bernd bernd self-assigned this Aug 2, 2016
bernd added a commit that referenced this issue Aug 2, 2016
@bernd
Fix extractor and static fields creation in multi-node setups
Loading status checks…
f3ea18b 
The extractor and static fields resource was using the local input
registry to check if an input exists. This breaks in a multi-node setup
where the web interface runs on node A and the input on node B.

Fixes #2580
@bernd bernd mentioned this issue Aug 2, 2016
Merged
@joschi joschi closed this in #2584 Aug 2, 2016
joschi added a commit that referenced this issue Aug 2, 2016
@bernd @joschi
Fix extractor and static fields creation in multi-node setups (#2584)
Loading status checks…
61656d4 
The extractor and static fields resource was using the local input
registry to check if an input exists. This breaks in a multi-node setup
where the web interface runs on node A and the input on node B.

Fixes #2580
@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

@bernd bernd

Labels
P1 S1 bug triaged
Projects
None yet
Milestone
2.1.0
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@bernd @kroepke