fix SearchWithRandomExceptionsTests.testRandomExceptions #3694
Assignees
Labels
Comments
ghost
assigned 
|
thanks for disabling it. I will look into it! |
s1monw
added a commit
that referenced
this issue
Sep 16, 2013
The SearchWithRandomExceptionTests aim to catch problems when resources are not closed due to exceptions etc. Yet in some cases the random seeds cause the index to never be fully allocated so we basically go into a ping-pong state where we try to allocate shards back and forth on nodes. This causes all docs to time out which in-turn causes the tests to run for a very long time (hours or days). If we can not allocate the index and get to a yellow state we simply index only one doc and expected all searches to fail. This commit also beefs up the assertions in this test to check if documents are actually present if they are indexed and refresh was successful. Closes #3694
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
see elastic#3694 Also, this might have caused one of the problems described in issue elastic#3674
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
The SearchWithRandomExceptionTests aim to catch problems when resources are not closed due to exceptions etc. Yet in some cases the random seeds cause the index to never be fully allocated so we basically go into a ping-pong state where we try to allocate shards back and forth on nodes. This causes all docs to time out which in-turn causes the tests to run for a very long time (hours or days). If we can not allocate the index and get to a yellow state we simply index only one doc and expected all searches to fail. This commit also beefs up the assertions in this test to check if documents are actually present if they are indexed and refresh was successful. Closes elastic#3694
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The test is trapped in an infinite loop for some seeds. This causes the test log to fill and finally an oom when running the full suite. The following seeds reproduce this:
6D1FE72CC0B92909
843B52FFCF8E5B33
6F9CC4362D6D82CB
The text was updated successfully, but these errors were encountered: