Not yet, but I'll keep an eye on the backup-push output. On Wed, Jan 21, 2015 at 12:23 PM, Daniel Farina <[email protected]> wrote:
> On Wed, Jan 21, 2015 at 6:55 AM, Brian Scholl <[email protected]> wrote: > > Updating this thread in case anyone else finds themselves in this boat... > > > > This problem is still ongoing, here are the things I've tried: > > > > Updated kernel to 3.16.0-29 > > No change, the launchpad thread on this issue > > (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811) indicates > > that the fix in 3.14+ might be a regression but should be fixed in the > 15.04 > > release. Hopefully that fix makes its way back to LTS. > > > > WAL-E master > > No change after installing the master, but it did seem to take longer for > > the "rides the rocket" errors to start compounding. > > That's just anecdotal though, I don't have any real timings. > > > > Pool Size > > I am currently trying a backup-push using --pool-size 1. This has been > > running for 12+ hours now and has only caused the error a few times. I'm > > hoping that even if this takes a couple days I can get a complete > basebackup > > in to S3. > > > > I haven't tried using the --cluster-read-rate-limit option yet. If the > pool > > size change above doesn't pan out this option is next. My main concern > with > > this option is not having a sense of what rate to pass in so pool size > > option was a little easier to attempt. If anyone has a suggestion on > how to > > compute that number please let me know. > > Did you get a copy of that 500 you report? > -- 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.
