-
Notifications
You must be signed in to change notification settings - Fork 25.2k
testForceMergeWithSoftDeletesRetentionAndRecoverySource fails #48735
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
Labels
:Distributed Indexing/Engine
Anything around managing Lucene and the Translog in an open shard.
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/es-distributed (:Distributed/Engine) |
dnhatn
added a commit
that referenced
this issue
Nov 1, 2019
This test failure manifests the limitation of the recovery source merge policy explained in #41628. If we already merge down to a single segment then subsequent force merges will be noop although they can prune recovery source. We need to adjust this test until we have a fix for the merge policy. Relates #41628 Closes #48735
dnhatn
added a commit
that referenced
this issue
Nov 3, 2019
This test failure manifests the limitation of the recovery source merge policy explained in #41628. If we already merge down to a single segment then subsequent force merges will be noop although they can prune recovery source. We need to adjust this test until we have a fix for the merge policy. Relates #41628 Closes #48735
dnhatn
added a commit
that referenced
this issue
Nov 3, 2019
This test failure manifests the limitation of the recovery source merge policy explained in #41628. If we already merge down to a single segment then subsequent force merges will be noop although they can prune recovery source. We need to adjust this test until we have a fix for the merge policy. Relates #41628 Closes #48735
dnhatn
added a commit
that referenced
this issue
Nov 9, 2019
This test failure manifests the limitation of the recovery source merge policy explained in #41628. If we already merge down to a single segment then subsequent force merges will be noop although they can prune recovery source. We need to adjust this test until we have a fix for the merge policy. Relates #41628 Closes #48735
dnhatn
added a commit
that referenced
this issue
Nov 9, 2019
This test failure manifests the limitation of the recovery source merge policy explained in #41628. If we already merge down to a single segment then subsequent force merges will be noop although they can prune recovery source. We need to adjust this test until we have a fix for the merge policy. Relates #41628 Closes #48735
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/Engine
Anything around managing Lucene and the Translog in an open shard.
>test-failure
Triaged test failures from CI
On
master
(3e4791a) I get the following failure:The
REPRODUCE WITH
line does seem to reliably reproduce this.The text was updated successfully, but these errors were encountered: