I advise you to have 7GB RAM better (more would be better if you have a lot
of data per node). But the real difference is made when you use SSDs or
RAIDs of SSDs, since the bottleneck is the disk throughput in most cases.
We are in the cloud, we tried a lot of configurations and were comfortable
I found using a JBOD SSD setup (one per data directory) to be faster than
RAID. JBOD configuration will also allow a disk to fail and the remaining
disks to continue serving reads if you set disk_failure_policy: best_effort.
If you do go for a RAID controller watch out for any special
Hi,
I am new to Cassandra.
I tried cassandra -f but i am getting the JmxReporter.java (line 388) Error
processing errors.
I downloaded binary version of apache-cassandra-1.2.8 which runs on Ubuntu
11.04 VM Virtual Box.
I added jna.jar file to the library file too.
Thanks for your help.
Massoud
On Thu, Aug 8, 2013 at 9:35 AM, kohanm kohan.mass...@gmail.com wrote:
I tried cassandra -f but i am getting the JmxReporter.java (line 388)
Error processing errors.
ERROR [main] 2013-08-08 07:30:53,717 CassandraDaemon.java (line 176) Your
JVM is out of date. Please upgrade to the newest
The Cassandra team is pleased to announce the first release candidate for
Apache Cassandra 2.0.0.
As a release candidate, we're working to establish that this is relatively
free of obvious bugs before calling it Done. Bottom line, if you aren't
willing to test pre-production software and report
Is the plan to close the 1.x generation on 1.2.* branch and move to 2.0 or
will 1.2 continue to 1.3, 1.4, etc while 2.0 also progresses?
On Thu, Aug 8, 2013 at 1:44 PM, Eric Evans eev...@sym-link.com wrote:
The Cassandra team is pleased to announce the first release candidate for
Apache
Afternoon,
We are noticing nodetool repair processes are not completing after a weeks
worth of time, and have resulted in some Cassandra nodes having more than one
process running do to cron scheduled. We are also chasing some performance
degradation after upgrading all nodes to version 1.2.8
Thanks Rob.
Now I am getting listen_address in cassandra.yaml errors
I mentioned before the Cassandra runs on VM VitualBox on windows 7 machine.
On the ERROR text I changed the real ip address to MymachineIP.
What should I put on the* listen_address:* in *cassandra.yaml* file?
Thanks.
short
[ David Ward ]
Is the plan to close the 1.x generation on 1.2.* branch and move to 2.0 or
will 1.2 continue to 1.3, 1.4, etc while 2.0 also progresses?
The 1.2 branch will be continue to be maintained for sometime, but there
will be no new releases = 1.3 and 2.0.
On Thu, Aug 8, 2013 at
What does ifconfig say? use eth0 or eth1's IP or whatever is static. And
on that note, setup a static IP ( versus dhcp based ) it will make
stopping/starting easier.
On Thu, Aug 8, 2013 at 2:01 PM, kohanm kohan.mass...@gmail.com wrote:
Thanks Rob.
Now I am getting listen_address in
Congradulations on all your hard work!
Can 1.2.5 run alongside of 2.0.0 RC 1?
Thanks,
-Tony
From: Eric Evans eev...@sym-link.com
To: user@cassandra.apache.org
Sent: Thursday, August 8, 2013 1:44 PM
Subject: [RELEASE] Apache Cassandra 2.0.0 RC 1
The Cassandra team is pleased to announce
Hi Dave
Can you tell me more specific.
Thanks,
Here are ifconfig:
ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:00:32:0c
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe00:320c/64 Scope:Link
UP BROADCAST RUNNING
It maybe easier to manage virtualbox using vagrant (
http://www.vagrantup.com/ ).
I am going to assume eth0 from your ifconfig output is a dhcp/dynamic IP
address thats going to change every time you halt/start your virtualbox
instance.
Virtualbox is far outside the scope of C* so I'd recommend
Hi Dave
I added *listen_address:*10.0.2.15 to the *cassandra.yaml *file and it
worked.
But i got another error please look at errors(short):
ERROR 14:47:00,398 Exception encountered during startup
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a
nodetool repair just triggers repair procedure. You can kill nodetool after
start, it doesn't change anything. To stop repair you have to use nodetool
stop VALIDATION|COMPACTION
Thank you,
Andrey
On Thu, Aug 8, 2013 at 1:00 PM, Andy Losey and...@addthis.com wrote:
Afternoon,
We are
But node might be streaming data as well, in that case only option is to
restart node that started streaming operation
Sent from my iPhone
On Aug 8, 2013, at 5:56 PM, Andrey Ilinykh ailin...@gmail.com wrote:
nodetool repair just triggers repair procedure. You can kill nodetool after
start,
I've seen your email last week and saved it to ping you about DevCenter:
http://www.datastax.com/dev/blog/introducing-datastax-devcenter. Please
keep in mind that this is just the first version and we need
suggestions/bug reports/etc.
:- a)
On Wed, Aug 7, 2013 at 11:18 AM, Tony Anecito
17 matches
Mail list logo