[CI Failure] DateHistogramOffsetTests.singleValue_WithPreOffset_MinDocCount

[markharwood]

http://build-us-1.elasticsearch.org/job/es_core_1x_regression/803/

REPRODUCE WITH  : mvn clean test -Dtests.seed=76338BDFEAB372C -Dtests.class=org.elasticsearch.search.aggregations.bucket.DateHistogramOffsetTests -Dtests.prefix=tests -Dfile.encoding=UTF-8 -Duser.timezone=Europe/Berlin -Dtests.method="singleValue_WithPreOffset_MinDocCount" -Des.logger.level=DEBUG -Dtests.nightly=false -Dtests.heap.size=512m -Dtests.processors=8
Throwable:
java.lang.AssertionError: 
Expected: <5L>
     got: <4L>

    __randomizedtesting.SeedInfo.seed([76338BDFEAB372C:95FAB45878660D92]:0)
    [...org.junit.*]
    org.elasticsearch.search.aggregations.bucket.DateHistogramOffsetTests.singleValue_WithPreOffset_MinDocCount(DateHistogramOffsetTests.java:124)
    [...sun.*, com.carrotsearch.randomizedtesting.*, java.lang.reflect.*]
    org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)

[markharwood]

Looks like it might be down to failure to create a shard:

Failed to create shard, message [IndexShardCreationException[[idx2][3] failed to create shard]; 
nested: LockObtainFailedException[Can't lock shard [idx2][3], timed out after 5000ms        

[markharwood]

A round up of related issues - "Lock obtain" issues of this form:

org.apache.lucene.store.LockObtainFailedException: Can't lock shard [test][0], timed out after 0ms

are found in the following test results (grouped by issues raised so far):

#8533 :
http://build-us-1.elasticsearch.org/job/es_core_1x_regression/803/

#8523 :
http://build-us-1.elasticsearch.org/job/es_core_master_centos/1374/

#8522 :
http://build-us-1.elasticsearch.org/job/es_bwc_1x/4950/

#8515 :
http://build-us-1.elasticsearch.org/job/es_core_master_metal/5354/

#8514 :
http://build-us-1.elasticsearch.org/job/es_core_master_metal/5324/

#8511 :
http://build-us-1.elasticsearch.org/job/es_bwc_1x/4941/
http://build-us-1.elasticsearch.org/job/es_bwc_1x/4967/

#8509 :
http://build-us-1.elasticsearch.org/job/es_core_master_debian/2402/
http://build-us-1.elasticsearch.org/job/es_core_master_window-2008/603/

#8505
http://build-us-1.elasticsearch.org/job/es_core_master_metal/5320/

[s1monw]

this was likely caused by the shard locking issues that are now resovled