Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 48286 invoked from network); 14 Jul 2009 15:23:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Jul 2009 15:23:03 -0000 Received: (qmail 91410 invoked by uid 500); 14 Jul 2009 15:23:12 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 91396 invoked by uid 500); 14 Jul 2009 15:23:12 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 91366 invoked by uid 99); 14 Jul 2009 15:23:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2009 15:23:12 +0000 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=FS_REPLICA,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mobiledreamers@gmail.com designates 209.85.132.240 as permitted sender) Received: from [209.85.132.240] (HELO an-out-0708.google.com) (209.85.132.240) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2009 15:23:01 +0000 Received: by an-out-0708.google.com with SMTP id c38so1337078ana.0 for ; Tue, 14 Jul 2009 08:22:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=2oL60tPC/trmO90rIlduvfWkmeGeIXEatelpl2OAGRM=; b=SbvYOxd5XLf4Mb2PLdZh3BHB4u+yu1iNO1amUPJtFTszDs3b4jkH/driAyFHAdEUa2 0ztO1pW5OaxoBqDdcZu+PT3rU6CLQjURU4fYL81JxD7R39Lo21y5U7xn92L71K6AnrU5 7mHOCJ/dF6OpB/MxZ1JgJRZnQapcdx5tAeNvg= 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; b=RumJShOscBBjW0QfjNcniJajsEzMwvIRHcGbZ2tjtmsdcZh7yyG03LFiB7ETOddcAA GBZLQEhf18DC0zGl7xKfY7+yMpWQhwUQAxE6YrgzQ75yg+MJGr4g917Gi+8U9tjVe0q7 z6I8zdFTawgA7zhkasxSe6lJOMAMt43ndRyT8= MIME-Version: 1.0 Received: by 10.100.133.20 with SMTP id g20mr8929020and.24.1247584960308; Tue, 14 Jul 2009 08:22:40 -0700 (PDT) In-Reply-To: References: Date: Tue, 14 Jul 2009 08:22:40 -0700 Message-ID: Subject: Re: replica on in the beginning or added later From: mobiledreamers@gmail.com To: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e6470d706352f9046eac02d1 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6470d706352f9046eac02d1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit starting with replica count 2 is more prudent thanks On Tue, Jul 14, 2009 at 8:21 AM, Jonathan Ellis 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, 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 --0016e6470d706352f9046eac02d1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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
--0016e6470d706352f9046eac02d1--