[ResponseOps][Task Manager][mget Claimer] ensure we can switch between claimers after a restart #184941
Assignees
Labels
Feature:Task Manager
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
pmuellr
added
Feature:Task Manager
Team:ResponseOps
|
Pinging @elastic/response-ops (Team:ResponseOps) |
This was referenced Jun 6, 2024
ymao1
added a commit
that referenced
this issue
Jun 21, 2024
…ask claim strategies (#186419) Resolves #184941 ## Summary Adds integration test to verify that restarting Kibana with a different task claim strategy does not break anything and tasks are claimed as expected. --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
bhapas
pushed a commit
to bhapas/kibana
that referenced
this issue
Jun 24, 2024
…ask claim strategies (elastic#186419) Resolves elastic#184941 ## Summary Adds integration test to verify that restarting Kibana with a different task claim strategy does not break anything and tasks are claimed as expected. --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In PR implement task claiming strategy mget #180485 we implemented an alternative task claiming strategy, but it has the following problem:
We didn't add any kind of check to see if you can switch between claimers (with a config value change), and everything still runs correctly.
Ideally we can do this with a Jest integration test, I don't think it would be possible with a Function test.
The text was updated successfully, but these errors were encountered: