Colin,
Yes, have seen this exact problem before.
You can hack on your /etc/hosts file to redirect the secondary to read from anyone you want. So just put a false entry in there for the server it's reading from pointing back to the primary. I think there are tickets to deal with this in the future.
-kg
On Jul 3, 2012, at 9:16 AM, Colin Howe wrote:
> We've hit the following scenario:
> X is the primary
> Y is a secondary but is struggling to keep up with the oplog and is starting to have noticable replication lag
> Z is also a secondary and has syncingTo in rs.status() set to Y... as a result Z is dropping behind too even though it is actually healthy
> Is there a way to force Z to sync to X?
> Thanks,
> Colin
> --
> Website: http://www.colinhowe.co.uk
> Twitter: http://twitter.com/colinhowe
> --
> You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb