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
codership
Home
+ new post
About this group
Join this group
Message from discussion Avoiding NON-PRIMARY situation in 2-node dpeloyment
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
 
Henrik Ingo  
View profile  
 More options Apr 4 2012, 2:22 pm
From: Henrik Ingo <henrik.i...@avoinelama.fi>
Date: Wed, 4 Apr 2012 21:22:39 +0300
Local: Wed, Apr 4 2012 2:22 pm
Subject: Re: [codership-team] Avoiding NON-PRIMARY situation in 2-node dpeloyment
Print | View thread | Show original | Report this message | Find messages by this author

On Wed, Apr 4, 2012 at 4:06 PM, SyRenity <stas.os...@gmail.com> wrote:

> So as long as we make sure that node B connects node A (and not the other
> way around) and gets full SST, this option is safe to use. Correct?

But always remember that's quite a big if :-) The reason people want true
syncronous replication like galera provides (with 3 nodes) is that we make
human errors all the time, and then A and B are screwed.

henrik

--
henrik.i...@avoinelama.fi
+358-40-8211286 skype: henrik.ingo irc: hingo
www.openlife.cc

My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559


 
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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google