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

If doc monitor execution fails for certain errors, log error alert, update seq no and ensure further data is seen in next execution #1383

Open
eirsep opened this issue Jan 20, 2024 · 0 comments
Labels
v2.9.1 Issues targeting release v2.9.1 v2.19.0 Issues targeting release v2.19.0

Comments

@eirsep
Copy link
Member

eirsep commented Jan 20, 2024

  • We could create a boolean flag createErrorAlertsAndMoveOn which is true by default
  • create a list that holds exceptions from following operations

If percolate query fails, on one of the batches of docs queried, we can add to list of exceptions and move on to update sequence number. Don't fail entire monitor execution


If shard fetch fails circuit breaker exception we can retry in upcoming executions of job for that shard but catch and continue execution to try query other shards/indices

@eirsep eirsep added the v2.12.0 Issues targeting release v2.12.0 label Jan 20, 2024
@eirsep eirsep removed the untriaged label Feb 8, 2024
@eirsep eirsep added v2.9.1 Issues targeting release v2.9.1 v2.19.0 Issues targeting release v2.19.0 and removed v2.12.0 Issues targeting release v2.12.0 labels Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2.9.1 Issues targeting release v2.9.1 v2.19.0 Issues targeting release v2.19.0
Projects
None yet
Development

No branches or pull requests

1 participant