Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 209.85.219.223 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=LmTq0izsNJ516ViiQ+BxGSwrwb1Qgm8Jipj29XI326xgyz+v9Mq/uUxOaV1jWDx+n+
         XepMx5hXBFUKQimkD1bOqI1GG0g7GIkWc2aD8Rw8kJAWV+moS3lnAlrtkP7I2+/EDsr/
         98opf56uAKZ1TEAzfAIl9MLC4wPZfpydFIJ9Y=
MIME-Version: 1.0
In-Reply-To: <c1870d60907140822y79e17ech4d95904a6e0b48a9@mail.gmail.com>
References: <c1870d60907140817i1eacb430pb275631b987564b0@mail.gmail.com>
	 <e06563880907140821s52226062hdbad355c021e3a5b@mail.gmail.com>
	 <c1870d60907140822y79e17ech4d95904a6e0b48a9@mail.gmail.com>
Date: Tue, 14 Jul 2009 10:25:26 -0500
Message-ID: <e06563880907140825x64777948q812b62c63f1f5448@mail.gmail.com>
Subject: Re: replica on in the beginning or added later
From: Jonathan Ellis <jbellis@gmail.com>
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Note that for N=2, quorum write is the same as block-for-all.  That is
why N=3 is more popular, because it allows for one node to be down but
still give you a quorum for any key.

-Jonathan

On Tue, Jul 14, 2009 at 10:22 AM, <mobiledreamers@gmail.com> wrote:
> starting with replica count 2 is more prudent thanks
>
> On Tue, Jul 14, 2009 at 8:21 AM, Jonathan Ellis <jbellis@gmail.com> wrote:
>>
>> although the repair code Stu is working on
>> (https://issues.apache.org/jira/browse/CASSANDRA-193) could handle
>> increasing the replica count, IMO there's little sense in relying any
>> more on features that don't yet exist than necessary. :)
>>
>> On Tue, Jul 14, 2009 at 10:17 AM, <mobiledreamers@gmail.com> wrote:
>> > as a followup question
>> > the items we are storing are extremely valuable and we are using
>> > cassandra
>> > as a sql replacement tool.. ie no more postgres and all data from
>> > cassandra,
>> > given cassandra scalability
>> > as we hit limits on postgres and found pgpool-II horizontal partitioning
>> > too
>> > clunky and skype, plproxy requires too much rewiring the client code.
>> > should we start with a replica factor 1 and then increase replica factor
>> > to
>> > 2
>> > or is is prudent to start with a replica factor of 2
>> > Can cassandra replicate even after running for a long time with a
>> > replica
>> > factor of 1, if we change the replica factor to say 2 after 2months when
>> > we
>> > add more nodes and figure there is enough space now to replicate
>> > thanks
>> >
>> > --
>> > Bidegg worlds best auction site
>> > http://bidegg.com
>> >
>
>
>
> --
> Bidegg worlds best auction site
> http://bidegg.com
>