OK, so this brings me to Plan B. (Feel free to suggest a plan C if you can.)
I want to have six nodes, three in each availability zone, replicate a
Mercurial repository. Here's some art:
[gluster c/s] [gluster c/s] | [gluster c/s] [gluster c/s]
|
[gluster
On 06/30/2010 10:22 AM, Craig Box wrote:
OK, so this brings me to Plan B. (Feel free to suggest a plan C if you can.)
I want to have six nodes, three in each availability zone, replicate a
Mercurial repository. Here's some art:
[gluster c/s] [gluster c/s] | [gluster c/s] [gluster c/s]
Hi all,
Spent the day reading the docs, blog posts, this mailing list, and
lurking on IRC, but still have a few questions to ask.
My goal is to implement a cross-availability-zone file system in
Amazon EC2, and ensure that even if one server goes down, or is
rebooted, all clients can continue,
