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

[CI] RejectedExecutionTests testHistoryOnRejection fails #47008

Closed
dimitris-athanasiou opened this issue Sep 24, 2019 · 1 comment · Fixed by #47680
Closed

[CI] RejectedExecutionTests testHistoryOnRejection fails #47008

dimitris-athanasiou opened this issue Sep 24, 2019 · 1 comment · Fixed by #47680
Labels
:Data Management/Watcher >test-failure Triaged test failures from CI

Comments

@dimitris-athanasiou
Copy link
Contributor

dimitris-athanasiou commented Sep 24, 2019

Log: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.4+multijob-unix-compatibility/os=fedora-29&&immutable/50/console

Build scan: https://gradle-enterprise.elastic.co/s/lkpncm2tvpqii

Failure:

com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=95, name=elasticsearch[node_s2][generic][T#2], state=RUNNABLE, group=TGRP-RejectedExecutionTests]Close stacktrace
at __randomizedtesting.SeedInfo.seed([2C8460A656D442E1:538BCEA5D73CC9A2]:0)
Caused by: org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution of processing of [79][indices:data/write/bulk[s][p]]: request: BulkShardRequest [[.triggered_watches][0]] containing [delete {[.triggered_watches][_doc][pXWYF_4d32327a-3e4a-404d-b5b8-d5927e7d5ed5-2019-09-24T09:58:00.03Z]}], target allocation id: 3HgeE2uCRmK-F1nbvAJGPA, primary term: 1 on EsThreadPoolExecutor[name = node_s1/write, queue capacity = 1, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@6460c6a2[Running, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 4]]

Reproduce with:

./gradlew ':x-pack:plugin:watcher:test' --tests "org.elasticsearch.xpack.watcher.test.integration.RejectedExecutionTests.testHistoryOnRejection" -Dtests.seed=2C8460A656D442E1 -Dtests.security.manager=true -Dtests.locale=da-DK -Dtests.timezone=Europe/Gibraltar -Dcompiler.java=12 -Druntime.java=8

Cannot reproduce locally.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

jakelandis added a commit to jakelandis/elasticsearch that referenced this issue Oct 7, 2019
If a thread pool rejection exception happens, an alternative code
path is chosen to write history and delete the trigger. If an exception
happens during deletion of the trigger an exception may be thrown and not
caught.

This commit catches the exception and provides a meaning error message.

fixes elastic#47008
jakelandis added a commit that referenced this issue Oct 7, 2019
If a thread pool rejection exception happens, an alternative code
path is chosen to write history and delete the trigger. If an exception
happens during deletion of the trigger an exception may be thrown and not
caught.

This commit catches the exception and provides a meaning error message.

fixes #47008
jakelandis added a commit to jakelandis/elasticsearch that referenced this issue Oct 7, 2019
If a thread pool rejection exception happens, an alternative code
path is chosen to write history and delete the trigger. If an exception
happens during deletion of the trigger an exception may be thrown and not
caught.

This commit catches the exception and provides a meaning error message.

fixes elastic#47008
jakelandis added a commit to jakelandis/elasticsearch that referenced this issue Oct 7, 2019
If a thread pool rejection exception happens, an alternative code
path is chosen to write history and delete the trigger. If an exception
happens during deletion of the trigger an exception may be thrown and not
caught.

This commit catches the exception and provides a meaning error message.

fixes elastic#47008
jakelandis added a commit that referenced this issue Oct 7, 2019
If a thread pool rejection exception happens, an alternative code
path is chosen to write history and delete the trigger. If an exception
happens during deletion of the trigger an exception may be thrown and not
caught.

This commit catches the exception and provides a meaning error message.

fixes #47008
jakelandis added a commit that referenced this issue Oct 7, 2019
If a thread pool rejection exception happens, an alternative code
path is chosen to write history and delete the trigger. If an exception
happens during deletion of the trigger an exception may be thrown and not
caught.

This commit catches the exception and provides a meaning error message.

fixes #47008
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Watcher >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants