If your cluster is large enough to guarantee your N value (e.g. N=3 requires 5 nodes) then you can just remove one node at a time from the cluster (riak admin leave), re-install the node with the new backend options, and re-join the cluster. In between these updates you then need to wait for all transfers to finish.
Alternatively, if you have an extra machine to spare, you can use "riak-admin cluster replace" to transfer data from an existing node to a new node. When that command completes (some time after commit) all data is transferred and the original node has left the cluster. This options would be much faster because you avoid the extra transfers and partition reshuffling, but needs an extra machine. Kresten Trifork On Sep 28, 2012, at 12:59 PM, Venki Yedidha <[email protected]<mailto:[email protected]>> wrote: Hi All, How to migrate from bitcask to eleveldb with out losing data from bitcask? Thanks, Venkatesh _______________________________________________ riak-users mailing list [email protected]<mailto:[email protected]> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com Mobile: + 45 2343 4626 | Skype: krestenkrabthorup | Twitter: @drkrab Trifork A/S | Margrethepladsen 4 | DK- 8000 Aarhus C | Phone : +45 8732 8787 | www.trifork.com<http://www.trifork.com> _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
