Extractor creation cannot load input in multi-node setup #2580
Comments
bernd
added a commit
that referenced
this issue
Aug 2, 2016
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
joschi
added a commit
that referenced
this issue
Aug 2, 2016
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Environment
The text was updated successfully, but these errors were encountered: