Skip to content
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

How to handle node where aws kinesis input thread is running #72

Open
umeshdc opened this issue Apr 10, 2018 · 3 comments
Open

How to handle node where aws kinesis input thread is running #72

umeshdc opened this issue Apr 10, 2018 · 3 comments

Comments

@umeshdc
Copy link

umeshdc commented Apr 10, 2018

Hi,

We have 2 node graylog cluster and we found that at any point aws kinesis input thread will be running in only one graylog node.

Also we found that if graylog node where this thread is running goes down, their no way that active graylog will recreate that thread to continue consuming messages.

Please let us know if their is a way to handle this scenario.

Thanks

@joschi
Copy link
Contributor

joschi commented Apr 10, 2018

@umeshdc Have you tried starting the input as a global input (which is running on all nodes)?

@umeshdc
Copy link
Author

umeshdc commented Apr 11, 2018

Yes, If we choose global option while creating input, then thread will be created in randomly selected node. If we select specific node then thread will be always created in the selected node.

@gabricar
Copy link

gabricar commented Jul 6, 2023

I have the same issue. Global option does not work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants