Saw what I think is strange replication/failover behavior while testing out
a cluster with two nodes. My cluster is running defaults and maps simple
keys to byte payloads. I saw this sequence of events:
1) Query for key "X". Receive the correct value "Y" as expected.
2) Shut down node #1. Que
Ah, yes. So with 1 node, I had a guaranteed 3 copies of the data, and when
I added another node, some of those got reduced to 1 or 2 on that node. I
understand now, thanks.
Jimmy
On Thu, May 13, 2010 at 11:34 AM, Justin Sheehy wrote:
> Hi, Jimmy.
>
> With an n_val of 3, there will be 3 copies
Hi, Jimmy.
With an n_val of 3, there will be 3 copies of each data item in the
cluster even when there are less than 3 hosts. With 2 nodes in that
situation, each node will have either 1 or 2 copies of each item.
Does that help with your understanding?
-Justin
_
Hi all,
I just added another node to my cluster (moving from 1 to 2) and was
surprised by some behavior.
As I understand replication, with an n_val of 3 (default), all nodes will
have all data until I add my 4th node. First, is this right?
Second, I watched my disk usage on node 1 go from 1GB t
