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.0 installation does not have enough disk space available due to the sizing of its provisioned volume.

You can increase the size of the volume by editing the value of the size field in the rethinkdb section of the values.yaml file that is used for deployment.

  1. Change the 1Gi default value to match the size of the rethinkdb volume for the source MSR 2.9.x system.

  2. Perform a helm upgrade.

    1. Edit the values.yaml file you used for MSR deployment, changing the rethinkdb.cluster.persistentVolume.size value to match the 2.9.x rethinkdb volume size

    2. Run the helm upgrade --values <path to values.yaml> msr msr/msr command.