alextes opened a new issue, #138: URL: https://github.com/apache/arrow-rs-object-store/issues/138
**Describe the bug** Our service sometimes hits a conflict while putting. We'd like to retry, the lib offers an option, but it appears a 409 response is not retried. First it'd be fair to ask, should 409 generally be retried? For us the error literally says to do so, but perhaps in the general case it makes less sense. If it does make sense, it'd be lovely to have this feature. We're having to retry manually now. Not the worst, but definitely more complex than then simple `.with_retry(RetryConfig::default())` ``` Generic S3 error: response error "<?xml version='1.0' encoding='UTF-8'?> <Error><Code>OperationAborted</Code><Message>A conflicting conditional operation is currently in progress against this resource. Please try again.</Message><RequestId>tx29de9421407d406eb7588-0064f72112</RequestId></Error>", after 0 retries: HTTP status client error (409 Conflict) for url (https://s3.gra.perf.cloud.ovh.net//block-submission-archive-prod/2023/09/05/12/29/7257748/0x26c152f988d9b3c47d5cbb0cf5571981b9684501df4713a8e0c18881a7124cdc.json.gz) Caused by: 0: response error "<?xml version='1.0' encoding='UTF-8'?> <Error><Code>OperationAborted</Code><Message>A conflicting conditional operation is currently in progress against this resource. Please try again.</Message><RequestId>tx29de9421407d406eb7588-0064f72112</RequestId></Error>", after 0 retries: HTTP status client error (409 Conflict) for url (https://s3.gra.perf.cloud.ovh.net//block-submission-archive-prod/2023/09/05/12/29/7257748/0x26c152f988d9b3c 47d5cbb0cf5571981b9684501df4713a8e0c18881a7124cdc.json.gz) 1: HTTP status client error (409 Conflict) for url (https://s3.gra.perf.cloud.ovh.net//block-submission-archive-prod/2023/09/05/12/29/7257748/0x26c152f988d9b3c47d5cbb0cf5571981b9684501df4713a8e0c18881a7124cdc.json.gz ``` **To Reproduce** Store an item which is already in the process of being stored. **Expected behavior** Retry 409. **Additional context** - -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
