Open jlewis-spotnana opened 3 weeks ago
Here's the full '--state run' command
./cqlreplicator --state run --region $AWS_REGION \
--landing-zone s3://bucket-name \
--tiles 2 --replication-stats-enabled \
--src-keyspace XXX --src-table YYY \
--trg-keyspace ZZZ --trg-table YYY \
--json-mapping '{"keyspaces": { "readBeforeWrite": true}}'
@jlewis-spotnana
Thanks @nwheeler81 . I copied head to tail as suggested, and cqlreplicator is running again!
What is the affect of copying head to tail in this manner? Is there any risk of losing data when doing this?
@jlewis-spotnana there is no risk of losing data, but you will have one idle cycle from the discovery Glue job.
Describe the bug After restarting cqlreplicator, the DISCOVERY job fails with the following error:
The table structure has not changed, so I assume some corruption in cqlreplicator's tracking data (in S3 or the migration.ledger table).
To Reproduce This issue is sporadic. I believe it was caused by the following steps:
./cqlreplicator --state run ...
Expected behavior I expect cqlreplicator to restart and continue replication from where it left off.
Screenshots n/a
Additional context This may be related to https://github.com/aws-samples/cql-replicator/issues/112