I was told, on a tip from a fellow engineer, to switch my S3 bucket from the "Oregon" region (which I had been using) to the "US Standard" one. Sure enough, that worked, and I no longer see the "[Errno 104] Connection reset by peer" errors from my WAL-E operations.
I don't think this is a CPU issue (as a medium-sized instance should be plenty powerful for something like this), but one related to the S3 region. At least in my case, this distinction was essential to my being able to use WAL-E at all - perhaps it's worth at least a mention in the documentation? Dave On Thu, Mar 13, 2014 at 5:53 PM, Daniel Farina <[email protected]> wrote: > On Thu, Mar 13, 2014 at 11:48 AM, <[email protected]> wrote: > > Has there been any definitive solution to this? I'm running into the > exact > > same problem on an m1.medium, which I'd think would have enough > horsepower > > for this. I am running WAL-E 0.6.9. > > Perhaps consider v0.7b2. I greatly improved reduced the CPU used to > do anything. I've been burning it in for a while, now and I'm > thinking about re-casting it as an RC. > -- 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.
