rethinkdb row cannot be restored¶
During the Restore stage of the migration workflow, you may encounter an error message that indicates an issue with rethinkdb row restoration:
Can't restore rethinkdb row: rethinkdb: Cannot perform write: lost contact with primary replica in:\n<rethink-db-statement>
The error is reported when the rethinkdb Pod for the destination MSR 3.x installation does not have enough disk space available due to the sizing of its provisioned volume.
To increase volume size using the MSR Operator:
Edit the custom resource manifest, changing the
rethinkdb.cluster.persistentVolume.sizevalue to match the source RethinkDB volume size.
Apply the changes to the custom resource:
kubectl apply -f cr-sample-manifest.yaml
Verify completion of the reconciliation process for the custom resource:
kubectl get msrs.msr.mirantis.com kubectl get rethinkdbs.rethinkdb.com
To increase volume size using a Helm chart:
values.yamlfile you used for MSR deployment, changing the
rethinkdb.cluster.persistentVolume.sizevalue to match the source RethinkDB volume size
Run the helm upgrade --values <path to values.yaml> msr msr/msr command.
The error is reported when the node on which RethinkDB is running on the target MSR system does not have enough available disk space.
SSH into the node on which RethinkDB is running.
Review the amount of disk space used by the docker daemon on the node:
docker system df
Review the total size and available storage of the node filesystem:
Allocate more storage to the host machine on which the target node is running.