Probably yes, if you also disabled any sort of failovers from the token-aware
client…
(Talking about this makes you realize how many failsafes Cassandra has. And
still you can lose data… :-P)
/Janne
On 18 Dec 2013, at 20:31, Robert Coli rc...@eventbrite.com wrote:
On Wed, Dec 18, 2013 at
On Wed, Dec 18, 2013 at 7:31 PM, Robert Coli rc...@eventbrite.com wrote:
On Wed, Dec 18, 2013 at 2:44 AM, Sylvain Lebresne sylv...@datastax.comwrote:
As Janne said, you could still have hint being written by other nodes if
the one storage node is dead, but you can use the system
property
Mind opening a ticket on https://datastax-oss.atlassian.net/browse/JAVA?
It's almost surely a bug.
--
Sylvain
On Thu, Dec 19, 2013 at 8:21 AM, David Tinker david.tin...@gmail.comwrote:
We are using Cassandra 2.0.3-1 installed on Ubuntu 12.04 from the
DataStax repo with the DataStax Java
I would suggest to file an issue at
https://datastax-oss.atlassian.net/browse/JAVA
-Mikhail
On 12/18/13, 23:21, David Tinker wrote:
We are using Cassandra 2.0.3-1 installed on Ubuntu 12.04 from the
DataStax repo with the DataStax Java driver version 2.0.0-rc1. Every
now and then we get the
I would suggest to file an issue at
https://datastax-oss.atlassian.net/browse/JAVA
-Mikhail
On 12/18/13, 23:21, David Tinker wrote:
We are using Cassandra 2.0.3-1 installed on Ubuntu 12.04 from the
DataStax repo with the DataStax Java driver version 2.0.0-rc1. Every
now and then we get the
Hi all,
after upgrading C* and the java-driver I am running into problems with paging.
Maybe someone can provide a quick clue.
Upgrading was
C* from 2.0.1 to 2.0.3
Java Driver from 2.0.0-rc1 to 2.0.0-rc2
Client side, I get the following messages (apparently during a call to
Hi,
In regards to recv_get_range_slices(), in my cassandra client code, it
always throw new
org.apache.thrift.TApplicationException(org.apache.thrift.TApplicationException.BAD_SEQUENCE_ID,
get_range_slices failed: out of sequence response);
Full source code here
https://issues.apache.org/jira/browse/CASSANDRA-6447
On Thu, Dec 19, 2013 at 11:16 AM, Jan Algermissen
jan.algermis...@nordsc.com wrote:
Hi all,
after upgrading C* and the java-driver I am running into problems with
paging. Maybe someone can provide a quick clue.
Upgrading was
C* from
Sylvain,
thanks.
Is there anything I can do except waiting for a fix?
Could I do something to my data? Or data model?
I moved to 2.0.3 because I think I experienced missing rows in 2.0.1 paging -
is this related to the 2.0.3 bug? Meaning: going back to 2.0.1 will fix the
exception, but leave
Thanks all for your responses. We've downgraded from 2.0.3 to 2.0.0 and
everything became normal.
2013/12/8 Nate McCall n...@thelastpickle.com
If you are really set on using Cassandra as a cache, I would recommend
disabling durable writes for the keyspace(s)[0]. This will bypass the
Hi all!
We've had a problem with cassandra recently. We had 2 one-minute periods
when we got a lot of timeouts on the client side (the only timeouts during
9 days we are using cassandra in production). In the logs we've found
corresponding messages saying something about MUTATION messages
Is there anything I can do except waiting for a fix?
Disable paging (which might imply having to do some manual paging if the
result set you were querying were really big).
I moved to 2.0.3 because I think I experienced missing rows in 2.0.1
paging - is this related to the 2.0.3 bug?
What version of Cassandra are you running ? I used to see them a lot with
1.2.9, I could correlate the dropped messages with the heap usage almost
every time, so check in the logs whether you are getting GC'd. In this
respect 1.2.12 appears to be more stable. Moving to 1.2.12 took care of
this for
On 19.12.2013, at 14:09, Sylvain Lebresne sylv...@datastax.com wrote:
Is there anything I can do except waiting for a fix?
Disable paging (which might imply having to do some manual paging if the
result set you were querying were really big).
Yes, that was my original code - might do
I'll note that while far from idea, you can also disable assertion with
2.0.3.
Is there a way to do that without patching/recompiling?? You make it sound
as if there is...
Comment the following line in cassandra-env.sh:
JVM_OPTS=$JVM_OPTS -ea
Rob - I got a question following your advice. This is how, I define my
column family
validators = {
'approved':'UTF8Type',
'tid': 'UTF8Type',
'iid': 'UTF8Type',
'score': 'IntegerType',
'likes':
Hi,
We are in the process of upgrading 1.2 to 2.0.3. We have a four node cluster
and we're upgrading one node at a time. After upgrading two of the nodes, we
encountered a problem. We observed that if we run nodetool status on the 2.0.3
hosts, they would show 2 nodes down and 2 nodes up.
On Thu, Dec 19, 2013 at 1:03 PM, Parag Patel parag.pa...@fusionts.comwrote:
We are in the process of upgrading 1.2 to 2.0.3.
...
Please help as this will prevent us from pushing into production.
(as a general commentary :
Thanks for the reply. By packet drops I mean, the client is not able to read
the shared memory as fast as the software switch is writing into it..
What is the error you are getting on the client ?
Also, I would like to know if in general , distribution of write requests
to
Thanks for that link.
Our 1.2 version is 1.2.12
Our 2.0.3 nodes were restarted once. Before restart, it was the 1.2.12 binary,
after it was the 2.0.3. Immediately after the node was back in the cluster, we
ran nodetool upgradesstables. We haven't restarted since.
Is a restart required for
I can't comment on your specific issue, but I don't know if running 2.0.0
in production is a good idea. At the very least I'd try upgrading to the
latest 2.0.X (currently 2.0.3.)
https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/
On 20 December 2013 06:08, Alexander
21 matches
Mail list logo
