memory
(8 or 16 GB) it dies much faster due to GC not being able to keep up. But
it consistently dies on a specific row in single instance case…
Is this enough info to point me somewhere?
Thank you,
Pavel
On Feb 11, 2015, at 1:48 PM, Carlos Rolo r...@pythian.com wrote:
Hello Pavel
and request_timeout) from 3 to 1 for 6 nodes yesterday. Will this
affect internode gossip?
Thanks,
Cheng
On Mon, Feb 9, 2015 at 11:07 PM, Carlos Rolo r...@pythian.com wrote:
Hi Cheng,
Are all machines configured with NTP and all clocks in sync? If that is
not the case do it.
If your clocks
Hi Cheng,
Are all machines configured with NTP and all clocks in sync? If that is not
the case do it.
If your clocks are not in sync it causes some weird issues like the ones
you see, but also schema disagreements and in some cases corrupted data.
Regards,
Regards,
Carlos Juzarte Rolo
Hi,
You can't. Batches are only available for INSERT, UPDATE and DELETE
operations. Batches exist to give Cassandra some atomicity, as in, or all
operations succeed or all fail.
Regards,
Regards,
Carlos Juzarte Rolo
Cassandra Consultant
Pythian - Love your data
rolo@pythian | Twitter: cjrolo
Hey Saurabh,
Your issue seems similar to one I have, but mine seems like a timing issue
(and not easy to reproduce) , check the comments here
https://issues.apache.org/jira/browse/CASSANDRA-8012 and see if it fits
your problem.
Otherwise do like Mark recommended and create a new JIRA issue.
Hello Erik,
It seems possible, refer to the following documentation to see if it fits
your needs:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/security/secureInternalAuthenticationTOC.html
Using Pycassa (https://github.com/pycassa/pycassa)I had no trouble with the
Clients writing/reading from 1.2.x to 2.0.x (Can't recall the minor
versions out of my head right now).
Regards,
Carlos Juzarte Rolo
Cassandra Consultant
Pythian - Love your data
rolo@pythian | Twitter: cjrolo |
HI Asit,
The only help I'm going to give is on point 3), as I have little experience
with 2) and 1) depends on a lot of factors.
For testing the workload use this:
http://www.datastax.com/documentation/cassandra/2.1/cassandra/tools/toolsCStress_t.html
It probably covers all your testing needs.
is not compatible with 1.2.x ?
Regards
Charles
From: Carlos Rolo r...@pythian.com
Reply-To: user@cassandra.apache.org user@cassandra.apache.org
Date: Thursday, 29 January 2015 14:47
To: user@cassandra.apache.org user@cassandra.apache.org
Subject: Re: Upgrading from Cassandra 1.2.14
Hi all,
I have a Cassandra Cluster running and we recently duplicated the cluster.
After following all the steps, the cassandra clients started failing with the
following message:
AuthenticationException(why='Username and/or password are incorrect')
The problem is that even I can't login to
Hello,
I have managed to insert up to 63k records without any problem. In certain
workloads I found that massive batch inserts perform way better than lots of
not-so-massive inserts. I guess it also depends on your setup. Just try it.
Alan Ristić alan.ris...@gmail.com escreveu:
Hi,
I'm
Hi Pierre,
Using 1.0.2 without any problem so far.
0.8.x had problems for us. Never tried 0.8.7 or later tough.
Carlos Rolo
From: Karsten Pappert [mailto:kars...@pappert.de]
Sent: woensdag 7 december 2011 16:54
To: user@cassandra.apache.org; pie...@chalamet.net
Subject: AW: cassandra most
from the upgrade? I just did a rolling restart of all nodes
one-by-one.
From: Tyler Hobbs [mailto:ty...@datastax.com]
Sent: vrijdag 11 november 2011 20:18
To: user@cassandra.apache.org
Subject: Re: Client Timeouts on incrementing counters
On Fri, Nov 11, 2011 at 7:17 AM, Carlos Rolo
c.r
.
I'm bagging my head against the wall checking where can I tune Cassandra to get
rid of this error!
Thx,
Carlos Rolo
101 - 114 of 114 matches
Mail list logo
