Apologies for the delayed reply, was trying to export from riak 1.4.8. riak 2.0 would definitely address the ring size adjustment issue but I'd still be curious as to best practices for moving data from one cluster to another that may have different configs ie new default bucket properties and what not. Thanks!
On Wed, Sep 3, 2014 at 12:22 PM, Dmitri Zagidulin <[email protected]> wrote: > Mark, > > What version Riak are you trying to export from? > > > On Tue, Sep 2, 2014 at 1:07 PM, Mark Rechler <[email protected]> wrote: > >> Hello All, >> >> What would be the best tool for moving data from one riak cluster to >> another? >> >> To give some context, we needed to change the ring_creation_size and >> build out a new cluster. >> Once the cluster was built I initially tried riak-data-migrator >> (https://github.com/basho-labs/riak-data-migrator) but that caused the >> load across the old cluster to skyrocket and the tool would time out >> before it could actually receive any data. >> >> I then attempted riak-admin backup/restore. The backup took ~ 2 days. >> The restore seemed much slower going ~ 10 megabytes/hour. Needing to >> fill 26gb/node this seemed impractical. >> >> Are there any other recommended ways to migrate data? We're using >> leveldb as the only back-end. Appreciate any help. >> >> Thanks, >> Mark >> >> -- >> Mark Rechler >> Infrastructure Engineer, Bitly >> >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> > > -- Mark Rechler Infrastructure Engineer, Bitly <http://bitly.com/> +1.201.500.8637 Twitter <http://twitter.com/bitly> | Facebook <http://facebook.com/bitly>
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
