On Aug 17, 2010, at 6:23 PM, Dwight Merriman wrote:

what i am planning is use of slavedelay in set configs

but the member must be passive

e.g.

{ ...,
members: [

{ host: 'abc', priority:0, slavedelay: 7200 }

,
...
]
}

On Tue, Aug 17, 2010 at 9:13 PM, Kenny Gorman <kgorman@shutterfly.com> wrote:
Guys,

I am curious as to your advice. We want the following configuration:

• (2) hosts in replica set to fail over to each other
• (1) host with --slavedelay and will never be failed to, but I want it to read the logs from whomever is master.

What are my options here? It appears I can setup a slave against the (NOW) master, but if it fails over it doesn't understand the new master. It's 'set unaware'.

An approach would be to create a new settings option for slavedelay and allow this to be passive or perhaps mandate it's passive (could be confusing to fail over to really old data if someone wasn't on top of it).

Thanks
Kenny