Details
-
Bug
-
Resolution: Resolved
-
Critical
-
6.5.1, 6.6.0, 6.6.1, 6.6.2, 6.5.2, 6.5.0, 6.6.3, 6.6.4, 6.6.5, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.1.0, 7.1.1, 7.1.2
-
Security Level: Public
-
Triaged
-
1
-
No
Description
Saw this while trying to restore a bucket on Capella provisioned cluster. Opened ticket when the restore failed, and Capella Support explained that this is what they see in the logs:
{"error":"failed to execute cluster operations: failed to execute bucket operation for bucket 'bucket1': failed to transfer bucket data for bucket 'bucket1': failed to transfer restrictions: failed to set data movement restrictions: The data being transferred uses lww based conflict resolution, but the target bucket `bucket2` uses seqno based conflict resolution","stats":{"started_at":1666044466559840248,"complete":false}}
|
I was able to repro on my desktop using 7.1.2-3420 :
1. Create bucket1 with timestamp conflict resolution, full eviction, memory quota=100.
|
|
|
2 Backup:
|
cbbackupmgr config -a /Users/hyun-ju.vega/cb_backups_20221018 -r testrepo1
|
cbbackupmgr backup -a /Users/hyun-ju.vega/cb_backups_20221018 -r testrepo1 -c localhost -u Administrator -p password
|
|
|
3. Restore using --map-data and --auto-create-buckets -- restore fails:
|
cbbackupmgr restore -a /Users/hyun-ju.vega/cb_backups_20221018 -r testrepo1 -c localhost -u Administrator -p password --map-data bucket1=bucket2 --auto-create-buckets
|
|
|
Restoring backup '2022-10-18T16_33_13.670733-07_00'
|
Checking for data movement restrictions from bucket 'bucket1' to 'bucket2' 7303 items / 2.87MiB
|
[============================================= ] 33.49%
|
Error restoring cluster: The data being transferred uses lww based conflict resolution, but the target bucket `bucket2` uses seqno based conflict resolution
|
|
|
4. Checking bucket2 -- the memory quota was created with 100, and it was created with full eviction (like bucket1), but the conflict resolution was created with seqno, even though the conflict resolution of bucket1 was timestamp.
|
Issue: When using --auto-create-buckets, the conflict resolution of the auto-created bucket should match the conflict resolution of the bucket being restored.
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
