Swift3 is not write affinity aware, that causes multipart upload failed in `404 (NoSuchKey)`
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Swift3 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Here is the flow I tested.
1. Enable write affinity
2. Stop all object-replicator on each node
3. Do a multipart upload
$ s3cmd put test.zip s3://test/
upload: 'test.zip' -> 's3://test/
5242880 of 5242880 100% in 0s 7.23 MB/s done
upload: 'test.zip' -> 's3://test/
5242880 of 5242880 100% in 0s 6.49 MB/s done
upload: 'test.zip' -> 's3://test/
5242880 of 5242880 100% in 0s 9.58 MB/s done
upload: 'test.zip' -> 's3://test/
5242880 of 5242880 100% in 0s 7.55 MB/s done
upload: 'test.zip' -> 's3://test/
5242880 of 5242880 100% in 0s 6.76 MB/s done
upload: 'test.zip' -> 's3://test/
5242880 of 5242880 100% in 0s 7.84 MB/s done
upload: 'test.zip' -> 's3://test/
2097152 of 2097152 100% in 0s 4.72 MB/s done
ERROR: S3 error: 404 (NoSuchKey): The specified key does not exist.
Here is detail logs from s3cmd and swift.
Patch: https:/ /review. openstack. org/#/c/ 368264/ 2