> What happened is this:
> You started your cluster with only one node, so at first, all data was on
> this.
> Then you added a second node. Cassandra then moved (approximatively)
> half of the data to the second node. In theory, at that
> point the data that was moved to the second node could be
ect?
>
> -Original Message-
> From: Sylvain Lebresne [mailto:sylv...@datastax.com]
> Sent: Friday, March 25, 2011 3:01 AM
> To: user@cassandra.apache.org
> Cc: Jared Laprise
> Subject: Re: URGENT HELP PLEASE!
>
> On Fri, Mar 25, 2011 at 1:49 AM, Jared Lap
atastax.com]
> Sent: Friday, March 25, 2011 3:01 AM
> To: user@cassandra.apache.org
> Cc: Jared Laprise
> Subject: Re: URGENT HELP PLEASE!
>
> On Fri, Mar 25, 2011 at 1:49 AM, Jared Laprise wrote:
>> Hello all, I'm running 2 Cassandra 6.5 nodes and I brought down the
ain Lebresne [mailto:sylv...@datastax.com]
Sent: Friday, March 25, 2011 3:01 AM
To: user@cassandra.apache.org
Cc: Jared Laprise
Subject: Re: URGENT HELP PLEASE!
On Fri, Mar 25, 2011 at 1:49 AM, Jared Laprise wrote:
> Hello all, I'm running 2 Cassandra 6.5 nodes and I brought down the
&
On Fri, Mar 25, 2011 at 1:49 AM, Jared Laprise wrote:
> Hello all, I’m running 2 Cassandra 6.5 nodes and I brought down the
> secondary node and restarted the primary node. After Cassandra came back up
> all data has been reverted to several months ago.
Out of curiosity, when you said 'brought do
> Based on what you're saying, and being I'm using session (cookie) based load
> balancing it would be true that data is rarely read or written (per user) on
> a different server, that could be why data isn't replicating.
You've probably discovered this already but just in case, and for
others f
On Thu, Mar 24, 2011 at 11:58 PM, Jared Laprise wrote:
> My replication factor is 1
>
Then you are living dangerously.
> I haven't run repair until today, I'm using ONE for consistency level.
>
Repair at rf=1 won't do anything.
I have two servers that are load balanced (per session) which bo
" moment, and didn't have the time to Google it myself :-)
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Thursday, March 24, 2011 9:49 PM
To: user@cassandra.apache.org
Cc: Jared Laprise; aaron morton
Subject: Re: URGENT HELP PLEASE!
Each row is replicat
of Cassandra and especially related to multi-node
deployments. Thanks!
-Original Message-
From: Benjamin Coverston [mailto:ben.covers...@datastax.com]
Sent: Thursday, March 24, 2011 8:59 PM
To: user@cassandra.apache.org
Subject: Re: URGENT HELP PLEASE!
Hi Jared,
Sounds like you have two
ginal Message-
> From: Jonathan Ellis [mailto:jbel...@gmail.com]
> Sent: Thursday, March 24, 2011 8:22 PM
> To: user@cassandra.apache.org
> Cc: aaron morton
> Subject: Re: URGENT HELP PLEASE!
>
> Right, Cassandra doesn't keep old versions around so to see an old version
l.com]
Sent: Thursday, March 24, 2011 8:22 PM
To: user@cassandra.apache.org
Cc: aaron morton
Subject: Re: URGENT HELP PLEASE!
Right, Cassandra doesn't keep old versions around so to see an old version you
have to have uncompacted data and whack the new data -- either by blowing away
sstab
nment.
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Thursday, March 24, 2011 8:22 PM
To: user@cassandra.apache.org
Cc: aaron morton
Subject: Re: URGENT HELP PLEASE!
Right, Cassandra doesn't keep old versions around so to see an old version you
have to have uncompacte
Right, Cassandra doesn't keep old versions around so to see an old
version you have to have uncompacted data and whack the new data --
either by blowing away sstables or not replaying the commitlog.
Snapshots flush before creating their hard links, which rules out any
commitlog problems.
If you r
Was there anything in the server logs during startup ?
I've not heard of this happening before and it's hard think of how / why
cassandra could revert it's data. Other than something external playing with
the files on disk
Aaron
On 25 Mar 2011, at 13:49, Jared Laprise wrote:
> Hello all, I’m
14 matches
Mail list logo
