Increase keep alive of point in time in async search tests (#62593)

Async search tests can take more than one minute due to the excessive trace logs. 
And the point in time in the tests can be expired the midway.

Closes #62451
This commit is contained in:
Nhat Nguyen 2020-09-18 07:47:45 -04:00
parent 4c949b0869
commit 8bea6b3711
2 changed files with 1 additions and 5 deletions

View File

@ -19,7 +19,6 @@ import org.elasticsearch.search.aggregations.metrics.InternalMax;
import org.elasticsearch.search.aggregations.metrics.InternalMin;
import org.elasticsearch.search.builder.SearchSourceBuilder;
import org.elasticsearch.test.ESIntegTestCase.SuiteScopeTestCase;
import org.elasticsearch.test.junit.annotations.TestIssueLogging;
import org.elasticsearch.xpack.core.XPackPlugin;
import org.elasticsearch.xpack.core.search.action.AsyncSearchResponse;
import org.elasticsearch.xpack.core.search.action.SubmitAsyncSearchRequest;
@ -41,9 +40,6 @@ import static org.hamcrest.Matchers.lessThan;
import static org.hamcrest.Matchers.lessThanOrEqualTo;
@SuiteScopeTestCase
@TestIssueLogging(
value = "org.elasticsearch.index:TRACE,org.elasticsearch.env:TRACE",
issueUrl = "https://github.com/elastic/elasticsearch/issues/56765")
public class AsyncSearchActionIT extends AsyncSearchIntegTestCase {
private static String indexName;
private static int numShards;

View File

@ -231,7 +231,7 @@ public abstract class AsyncSearchIntegTestCase extends ESIntegTestCase {
OpenPointInTimeRequest openPIT = new OpenPointInTimeRequest(
new String[]{indexName},
OpenPointInTimeRequest.DEFAULT_INDICES_OPTIONS,
TimeValue.timeValueMinutes(between(1, 5)),
TimeValue.timeValueMinutes(between(5, 10)),
null,
null);
pitId = client().execute(OpenPointInTimeAction.INSTANCE, openPIT).actionGet().getSearchContextId();