Briefly, this error occurs when Elasticsearch fails to move a blob (binary large object) within a container, possibly due to insufficient permissions or storage space. To resolve this, you can check if the Elasticsearch process has the necessary permissions to perform the operation. If permissions are not the issue, check if there’s enough storage space in the destination. If the problem persists, it could be due to a bug in Elasticsearch, in which case you should consider updating to the latest version.
This guide will help you check for common problems that cause the log ” can not move blob [{}] to [{}] in container {{}}: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, cloud-aws, cloud-azure, container and plugins.
Log Context
Log “can not move blob [{}] to [{}] in container {{}}: {}” classname is AzureBlobContainer.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
blobStore.moveBlob(blobStore.container(); source; target);
} catch (URISyntaxException e) {
logger.warn("can not move blob [{}] to [{}] in container {{}}: {}"; sourceBlobName; targetBlobName; blobStore.container(); e.getMessage());
throw new IOException(e);
} catch (StorageException e) {
logger.warn("can not move blob [{}] to [{}] in container {{}}: {}"; sourceBlobName; targetBlobName; blobStore.container(); e.getMessage());
throw new IOException(e);
}
}
Override
