On 2015/07/21 11:45, Nikolaus Rath wrote:
On Jul 15 2015, Motomura Shinichi <[email protected]> wrote:
On 2015/07/15 0:43, Nikolaus Rath wrote:
On Jul 14 2015, Motomura Shinichi <[email protected]> wrote:
S3ql is offen crached when the same file "s3ql_data_593221" tried to delete.
Is it a bug of s3ql?
[...]>
The debug log is shown below.
First delete method is timed out.
Then s3ql retries delete method, but s3ql_data_636800 is deleted by
first delete method.
Indeed, I can confirm that s3ql_data_636800 is deleted in swift
backend by first delete method.
In this case the solution is easy. Either speed up your backend, or
increase the tcp-timeout in S3QL.
Thank you.
I try to set tcp-timeout option.
Would you mind trying out the attached patch (while setting tcp-timeout
back to the smaller value)? This should cause S3QL to ignore 404 when
deleting objects if and only if there have been prior attempts to delete
the object.
Thank you for providing this patch.
I am running the s3ql with this patch.
I
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
