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

Needs to only be one primary viewer. #40

Closed
awick opened this issue Apr 27, 2023 · 1 comment
Closed

Needs to only be one primary viewer. #40

awick opened this issue Apr 27, 2023 · 1 comment
Assignees

Comments

@awick
Copy link
Contributor

awick commented Apr 27, 2023

Background:
Currently viewer is designed that one and only one viewer node will have cronQueries=true set in the config file. The viewer node with this set to true is responsible for running the cron queries and hunts. If multiple nodes have this setting, all the nodes will run the queries which can be inefficient and cause OS/ES overload. It is ok if there is no primary node for a period of time since when a primary node starts back up it will just resume where the last primary node was.

Problem:
Since we are starting up multiple nodes behind an ASG we need to make sure we only have at most 1 primary node at a time.

Possible solutions:

  1. Arkime change of cronQueries=auto where the viewers figure out themselves who should be the primary viewer.
  2. Dedicated primary viewer that isn't actually behind the ASG.
@awick awick self-assigned this Apr 27, 2023
@awick
Copy link
Contributor Author

awick commented May 1, 2023

fixed by #41 and arkime/arkime#2254

@awick awick closed this as completed May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant