-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
HistoryTemplateSearchInputMappingsTests failure on master with RejectedExecutionException #47749
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>test-failure
Triaged test failures from CI
Comments
dakrone
added
>test-failure
Triaged test failures from CI
:Data Management/Watcher
labels
Oct 8, 2019
Pinging @elastic/es-core-features (:Core/Features/Watcher) |
It seems to be something to do with the way the SnapshotRetentionService is being shut down? Build scan is here: https://gradle-enterprise.elastic.co/s/5z5xvauuwaqxg/console-log?task=:x-pack:plugin:watcher:test |
romseygeek
added
the
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
label
Oct 18, 2019
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Oct 29, 2019
This adds a guard for the SLM lifecycle and retention service that prevents new jobs from being scheduled once the service has been stopped. Previous if the node were shut down the service would be stopped, but a cluster state or local master election would cause a job to attempt to be scheduled. This could lead to an uncaught `RejectedExecutionException`. Resolves elastic#47749
dakrone
added a commit
that referenced
this issue
Oct 30, 2019
This adds a guard for the SLM lifecycle and retention service that prevents new jobs from being scheduled once the service has been stopped. Previous if the node were shut down the service would be stopped, but a cluster state or local master election would cause a job to attempt to be scheduled. This could lead to an uncaught `RejectedExecutionException`. Resolves #47749
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Oct 30, 2019
This adds a guard for the SLM lifecycle and retention service that prevents new jobs from being scheduled once the service has been stopped. Previous if the node were shut down the service would be stopped, but a cluster state or local master election would cause a job to attempt to be scheduled. This could lead to an uncaught `RejectedExecutionException`. Resolves elastic#47749
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Oct 30, 2019
This adds a guard for the SLM lifecycle and retention service that prevents new jobs from being scheduled once the service has been stopped. Previous if the node were shut down the service would be stopped, but a cluster state or local master election would cause a job to attempt to be scheduled. This could lead to an uncaught `RejectedExecutionException`. Resolves elastic#47749
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Oct 30, 2019
This adds a guard for the SLM lifecycle and retention service that prevents new jobs from being scheduled once the service has been stopped. Previous if the node were shut down the service would be stopped, but a cluster state or local master election would cause a job to attempt to be scheduled. This could lead to an uncaught `RejectedExecutionException`. Resolves elastic#47749
dakrone
added a commit
that referenced
this issue
Oct 30, 2019
This adds a guard for the SLM lifecycle and retention service that prevents new jobs from being scheduled once the service has been stopped. Previous if the node were shut down the service would be stopped, but a cluster state or local master election would cause a job to attempt to be scheduled. This could lead to an uncaught `RejectedExecutionException`. Resolves #47749
dakrone
added a commit
that referenced
this issue
Oct 30, 2019
This adds a guard for the SLM lifecycle and retention service that prevents new jobs from being scheduled once the service has been stopped. Previous if the node were shut down the service would be stopped, but a cluster state or local master election would cause a job to attempt to be scheduled. This could lead to an uncaught `RejectedExecutionException`. Resolves #47749
dakrone
added a commit
that referenced
this issue
Oct 30, 2019
* Don't schedule SLM jobs when services have been stopped (#48658) This adds a guard for the SLM lifecycle and retention service that prevents new jobs from being scheduled once the service has been stopped. Previous if the node were shut down the service would be stopped, but a cluster state or local master election would cause a job to attempt to be scheduled. This could lead to an uncaught `RejectedExecutionException`. Resolves #47749 * Fix test for backport
This was referenced Feb 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>test-failure
Triaged test failures from CI
The failure looks like:
I was not able to reproduce this with
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+pull-request-2/8367/console
https://gradle-enterprise.elastic.co/s/bsbxzot5q5dfy
The text was updated successfully, but these errors were encountered: