Briefly, this error occurs when Elasticsearch fails to move a blob (binary large object) to a specific location within a container. This could be due to insufficient permissions, a full disk, or network connectivity issues. To resolve this, you can check and adjust the permissions, ensure there’s enough disk space, or troubleshoot network connectivity. Additionally, check the blob’s integrity to ensure it’s not corrupted.
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 :
logger.debug("moving blob [{}] to [{}] in container {{}}"; source; target; blobStore.container());
blobStore.client().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);
}
