Vagrant (https://github.com/basho/vagrant-riak-cluster) will probably be not so great for performance but you won't notice that until you need too (map reduce will suck). Once your cluster needs grow, migrating your nodes to physical boxes shouldn't be hard. Consider and uneven split on 2 boxes (3/2).
On Fri, Jan 3, 2014 at 5:19 PM, Patrick Tuckey <patrick.tuc...@gmail.com>wrote: > Thanks Kartik, I will check out docker/vagrant! > > > On Fri, Jan 3, 2014 at 11:08 AM, Kartik Thakore <kthak...@scratchd.ca>wrote: > >> Hey Patrick, >> I have done this in the past. I would recommend using docker/vagrant to >> separate each node on the clusters. Additionally us a different port scheme >> for (8098 vs.s 9098) for each nodes. >> >> The biggest problem I have had was sys admins accidentally merging >> different clusters. >> >> >> On Fri, Jan 3, 2014 at 1:14 PM, Patrick Tuckey >> <patrick.tuc...@gmail.com>wrote: >> >>> Has anyone had experience running multiple clusters on the same host(s)? >>> >>> We have two distinct data sets that we'd like to keep in riak, but one >>> of them is more experimental, so we'd like to run them as separate >>> clusters. That being said, it would be preferable to use the same hardware >>> if we can. >>> >>> I see that it's described here in the docs: >>> >>> http://docs.basho.com/riak/latest/ops/building/basic-cluster-setup/#Multiple-Clusters-on-One-Host >>> >>> But was curious if there were any gotchas with running that in a >>> production environment. >>> >>> Thanks, >>> Patrick >>> >>> _______________________________________________ >>> riak-users mailing list >>> riak-users@lists.basho.com >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >>> >>> >> >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
