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

[BUG] Job Scheduler internal index has replicas #168

Closed
Tracked by #587
AlexRuiz7 opened this issue Dec 5, 2024 · 1 comment · Fixed by #173
Closed
Tracked by #587

[BUG] Job Scheduler internal index has replicas #168

AlexRuiz7 opened this issue Dec 5, 2024 · 1 comment · Fixed by #173
Assignees
Labels
level/task Task issue mvp Minimum Viable Product type/bug Bug issue

Comments

@AlexRuiz7
Copy link
Member

Describe the bug
The internal index of the CM's scheduled job has no settings so it falls back to the default values, which sets 1 replica to the index, causing the cluster to enter the yellow state on single node deployments.

To Reproduce

  1. Run /_cluster/health.
  2. Run /_cat/indices/.*?v.

Expected behavior
Cluster stays green.

Plugins
Command Manager plugin.

Host/Environment (please complete the following information):

  • OS: ['deb', 'rpm']
  • Version ['5.0.0']

Additional context
Packages: https://github.com/wazuh/wazuh-indexer/actions/runs/12164433520

@AlexRuiz7 AlexRuiz7 added level/task Task issue type/bug Bug issue mvp Minimum Viable Product labels Dec 5, 2024
@wazuhci wazuhci moved this to Backlog in XDR+SIEM/Release 5.0.0 Dec 5, 2024
@wazuhci wazuhci moved this from Backlog to In progress in XDR+SIEM/Release 5.0.0 Dec 6, 2024
@wazuhci wazuhci moved this from In progress to Pending review in XDR+SIEM/Release 5.0.0 Dec 6, 2024
@QU3B1M
Copy link
Member

QU3B1M commented Dec 6, 2024

LGTM! Everything works as expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue mvp Minimum Viable Product type/bug Bug issue
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants