Thanks Jonathan, actually I'm wondering how CQL is implemented underlying,
a different RPC mechanism? Why it is faster than thrift? I know I'm wrong,
but now I just regard CQL as a query language. Could you please help
explain to me? I still feel puzzled after reading some docs about CQL. I
create
cassandra-stress is a great tool to check whether the sizing of your cluster in
combination of your data model will fit your production needs. I.e. without the
application :) Removing the application removes any possible bugs from the load
test. Sure, it’s a necessary step to do it with your
This did not work either. I changed /etc/cassandra.yaml and restarted
Cassandra (I even restarted the machine to make 100% sure).
What I tried:
1) listen_address: localhost
- connection OK (but of course I can't connect from outside the VM
to localhost)
2) Set listen_interface: eth0
-
Two things:
1. Try telnet 192.168.111.136 9042 and see if it connects?
2. check for hostname in /etc/hosts, if it is mapped correctly.
-Vivek
On Mon, Dec 8, 2014 at 4:19 PM, Richard Snowden richard.t.snow...@gmail.com
wrote:
This did not work either. I changed /etc/cassandra.yaml and
Thanks Chris.
I run a *client on a separate* AWS *instance from* the Cassandra cluster
servers. At the client side, I create 40 or 50 threads for sending requests
to each Cassandra node. I create one thrift client for each of the threads.
And at the beginning, all the created thrift clients
Listen address needs the actual address, not the interface. This is best
accomplished by setting up proper hostnames for each machine (through DNS
or hosts file) and leaving listen_address blank, as it will pick the
external ip. Otherwise, you'll need to set the listen address to the IP of
the
I agree with Robert. If you're trying to test Cassandra, test Cassandra
using stress. Set a reasonable benchmark, and then you'll be able to aim
for that with your client code. Otherwise you're likely to be asking a lot
of the wrong questions make incorrect assumptions.
On Mon Dec 08 2014 at
Thanks Robert. So the native protocol is an asynchronous protocol? And is
native protocol specially created for Cassandra CQL? I haven't heard about
this protocol before.
I have tried using the stress test tool. But it seems that this tool should
run on the same node as one of the Cassandra
So the native protocol is an asynchronous protocol?
Yes.
I have tried using the stress test tool. But it seems that this tool should
run on the same node as one of the Cassandra node(or at least on a node
having Cassandra installed)? One I try to run this tool on a separate client
I left listen_address blank - still I can't connect (connection refused).
cqlsh - OK
cqlsh ubuntu - fail (ubuntu is my hostname)
cqlsh 192.168.111.136 - fail
telnet 192.168.111.136 9042 from outside the VM gives me a connection
refused.
I just started a Tomcat in my VM and did a telnet
Hi Cassandra users,
I'm trying but failing to join a new (well old, but wiped
out/decomissioned) node to an existing cluster.
Currently I have a cluster that consists of 2 nodes and runs C* 2.1.2. I
start a third node with 2.1.2, it gets to joining state, it bootstraps,
i.e. streams some data as
The upper bound for the data size of a single column is 2GB, and the upper
bound for the number of columns in a row (partition) is 2 billion. So if
you wanted to create the largest possible row, you probably can't afford
enough disks to hold it.
So I would -expect- an increase of ~20k qps per node with m3.xlarge so
there may be something up with your client (I am not a c++ person however
but hopefully someone on list will take notice).
Latency does not decreases linearly as you add nodes. What you are likely
seeing with latency since so
Do you mean that I should clear my table after each run? Indeed, I can
see several times of compaction during my test, but could only a few times
compaction affect the performance that much?
It certainly affects performance. Read performance suffers first, then
write performance suffers
The difference is what interface your service is listening on. What is the
output of
$ netstat -ntl | grep 9042
On Mon, 8 Dec 2014 07:21 Richard Snowden richard.t.snow...@gmail.com
wrote:
I left listen_address blank - still I can't connect (connection refused).
cqlsh - OK
cqlsh ubuntu -
Any chance you have something along the path that causes the
connectivity issues?
What's the network connectivity between this node and the other node?
Can you try transferring a big file between the two servers? perhaps
you have an MTU issue that causes TCP PMTU discovery fail.
Can you send
rpc_address (or rpc_interface) is used for client connections,
listen_address is for inter-node communication.
On 8 December 2014 at 19:21, Richard Snowden richard.t.snow...@gmail.com
wrote:
$ netstat -ntl | grep 9042
tcp6 0 0 127.0.0.1:9042 :::*
LISTEN
Ah! That did the trick!
Thanks Sam!
On Mon, Dec 8, 2014 at 8:49 PM, Sam Tunnicliffe s...@beobal.com wrote:
rpc_address (or rpc_interface) is used for client connections,
listen_address is for inter-node communication.
On 8 December 2014 at 19:21, Richard Snowden
has there been any recent discussion on multitenancy namespaces ? I think
this would effectively solve the scenario -- a formalized partition-key
that's enforced at the storage layer, similar to oracle's virtual private
database
it was on the wiki from ~ Aug 2010
Hi All,
I am new to Cassandra so I apologise in advance if I have missed anything
obvious but this one currently has me stumped.
I am currently running a 6 node Cassandra 2.1.1 cluster on EC2 using
C3.2XLarge nodes which overall is working very well for us. However, after
letting it run for a
20 matches
Mail list logo
