On Fri, Mar 14, 2014 at 2:47 PM, David Weaver <[email protected]> wrote: > No, my problem is entirely with AWS machines that are in the same region as > the S3 bucket. I have been running WAL-E from us-west-2 (Oregon) machines on > an Oregon S3 bucket and failing until I switch to US Standard.
That is also good data, because I was thinking that there may have some kind of starvation issue in WAL-E that caused S3 to give up on the connection and complain at you. Maybe that is indeed the case, but your impression that US-Standard does the job differently suggests it's not universal to S3 or your connection (US-Standard has looser timeouts or something). I think this is worth a report to AWS support. You may want to reference this thread. -- You received this message because you are subscribed to the Google Groups "wal-e" 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.
