Achieving 100% consitency
jlangevin at loomlearning.com
Tue Aug 30 14:56:52 EDT 2011
Agreed, if your intention is to grow the existing single-node instance into
a multi-node cluster, then yes, that's a problem.
For our own development environment, we run a single-node instance for our
current stage of development, then once our app is more stable, we'll drop
that single-node instance and create a proper 3+ node cluster for a dev
environment that will look closer to the final production setup.
* Jonathan Langevin
Wilmington, NC: (910) 241-0433 - jlangevin at loomlearning.com -
www.loomlearning.com - Skype: intel352 *
On Tue, Aug 30, 2011 at 2:24 PM, Scott Lystig Fritchie <
fritchie at snookles.com> wrote:
> Jonathan Langevin <jlangevin at loomlearning.com> wrote:
> jl> Even for development-purposes only? Otherwise it seems data would be
> jl> written n times to the same machine, which is needless in a dev
> jl> environment with low storage specs...
> ... which would be true until the 1-node cluster grows to a 2-node or
> N-node cluster. Changing the N value of a key that already exists,
> especially where N is increasing relative to its old value, creates many
> different kinds of unpleasantness.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users