Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion How to configure geo-redundant hidden replica to become primary?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Bob Grabar  
View profile  
 More options Nov 14 2012, 2:09 pm
From: Bob Grabar <bob.gra...@10gen.com>
Date: Wed, 14 Nov 2012 11:09:12 -0800 (PST)
Local: Wed, Nov 14 2012 2:09 pm
Subject: Re: How to configure geo-redundant hidden replica to become primary?

Bernardo, Are you still looking for answers, and if so, do you have five
members total (2 r/w, 2 hidden/0, 1 arbiter)? -Bob

On Wednesday, October 17, 2012 10:35:28 AM UTC-4, Bernardo wrote:

> I have a MongoDB replica set in EC2, most of which is located on the East
> coast.
> Two read/write nodes, one hidden zero-priority 4hour delay node for backup
> purposes, and one arbiter.
> I just added a 4th hidden zero-priority node in a West Coast EC2 zone. I
> would like to prevent any reads from it (hidden) and I would like to
> prevent it from becoming primary unless the entire East Coast replica is
> down. Currently with 0-priority it's never going to go primary unless I
> manually go in and change it.

> Suggestions?

> I might possibly need to add an arbiter on the West Coast as well?

> Thanks!


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.