Increase Timeout in #testSnapshotCanceled (#37890)
* The test failure reported in the issue looks like a mere timeout. Logging suggestst hat the snapshot completes/aborts correctly but the busy loop polling the snapshot state times out too early. * Closes #37888
This commit is contained in:
parent
519423b8f3
commit
0d109396fa
|
@ -3179,7 +3179,6 @@ public class SharedClusterSnapshotRestoreIT extends AbstractSnapshotIntegTestCas
|
|||
*
|
||||
* See https://github.com/elastic/elasticsearch/issues/20876
|
||||
*/
|
||||
@AwaitsFix(bugUrl = "https://github.com/elastic/elasticsearch/issues/37888")
|
||||
public void testSnapshotCanceledOnRemovedShard() throws Exception {
|
||||
final int numPrimaries = 1;
|
||||
final int numReplicas = 1;
|
||||
|
@ -3229,7 +3228,7 @@ public class SharedClusterSnapshotRestoreIT extends AbstractSnapshotIntegTestCas
|
|||
unblockNode(repo, blockedNode);
|
||||
|
||||
logger.info("--> ensuring snapshot is aborted and the aborted shard was marked as failed");
|
||||
SnapshotInfo snapshotInfo = waitForCompletion(repo, snapshot, TimeValue.timeValueSeconds(10));
|
||||
SnapshotInfo snapshotInfo = waitForCompletion(repo, snapshot, TimeValue.timeValueSeconds(60));
|
||||
assertEquals(1, snapshotInfo.shardFailures().size());
|
||||
assertEquals(0, snapshotInfo.shardFailures().get(0).shardId());
|
||||
assertEquals("IndexShardSnapshotFailedException[Aborted]", snapshotInfo.shardFailures().get(0).reason());
|
||||
|
|
Loading…
Reference in New Issue