We are seeing the exact same exception in our logs. Is there any workaround?
We never delete rows but we do a lot of updates. Is that where the
tombstones are coming from?
On Wed, Dec 25, 2013 at 5:24 PM, Sanjeeth Kumar wrote:
> Hi all,
> One of my cassandra nodes crashes with the following ex
On Mon, Jan 13, 2014 at 12:26 PM, Jacob Rhoden wrote:
> I would use them if I *really* needed them *and* had done comprehensive
> testing with real life usage patterns to ensure nothing unexpected happens.
>
... *and* were willing to accept the risk that they could completely and
totally change,
Sorry, I thought I was running the latest version, but it was on this
instance...
[cqlsh 4.1.0 | Cassandra 2.0.1-SNAPSHOT | CQL spec 3.1.1 | Thrift protocol
19.37.0]
I tried with 2.0.4 and it works just fine.
On Mon, Jan 13, 2014 at 9:07 PM, Huang, Roger wrote:
> Validimir,
>
> Thanks what v
I would use them if I really needed them and had done comprehensive testing
with real life usage patterns to ensure nothing unexpected happens.
I would call it "beta" in the google sense of the word "beta".
__
Sent from iPhone
> On 14 Jan 2014, at 5:29 am, Robert Col
Validimir,
Thanks what version of Cassandra?
-Roger
From: Vladimir Prudnikov [mailto:v.prudni...@gmail.com]
Sent: Monday, January 13, 2014 11:57 AM
To: user
Subject: Problem inserting set when query contains IF NOT EXISTS.
Hi all,
I've spend a lot of time finding a bug in system, but it turns ou
On Sat, Jan 11, 2014 at 11:40 AM, Vidit Asthana wrote:
> I know that triggers are still experimental but I want to know if they are
> prod ready? If not when will it be.
>
No. Not prod ready is most of what "experimental" means.
=Rob
On Mon, Jan 13, 2014 at 3:38 AM, Cyril Scetbon wrote:
> Can you confirm that, cause we'll add a new DC with version 1.2.13
> (read-only) and we'll upgarde other DCs to 1.2.13 weeks later. We made some
> tests and didn't notice anything. But we didn't test a node failure
>
In general adding nodes
Hi all,
I've spend a lot of time finding a bug in system, but it turns out that the
problem is in Cassandra.
Here is how to reproduce.
=
CREATE KEYSPACE IF NOT EXISTS test_set WITH REPLICATION = { 'class' :
'SimpleStrategy', 'replication_factor' : 1 };
USE test_set;
CREATE TABLE IF N
Hi,
Can you confirm that, cause we'll add a new DC with version 1.2.13 (read-only)
and we'll upgarde other DCs to 1.2.13 weeks later. We made some tests and
didn't notice anything. But we didn't test a node failure
thanks
--
Cyril SCETBON
On 08 Jan 2014, at 19:24, Robert Coli wrote:
> This
