Comment 2 for bug 1889661

Revision history for this message
toto (locklock) wrote :

Hi,

thank you for your answer, and sorry for getting back to you only now, we were discussing this issue internally and testing your option.

So after few tests on our side, we are not seeing any improvement by disabling the write-affinity on the proxy servers on the 3 regions we have.

We are still seeing 20X return code on the local storage and 404 in the 2 other regions when checking the logs of the storage servers with the POST request.

We tried the write_affinity_handoff_delete_count option, without luck, as per the documentation, it only affects the PUT/DELETE requests, so no chance on this one.

To give you more informations on the issue:
- At the creation of the object, when adding the metadata immediatly after that, the POST is returning a 404.
- But after few minutes, once the object has been replicated in the 2 other regions, we are succesfully getting a 20X return code on the POST request when adding the metadata.

In order to continue our upgrade, we are thinking to ask our teams who are using this feature post_as_copy, to upload/create their object on our 3 sites in the same time, so that their POST requests won't fail when adding the metadata immediatly after the object's creation, but it looks a bit overkill just to mitigate this issue and will potentially add more load on our servers.

Surely, this object_post_as_copy feature which has been deleted may have impacted other swift' users using the multi-region feature. We are only seeing this on our side, now that we want to upgrade our swift platform unfortunately.

We have looked at the bugs you're referencing, and it looks like the same issue to me indeed. Your patch could be a good solution for us and maybe other people.

Do you have any chance to continue your work on the POST_with_write_affinity feature you were working on and an ETA ? :) or if you have any other ideas/configuration we could try to mitigate the issue while you are working on this ? So that we can wait for the feature to be added in one of the upcoming releases.

Thank you a lot in advance for your answer and help.