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

[DOC] Alerting plugin not compatible with segment replication feature #4967

Closed
1 of 4 tasks
dreamer-89 opened this issue Sep 5, 2023 · 0 comments · Fixed by #4976
Closed
1 of 4 tasks

[DOC] Alerting plugin not compatible with segment replication feature #4967

dreamer-89 opened this issue Sep 5, 2023 · 0 comments · Fixed by #4976
Assignees
Labels
3 - Done Issue is done/complete v2.10.0
Milestone

Comments

@dreamer-89
Copy link
Member

dreamer-89 commented Sep 5, 2023

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
As part of campaign to validate compatibility of plugins with SEGMENT replication feature, we identified alerting plugin is not compatible in current (2.10.0) and in all previous versions. This is because alerting relies on the fact that latest data will be available on replica shards when using IMMEDIATE refresh policy. SEGMENT replication does not provide same guarantees with IMMEDIATE refresh policy and thus it is possible that replica shards be stale. This impacts the document level monitors in alerting plugin and security-analytics plugin (internally uses document level monitors). We need to update the SEGMENT replication documentation and add this limitation.

This short-coming is tracked on core in opensearch-project/OpenSearch#9669

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
Alerting plugin issue: opensearch-project/alerting#974
Core campaign issue: opensearch-project/OpenSearch#8211

@Naarcha-AWS Naarcha-AWS added 1 - Backlog Issue: The issue is unassigned or assigned but not started backport 2.9 PR: Backport label for 2.9 v2.10.0 and removed untriaged backport 2.9 PR: Backport label for 2.9 labels Sep 6, 2023
@Naarcha-AWS Naarcha-AWS self-assigned this Sep 6, 2023
@Naarcha-AWS Naarcha-AWS added this to the v2.10 milestone Sep 6, 2023
@Naarcha-AWS Naarcha-AWS removed their assignment Sep 6, 2023
@vagimeli vagimeli self-assigned this Sep 6, 2023
@vagimeli vagimeli added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog Issue: The issue is unassigned or assigned but not started labels Sep 6, 2023
@vagimeli vagimeli linked a pull request Sep 6, 2023 that will close this issue
1 task
@vagimeli vagimeli added 3 - Done Issue is done/complete and removed 2 - In progress Issue/PR: The issue or PR is in progress. labels Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Done Issue is done/complete v2.10.0
Projects
None yet
3 participants