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.

Sign up for GitHub

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

FIX: Only heavy nodes should be treated as remote Elastic clusters in SOC #11553

Closed
jertel opened this issue Oct 16, 2023 · 0 comments · Fixed by #11552
Closed

FIX: Only heavy nodes should be treated as remote Elastic clusters in SOC #11553

jertel opened this issue Oct 16, 2023 · 0 comments · Fixed by #11552
Assignees
@jertel
Milestone
2.4.30

Comments

@jertel
Copy link
Contributor

jertel commented Oct 16, 2023

Heavy nodes are the only nodes that should be individually updated by SOC in addition to the manager node. All other nodes are handled by Elastic clustering via the manager node.
@jertel jertel added this to the 2.4.30 milestone Oct 16, 2023
@jertel jertel self-assigned this Oct 16, 2023
@jertel jertel linked a pull request Oct 16, 2023 that will close this issue
only add heavynodes to remoteHostUrls #11552
Merged
@jertel jertel closed this as completed Oct 19, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jertel jertel

Labels
None yet
Projects
None yet
Milestone
2.4.30
Development

Successfully merging a pull request may close this issue.

only add heavynodes to remoteHostUrls Security-Onion-Solutions/securityonion
1 participant
@jertel