On Tue, Oct 21, 2014 at 9:49 PM, Hunter Blanks <[email protected]> wrote: > Daniel, > > Ah. To be clear, the recovery.conf in the failing case only restore_command.
So, no standby_mode = on in recovery.conf? Can you give that a try and user the "trigger file" to come out of recovery? > Although we do use hot_standby = on when bringing up a replicated slave, so > that it can pull WAL files either by WAL-E or by streaming replication, > hot_standby is not on in the failing case. > > Thus, the only difference between the passing failing case is the addition > of "--prefetch 0" to restore_command, the only config option passed into > recovery.conf. I can see why that may happen, because of a faithful rendering of the 404 as a proper exit code rather than a bogus empty file. -- 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.
