potential data loss in Cassandra 1.1.0 .. 1.1.4

I wanted to call out a particularly important bug for those who aren't in the habit of reading CHANGES. Summary: the bug was fixed in 1.1.5, with an follow-on fix for 1.1.6 that only affects users of 1.1.0 .. 1.1.4. Thus, if you upgraded from 1.0.x or earlier directly to 1.1.5, you're okay as far

Re: EOFException with BulkOutputFormat in 1.1.6

Apologies - looks like this is already being tracked in https://issues.apache.org/jira/browse/CASSANDRA-4813 From: Michael Kjellman mailto:mkjell...@barracuda.com>> Reply-To: "user@cassandra.apache.org" mailto:user@cassandra.apache.org>> Date: Wednesday, October

EOFException with BulkOutputFormat in 1.1.6

I'm getting EOFExceptions with BulkOutputFormat 2012-10-17 12:23:01,182 ERROR org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor: Error in ThreadPoolExecutor java.lang.RuntimeException: java.io.EOFException at org.apache.cassandra.utils.FBUtilities.unchecked(FBUtilities.java:628) at or

Re: Cassandra nodes loaded unequally

Some of your column families are not fully compacted. But it is pretty normal, I would not worry about it. Eventually it should happen. On Wed, Oct 17, 2012 at 1:46 AM, Alain RODRIGUEZ wrote: > I've got the same problem, and other people in the mailing list are > reporting the same issue. > > I d

Re: run repair on each node or every R nodes?

> > In my mind it does make sense, and what you're saying is correct. But I read > that it was better to run repair in each node with a "-pr" option. > > Alain > Yes, it's correct. Running repair -pr on each node you repair whole cluster without job duplication. Andrey

Re: Missing non composite column

> Yes, i understand that. Reason why i am asking is, with this i need to split > them to get actual column name using ":" as a seperator. > Though i did not try it yet, but wondering if column name is like > "alliance:movement", then how do it compute it? You've lost me, sorry. -- Sylvain > > >

Re: Astyanax empty column check

What specifically are you trying to achieve? The business requirement might help as there are other ways of solving it such that you do not need to know the difference. Dean From: Xu Renjie mailto:xrjxrjxrj...@gmail.com>> Reply-To: "user@cassandra.apache.org"

Re: RF update

Follow up question: Is it safe to abort the compactions happening after node repair? On Mon, Oct 15, 2012 at 6:32 PM, Will Martin wrote: > +1 It doesn't make sense that the xfr compactions are heavy unless they > are translating the file. This could be a protocol mismatch: however the > require

Re: Astyanax empty column check

So what you mean is essentially there is *no* way to differentiate it because what they "appear" is the same? On Wed, Oct 17, 2012 at 5:58 PM, rohit bhatia wrote: > See > "If you attempt to retrieve an entire row and it returns a result with > no columns, it effectively means that row does not e

Firebrand Object Mapper Library for Cassandra

Hello All, Just wanted to announce a new Open Source Object Mapping and Client library for Cassandra that we have recently released at 47 Degrees. Firebrand OCM is a simple library for persisting and querying Java Objects to Cassandra. Among other features it includes a CQL query builder. The c

Re: run repair on each node or every R nodes?

what if first node in range is down? then -pr would be ineffective

Re: run repair on each node or every R nodes?

"I see. So if I don't use the '-pr' option, triggering repair on node-00 is sufficient to repair the first 3 nodes. No need to cron a repair on node-{01,02}. correct?" "forget it. this was nonsense." In my mind it does make sense, and what you're saying is correct. But I read that it was better t

Re: Astyanax empty column check

See "If you attempt to retrieve an entire row and it returns a result with no columns, it effectively means that row does not exist." Essentially a row without columns doesn't exist.. (except those with tombstones) from here http://stackoverflow.com/questions/8072253/is-there-a-difference-between-

Re: Astyanax empty column check

Sorry for the version, I am using 1.0.1 Astyanax. On Wed, Oct 17, 2012 at 4:44 PM, Xu Renjie wrote: > hello guys, >I am currently using Astyanax as a client(new to Astyanax). But I am > not clear how to differentiate the following 2 situations: > a. A row which has only key without columns >

Re: Cassandra nodes loaded unequally

I've got the same problem, and other people in the mailing list are reporting the same issue. I don't know what is happening here. RF 2, 2 nodes : 10.59.21.241eu-west 1b Up Normal 137.53 GB 50.00% 0 10.58.83.109eu-west 1b Up Normal 102.46

Astyanax empty column check

hello guys, I am currently using Astyanax as a client(new to Astyanax). But I am not clear how to differentiate the following 2 situations: a. A row which has only key without columns b. No this row in database. Since when I use RowQuery to query Cassandra with given key, both the above two sit

Re: Missing non composite column

Yes, i understand that. Reason why i am asking is, with this i need to split them to get actual column name using ":" as a seperator. Though i did not try it yet, but wondering if column name is like "alliance:movement", then how do it compute it? On Wed, Oct 17, 2012 at 1:04 PM, Sylvain Lebresne

Re: Missing non composite column

On Wed, Oct 17, 2012 at 3:17 AM, Vivek Mishra wrote: > column name will be "2012-07-24:2:alliance_involvement" or > "alliance_involvement"? The former. Though let's clarify that "2012-07-24:2:alliance_involvement" is the string representation of a composite name (i.e. one compatible with Composit