With uuid named segment data blobs there is no reason to ensure no overwrites are happening for these blobs when writing. On the contrary, at least on Azure this check can conflict with the SDK's retrying and cause upload failures randomly.
This commit is contained in:
parent
283a1f605c
commit
e37bfe8a5f
|
@ -2313,7 +2313,7 @@ public abstract class BlobStoreRepository extends AbstractLifecycleComponent imp
|
||||||
final String partName = fileInfo.partName(i);
|
final String partName = fileInfo.partName(i);
|
||||||
logger.trace(() ->
|
logger.trace(() ->
|
||||||
new ParameterizedMessage("[{}] Writing [{}] to [{}]", metadata.name(), partName, shardContainer.path()));
|
new ParameterizedMessage("[{}] Writing [{}] to [{}]", metadata.name(), partName, shardContainer.path()));
|
||||||
shardContainer.writeBlob(partName, inputStream, partBytes, true);
|
shardContainer.writeBlob(partName, inputStream, partBytes, false);
|
||||||
}
|
}
|
||||||
Store.verify(indexInput);
|
Store.verify(indexInput);
|
||||||
snapshotStatus.addProcessedFile(fileInfo.length());
|
snapshotStatus.addProcessedFile(fileInfo.length());
|
||||||
|
|
Loading…
Reference in New Issue