On 05/18/2012 01:35 PM, Tyler Hobbs wrote:
Your firewall rules need to allow TCP traffic on any port >= 1024 for
JMX to work. It initially connects on port 7199, but then the client
is asked to reconnect on a randomly chosen port.
You can open the firewall, SSH to the node first, or set up so
I decided to wipe cassandra clean and try again. Haven't seen it again yet,
but will report if I do. This may have been a symptom of having some previous
data around, as my steps were:
1. shutdown and wipe data
2. run with NullCompressor
3. notice Cassandra complain compressor is not in packa
We have some production Solaris boxes so I can't use SnappyCompressor (no
library included for Solaris), so I set it to JavaDeflate. I've also noticed
higher load issues with 1.1.0 versus 1.0.6: could this be JavaDeflate, or is
that what the old default was? Anyway, I thought I would try no c
Thanks Radim.
Radim, actually 100 reads per second is achievable even with 2 disks.
But achieving them with a really low avg latency per key is the issue.
I am wondering if anyone has played with index_interval, and how much of a
difference would it make to reads on reducing the index_interval. I
On Fri, May 18, 2012 at 1:41 PM, Poziombka, Wade L
wrote:
> How does counters affect this? Why would be different?
Oh, actually this is an obsolete caution as of Cassandra 0.8beta1 :
https://issues.apache.org/jira/browse/CASSANDRA-1938
Sorry! :)
=Rob
PS - for historical reference, before this
How does counters affect this? Why would be different?
Sent from my iPhone
On May 18, 2012, at 15:40, "Rob Coli" wrote:
> On Thu, May 17, 2012 at 9:37 AM, Bryan Fernandez
> wrote:
>> What would be the recommended
>> approach to migrating a few column families from a six node cluster to a
>
On Thu, May 17, 2012 at 9:37 AM, Bryan Fernandez wrote:
> What would be the recommended
> approach to migrating a few column families from a six node cluster to a
> three node cluster?
The easiest way (if you are not using counters) is :
1) make sure all filenames of sstables are unique [1]
2) c
On 05/18/2012 01:35 PM, Tyler Hobbs wrote:
Your firewall rules need to allow TCP traffic on any port >= 1024 for
JMX to work. It initially connects on port 7199, but then the client
is asked to reconnect on a randomly chosen port.
You can open the firewall, SSH to the node first, or set up so
Your firewall rules need to allow TCP traffic on any port >= 1024 for JMX
to work. It initially connects on port 7199, but then the client is asked
to reconnect on a randomly chosen port.
You can open the firewall, SSH to the node first, or set up something like
this: http://simplygenius.com/2010
Hi,
I had a schema disagreement problem in cassandra 1.0.9 cluster, where
one node had different schema version.
So I followed the faq at
http://wiki.apache.org/cassandra/FAQ#schema_disagreement
disabled gossip, disabled thrift, drained and finally stopped the
cassandra process, on startup
I updated the cassandra-env.sh
$JMX_HOST="10.20.30.40"
JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=$JMX_HOST"
netstat -ltn shows port 7199 is listening.
I tried both public and private IP for connecting but neither helps.
However, I am able to connect locally from within server.
I get this
Hey Roshan,
Read requests accepted by your Coordinator node in your PROD environment will
only be sent to your DR data center if you use a CONSISTENCY setting that
specifies such. The easiest way to ensure you are only reading from Production
is to use LOCAL_QUORUM or ONE on all reads in your P
to get 100 random reads per second on large dataset (100 GB) you need
more disks in raid 0 then 2.
Better is to add more nodes then stick too much disks into node. You
need also adjust io scheduler in OS.
+1 !
2012/5/17 Sasha Dolgy :
> All,
>
> A year ago I made a simple query to see if there were any users based in and
> around Zurich, Switzerland or the Alps region, interested in participating
> in some form of Cassandra User Group / Meetup. At the time, 1-2 replies
> happened. I didn't do mu
Hi,
Sorry to say I didn't look further into this. I'm using CentOS 6.2 now for
loader without any problems.
Kind regards,
Pieter Callewaert
-Original Message-
From: sj.climber [mailto:sj.clim...@gmail.com]
Sent: vrijdag 18 mei 2012 3:56
To: cassandra-u...@incubator.apache.org
Subject:
Hi Viktor,
As i mentioned, my goal is to finally achieve 100 reads per second
throughput, its not a batch size of 100.
The writes are already done, and i am not doing them anymore. I loaded the
system with about 130 million keys.
I am just doing a read workload in my experiment as of now..
1. n
16 matches
Mail list logo
