There are 2 options for that situation when riak-admin cluster plan gives
you the Not all replicas will be on distinct nodes warning.
1. You can riak-admin cluster clear, which will wipe out the plan, and the
riak-admin cluster plan again. You will get the same effect of
redistributing the vnodes
Hi Toby,
The error you are seeing is a bug which I'm working to resolve. We're
currently in the process of reviewing a test to ensure against possible
regressions, [1] two bug fixes, [2] [3] and a modification to the copy to
clarify what "incompatible" means. [4]
For now, it's safe to assume tha
My bad. Thanks, go it sorted!
--
View this message in context:
http://riak-users.197444.n3.nabble.com/PB-Java-Client-API-1-4-runtime-exception-tp4028743p4028752.html
Sent from the Riak Users mailing list archive at Nabble.com.
___
riak-users mailing
Having the same problem. Still running a restore of 2.7 gb. In my case is
1M keys of 1kb average, and a dump file of 2.7Gb.
Was running for at least one day already.
The cpu in that node is 100% (seems like only one core being used).
The backup was done in another cluster with smaller instances, a
On 06/08/13 07:51, Paul Ingalls wrote:
Hope you all don't get pissed for me spamming the list….;)
I upgraded my cluster to 1.4.1 in hopes the levelDB changes may help.
The cluster is now up and running, however Riak Control is complaining:
The following nodes are currently incompatible with R
