Hi
We have to use Cassandra with RF=2 (don't ask why...). There are two
datacenters (RF=2 in each datacenter). Also we use Astyanax as a client
library. In general we want to achieve strong consistency. Read performance
is important for us, that's why we perform writes with LOCAL_QUORUM and
reads
ruuning for a while, you should set the -Xss to more than 160k when you
using jdk1.7.
On Sun, Sep 9, 2012 at 3:39 AM, Peter Schuller
peter.schul...@infidyne.comwrote:
Has anyone tried running 1.1.1 on Java 7?
Have been running jdk 1.7 on several clusters on 1.1 for a while now.
--
/ Peter
@dong, any reason to do so??
On Sun, Sep 9, 2012 at 4:43 PM, dong.yajun dongt...@gmail.com wrote:
ruuning for a while, you should set the -Xss to more than 160k when you
using jdk1.7.
On Sun, Sep 9, 2012 at 3:39 AM, Peter Schuller
peter.schul...@infidyne.com wrote:
Has anyone tried
This is necessary under the later versions of 1.6v35 as well. Nodetool will
show the cluster as being down even though individual nodes will be up.
--Chris
On Sep 9, 2012, at 7:13 AM, dong.yajun dongt...@gmail.com wrote:
ruuning for a while, you should set the -Xss to more than 160k when
Deleting the commitlog files is harmless. It's just a tool that tries to
keep Cassandra more in-sync with the other nodes. A standard repair will
fix all problems that a commitlog replay might do too.
Best regards,
Robin Verlangen
*Software engineer*
*
*
W http://www.robinverlangen.nl
E
Starting with 1.6.0_34, you'll need xss set to 180k. It's updated with the
forthcoming 1.1.5 as well as the next minor rev of 1.0.x (1.0.12).
https://issues.apache.org/jira/browse/CASSANDRA-4631
See also the comments on https://issues.apache.org/jira/browse/CASSANDRA-4602
for the reference to
The bottleneck now seems to be the repair time. If any node becomes too
inconsistent, or needs to be replaced, the rebuilt time is over a week.
This is why i've recommended 300GB to 400GB per node in the past. It's not a
hard limit, but it seems to be a nice balance. You need to take into
This is a server side timeout.
Consistent Level nodes did not respond to the coordinator within rpc_timeout.
The nodes may have been overloaded, check the nodetool tpstats. It will tell
you if the node is backing up and if it has dropped messages.
Cheers
-
Aaron Morton
In general we want to achieve strong consistency.
You need to have R + W N
LOCAL_QUORUM and reads with ONE.
Gives you 2 + 1 2 when you use it. When you drop back to ONE / ONE you no
longer have strong consistency.
may be advise on how to improve it.
Sounds like you know how to improve
It's more like an Eclipse issue now since I find a 0.0.0.0:7199 listener
when executing bin/cassandra in terminal but none when running Cassandra
in Eclipse.
On Sun, Sep 9, 2012 at 12:56 PM, Manu Zhang owenzhang1...@gmail.com wrote:
No, I don't find a listener whose port is 7199. Where to
10 matches
Mail list logo
