Skip to content

Fix CreateIndexIT#testCreateAndDeleteIndexConcurrently#15853

Closed
s1monw wants to merge 1 commit intoelastic:masterfrom
s1monw:fix_testCreateAndDeleteIndexConcurrently
Closed

Fix CreateIndexIT#testCreateAndDeleteIndexConcurrently#15853
s1monw wants to merge 1 commit intoelastic:masterfrom
s1monw:fix_testCreateAndDeleteIndexConcurrently

Conversation

@s1monw
Copy link
Copy Markdown
Contributor

@s1monw s1monw commented Jan 8, 2016

The test fails in different ways since we can hit timeouts and shards not being available on retry
which we simply didn't expect before but are valid.

Closes #15312
Closes #14512

The test fails in different ways since we can hit timeouts and shards not being available on retry
which we simply didn't expect before but are valid.

Closes elastic#15312
Closes elastic#14512
@s1monw s1monw added >test Issues or PRs that are addressing/adding tests review labels Jan 8, 2016
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should throw the IndexNotFoundException instead?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we do if the index is not there, but there is a racing condition where the index is there when we check for that and then the shards are deleted beneath us. Then we go and wait for the shards (identically to where the index is created but the shards are not assigned yet), which results in this exception. We can do another check before failing, but I don't think it's worth it for this edge case?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough. Its probably not worth it.

@areek areek closed this in #16442 Mar 15, 2016
s1monw added a commit to s1monw/elasticsearch that referenced this pull request Mar 15, 2016
Since elastic#16442 is merged we should be able to reenable this test as a followup
of elastic#15853 - all issues blocking it have been resolved I guess.
@s1monw s1monw deleted the fix_testCreateAndDeleteIndexConcurrently branch March 15, 2016 08:32
s1monw added a commit that referenced this pull request Mar 15, 2016
Reenable CreateIndexIT#testCreateAndDeleteIndexConcurrently

Since #16442 is merged we should be able to reenable this test as a followup
of #15853 - all issues blocking it have been resolved I guess.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>test Issues or PRs that are addressing/adding tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants