You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the problem including expected versus actual behavior:
When taking a snapshot (using an s3 repository), one of my shards is being snapshotted extremely slowly compared to the other shards in the index (and they are of comparable size). I've tried deleting the snapshot and trying again, but the problem persists.
Provide logs (if relevant):
Here is the output of GET /_snapshot/snapshot_prod/snapshot_16/_status (node shard 2 in "prod"):
It continues to snapshot more bytes each time I re-run the _status command, but the # changes extremely slowly, so I want to make sure nothing is wrong with this node. Happy to provide more info & log output as necessary.
Thanks!
The text was updated successfully, but these errors were encountered:
@joshreback for whatever reason (custom routing, perhaps?) this shard is more than 10 times larger than other 2 shards. Shard 0 is 4g, shard 1 is 6g and shard 2 is 78g. It takes time to snapshot 78g. If your node is in AWS and has good network connection you can try changing throttling, but be careful not to overload the nodes in your cluster.
Elasticsearch version:
1.6.0
JVM version:
1.8.0_45-internal
Description of the problem including expected versus actual behavior:
When taking a snapshot (using an s3 repository), one of my shards is being snapshotted extremely slowly compared to the other shards in the index (and they are of comparable size). I've tried deleting the snapshot and trying again, but the problem persists.
Provide logs (if relevant):
Here is the output of
GET /_snapshot/snapshot_prod/snapshot_16/_status
(node shard 2 in "prod"):It continues to snapshot more bytes each time I re-run the
_status
command, but the # changes extremely slowly, so I want to make sure nothing is wrong with this node. Happy to provide more info & log output as necessary.Thanks!
The text was updated successfully, but these errors were encountered: