Hi Colin,
For clusters smaller than 5 nodes a certain amount of vnode shuffling has
been observed. The behavior you've observed seems to match bug 946:
https://issues.basho.com/show_bug.cgi?id=946
I'm not sure how much additional disk space per node would be necessary. The
example provided in the
Hi,
My bucket is using the default N=3. When writing, I am using W=1 and
when reading N=1.
My cluster has settled down now. After the addition of the 4th node,
one of the node started to use diskspace at a very rapid pace, heading
quickly toward 100% usage so I had to remove the 4th node. It took
Hi Collin,
I would not expect keys to return not found even during handoff. An
individual vnode may return not found if the requested data has not been
transferred but the other replicas should be able to satisfy the quorum.
What values of N, R, and W are you using?
Thanks,
Dan
Daniel Reverri
D
Yup, same version.
On Mon, Dec 20, 2010 at 7:58 PM, Alexander Sicular wrote:
> Did you add the same version of riak to your 0.10.1 cluster? I wouldn't
> mismatch...
>
> On Dec 20, 2010, at 3:46 PM, Colin Surprenant wrote:
>
>> Hi,
>>
>> Actually, they're not timeout error but Not Found errors fo
Did you add the same version of riak to your 0.10.1 cluster? I wouldn't
mismatch...
On Dec 20, 2010, at 3:46 PM, Colin Surprenant wrote:
> Hi,
>
> Actually, they're not timeout error but Not Found errors for a bunch
> of keys that have been stored without error while the cluster is
> rebalancin
Hi,
Actually, they're not timeout error but Not Found errors for a bunch
of keys that have been stored without error while the cluster is
rebalancing.
Is it "normal" to see Not Found errors while the cluster is
rebalancing? If not, what is my problem here? Is it a problem to
insert new keys while
