-
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
[CI] EarlyDeprecationIndexingIT testEarlyDeprecationIsIndexedAfterTemplateIsLoaded failing #104716
Comments
Pinging @elastic/es-core-infra (Team:Core/Infra) |
this test intends to test the bulkProcessor2's request consumer before the templates are initialised. This requires the flush to happen before the templates are loaded. To test this reliably the flush interval in the test should be as small as possible (not hardcoded 5s as of now) This commit introduces a setting (not meant to be exposed/documented) to allow for the flush interval to be configured. It also adds additional trace logging to help with troubleshooting. relates elastic#104716
this test intends to test the bulkProcessor2's request consumer (see DeprecationIndexingComponent#getBulkProcessor) scheduling requests before the startup is completed (flush is enabled). To verify this behaviour the flush has to happen before the templates are loaded. To test this reliably the flush interval in the test should be as small as possible (not hardcoded 5s as of now) This commit introduces a setting (not meant to be exposed/documented) to allow for the flush interval to be configured. It also adds additional trace logging to help with troubleshooting. relates #104716
I tweaked the test a little (to make sure that it always covers the early deprecation indexing) and enabled trace logging in #105696 |
@pgomulka here's a fresh failure for this one https://gradle-enterprise.elastic.co/s/qca37bsec4djs |
this test intends to test the bulkProcessor2's request consumer (see DeprecationIndexingComponent#getBulkProcessor) scheduling requests before the startup is completed (flush is enabled). To verify this behaviour the flush has to happen before the templates are loaded. To test this reliably the flush interval in the test should be as small as possible (not hardcoded 5s as of now) This commit introduces a setting (not meant to be exposed/documented) to allow for the flush interval to be configured. It also adds additional trace logging to help with troubleshooting. relates elastic#104716
…107540 this test intends to test the bulkProcessor2's request consumer (see DeprecationIndexingComponent#getBulkProcessor) scheduling requests before the startup is completed (flush is enabled). To verify this behaviour the flush has to happen before the templates are loaded. To test this reliably the flush interval in the test should be as small as possible (not hardcoded 5s as of now) This commit introduces a setting (not meant to be exposed/documented) to allow for the flush interval to be configured. It also adds additional trace logging to help with troubleshooting. relates #104716
This issue has been closed because it has been open for too long with no activity. Any muted tests that were associated with this issue have been unmuted. If the tests begin failing again, a new issue will be opened, and they may be muted again. |
Build scan:
https://gradle-enterprise.elastic.co/s/batvq7lqlwwiu/tests/:x-pack:plugin:deprecation:qa:early-deprecation-rest:javaRestTest/org.elasticsearch.xpack.deprecation.EarlyDeprecationIndexingIT/testEarlyDeprecationIsIndexedAfterTemplateIsLoaded
Reproduction line:
Applicable branches:
8.12
Reproduces locally?:
Didn't try
Failure history:
Failure dashboard for
org.elasticsearch.xpack.deprecation.EarlyDeprecationIndexingIT#testEarlyDeprecationIsIndexedAfterTemplateIsLoaded
Failure excerpt:
The text was updated successfully, but these errors were encountered: