Couple more details. I confirmed that swap space is not being used (free -m
shows 0 swap) and cassandra.log has a message like "JNA mlockall
successful". top shows the process having 9g in resident memory but 21.6g
in virtual...What accounts for the much larger virtual number? some kind of
off-heap
lots of folks use Apache Kafka, check out
https://cwiki.apache.org/confluence/display/KAFKA/Powered+By just to name a
few
you can read about the performance for yourself
http://incubator.apache.org/kafka/performance.html
@ http://www.medialets.com we use Kafka upstream of Cassandra acting like a
is anybody using kafka? what other options is there? currently i need
to do around 50,000 (is that a lot?) a minute.
On 7/1/2012 11:39 AM, aaron morton wrote:
Using Cassandra as a queue is generally thought of as a bas idea,
owing to the high delete workload. Levelled compaction handles it
yes, you where correct. resetting the flag and bouncing cassandra fixed
it. thx
On 7/2/2012 8:59 AM, Joost van de Wijgerd wrote:
Could be related to the leap second bug..
try this:
Bug: https://lkml.org/lkml/2012/6/30/122
Simple fix to reset the leap second flag: date; date `date
+"%m%d%H%M
Yeah I noticed the leap second problem and ran the suggested fix, but I
have been facing these problems before Saturday and still see the
occasional failures after running the fix.
Thanks.
On Mon, Jul 2, 2012 at 11:17 AM, Marcus Both wrote:
> Yeah! Look that.
>
> http://arstechnica.com/business
On Mon, Jul 2, 2012 at 10:35 AM, Brian Jeltema
wrote:
> I can't tell whether the bulk load process recovered from the transient dead
> node, or whether I need to start over.
>
> Does anybody know?
You need to start over if the failure detector tripped, but it will
retry a few times for regular n
Is this still an issue ?
It looks like something shut down the messaging service. Was there anything
else in the logs ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 28/06/2012, at 3:49 AM, Robin Verlangen wrote:
> Hi there,
>
> Toda
Thanks for contributing.
I'm behind the curve on CQL 3, but here is a post about some of the changes
http://www.datastax.com/dev/blog/whats-new-in-cql-3-0
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 28/06/2012, at 2:30 AM, Thierry Te
> I'm trying to do the following : update keyspace.CF set '2' = '2' + 12
> WHERE KEY = 'mykey';
CQL does not support expressions in the SET clause.
http://www.datastax.com/docs/1.0/references/cql/UPDATE
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpi
The nodes in DC1 need to be able to reach the nodes in DC2 on the public
(NAT'd) IP.
Others may be able to provide some more details .
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 27/06/2012, at 9:51 PM, Andras Szerdahelyi wrote:
>
Do you have the full stack ? It will include a cause.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 27/06/2012, at 12:07 PM, James Pirz wrote:
> Dear all,
>
> I am trying to use "sstableloader" in cassandra 1.1.1, to bulk load some data
Gurpreet ,
If you can reproduce this please create a ticket on
https://issues.apache.org/jira/browse/CASSANDRA
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 19/06/2012, at 6:38 AM, Gurpreet Singh wrote:
>
> I found a fix for this
> After 10 days my cluster crashes due to a java.lang.OutOfMemoryError during
> compaction of the big column family that contains roughly 95% of the data.
Does this column family have very wide rows ?
> simply some tweaks I need to make in the yaml file. I have tried:
The main things that r
Hello All,
We are using Cassandra 1.0.7 on AWS on mediums (that is 3.8G RAM, 1 Core),
running Ubuntu 12.04. We have three nodes in the cluster and we hit only
one node from our application. Thrift version is 0.6.1 (we changed from 0.8
because we thought there was a compatibility problem between th
is the 2.1 image still around?
On 7/2/2012 11:24 AM, Deno Vichas wrote:
all,
i've got a datastax 2.1 ami instance that's screwed up. for some
reason it won't read the config file. what's the recommended way to
replace this node with a new one? it doesn't seem like you can use
the ami to b
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.1.2.
Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:
http://cassand
you're right!
somehow while rebooting it tried to upgrade. this broke node has 1.1.1
where my others are running 1.0.7. wtf??
- deno
On 7/2/2012 10:25 AM, Brian Jeltema wrote:
Just the opposite, I think. The property value exists in the yaml
file but does not have a corresponding defin
all,
i've got a datastax 2.1 ami instance that's screwed up. for some reason
it won't read the config file. what's the recommended way to replace
this node with a new one? it doesn't seem like you can use the ami to
bring up single nodes as it want to do whole clusters.
thanks,
deno
should be the same version. i did notice some extra files in my etc
dir. there's a few dpkg-new files.
ubuntu@ip-10-40-207-151:~/datastax_ami$ ll /etc/cassandra/
total 100
drwxr-xr-x 2 root root 4096 2012-07-02 18:13 ./
drwxr-xr-x 99 root root 4096 2012-07-02 16:31 ../
-rw-r--r-- 1 root ro
On Mon, Jul 2, 2012 at 5:43 AM, puneet loya wrote:
> When I restarted the system , it is showing the keyspace does not exist.
>
> Not even letting me to create the keyspace with the same name again.
Paste the error you get.
=Rob
--
=Robert Coli
AIM>ALK - rc...@palominodb.com
YAHOO - rcoli.palo
no, it's there... after editing the first couple lines of the config
file there spot where it complains changes.
On 7/2/2012 10:20 AM, Robin Verlangen wrote:
Your missing the "sliced_buffer_size_in_kb" property in your
cassandra.yaml file.
2012/7/2 Deno Vichas mailto:d...@syncopated.net>>
Just the opposite, I think. The property value exists in the yaml file but
does not have a corresponding definition in the Config class.
Typically caused by a version mismatch in my experience.
On Jul 2, 2012, at 1:20 PM, Robin Verlangen wrote:
> Your missing the "sliced_buffer_size_in_kb" prop
Your missing the "sliced_buffer_size_in_kb" property in your cassandra.yaml
file.
2012/7/2 Deno Vichas
> i'm seeing the following exception in my log now. this is even after
> re-creating my config file.
>
>
> INFO [main] 2012-07-02 16:58:17,850 AbstractCassandraDaemon.java (line
> 121) JVM v
i'm seeing the following exception in my log now. this is even after
re-creating my config file.
INFO [main] 2012-07-02 16:58:17,850 AbstractCassandraDaemon.java (line
121) JVM vendor/version: Java HotSpot(TM) 64-Bit Server VM/1.6.0_26
INFO [main] 2012-07-02 16:58:17,853 AbstractCassandraDa
We are using hector.rb to do a MultigetSliceQuery over one row, with count 1.
Most of the time it works, but occasionally we are getting back 2 columns. Has
anyone seen this before?
Cassandra: 1.1.0-SNAPSHOT
Hector: 1.0.2
Hector.rb: 0.0.1
Gem Code:
https://github.com/jashmenn/hector.rb/blob/ma
the node that doesn't want to start just spit out -
/EC2 is experiencing some issues and has not allocated all of the
resources in under 10 minutes.
Aborting the clustering of this reservation. Please try again.
Please visit http://datastax.com/ami for this AMI's feature set.
/
Could be related to the leap second bug..
try this:
Bug: https://lkml.org/lkml/2012/6/30/122
Simple fix to reset the leap second flag: date; date `date
+"%m%d%H%M%C%y.%S"`; date;
mvg
Joost
On Mon, Jul 2, 2012 at 5:43 PM, Deno Vichas wrote:
> all,
>
> my 4 node cluster seems pretty screwed up
Hi all
We have 4 indexed columns; all configured in UT8Type even if one columns is
a date and the other an integer).
1/ the read query we run can have up to 4 criteria
*select my_cf where columnA = a and columnB = b and columnC = c and columnD
= d*
This query, is fast (<500ms) up to 3 criterias
Thanks for the answer. In fact this is maybe simpler.
We do a lot of inserts and a couple of reads.
- tpstats show us the pending read stage was growing.
- *It seems* there was an issue with one of our request. We have 4 indexed
columns (UT8Type)
First, one of the indexed value was "---".
all,
my 4 node cluster seems pretty screwed up after the AWS outage. we
found all our machines with their cpu stuck at 100%. so i went to
restart each cassandra node one by one. i did node with token id 0
first. i came back but doesn't look like it doing anything. once i
thought it was u
I'm attempting to perform a bulk load by calling the jmx:bulkLoad method on
several nodes in parallel. In a Casssandra log
file I see a few occurrences of the following:
INFO [GossipTasks:1] 2012-07-02 10:12:33,626 Gossiper.java (line 759)
InetAddress /10.4.0.3 is now dead.
ERROR [GossipTasks:1
Thierry,
Key cache files are stored inside your saved_caches_directory defined in
cassandra.yaml, which has default value of /var/lib/cassandra/saved_caches.
Yuki
On Monday, July 2, 2012 at 4:00 AM, Thierry Templier wrote:
> Hello Yuki,
>
> Could you give me hints about where to find these
Yeah! Look that.
http://arstechnica.com/business/2012/07/one-day-later-the-leap-second-v-the-internet-scorecard/
I had the same problem. The solution was rebooting.
On Mon, 2 Jul 2012 11:08:57 -0400
feedly team wrote:
> Hello,
>I recently set up a 2 node cassandra cluster on dedicated hardwa
Hi,
Had the same problem this morning, seems related to the leap second bug.
Rebooting the nodes fixed it for me, but there seems to be a fix also without
rebooting the server.
Kind regards,
Pieter
From: feedly team [mailto:feedly...@gmail.com]
Sent: maandag 2 juli 2012 17:09
To: user@cassandra
Hello,
I recently set up a 2 node cassandra cluster on dedicated hardware. In
the logs there have been a lot of "InetAddress xxx is now dead' or UP
messages. Comparing the log messages between the 2 nodes, they seem to
coincide with extremely long ParNew collections. I have seem some of up to
50
I've tested this and added a not to issue 4400. Hopefully that¹s the
correct thing to do.
Andy
On 02/07/2012 08:13, "Sylvain Lebresne" wrote:
>Yeah, we tried to catch when Snappy couldn't load (and deactivate it
>when that happens) but apparently we've missed a few of the exceptions
>that can
The only trouble you might run into is classpath conflicts, but as long as
they are using compatible versions of common dependencies you should be
okay.
-brian
--
Brian O'Neill
Lead Architect, Software Development
Health Market Science | 2700 Horizon Drive | King of Prussia, PA 19406
p: 215.588.
I recognize that behind the scenes there's connection pooling and all kinds
of nice asynchronous dispatch of requests to cassandra, but is there any
sort of reason to avoid using different Java clients in the same
application?
I'm noticing that some are better suited to certain kinds activity than
Hi,
While I was typing my mail I had the idea to try with the new directory layout.
It seems you have to change the parameter settings from 1.0 to 1.1
In 1.0:
Param 1:
Param 2:
In 1.1:
Param 1:
Param 2: /
Don't know if this is a bug or a breaking change ?
Kind regards,
Pieter Callewaert
From
Hi guys,
We have a 6-node 1.0.9 cluster for production and 3-node 1.1.0 cluster for
testing the new version of Cassandra.
In both we insert data in a particular CF with always a TTL of 31 days.
To clean up the files faster we use the forceUserDefinedCompaction to manually
force compaction on th
Hi,
I have set up cassandra on my linux system.
When I restarted the system , it is showing the keyspace does not exist.
Not even letting me to create the keyspace with the same name again.
Did anybody find this issue?
Any solutions on it?
Cheers,
Puneet
Just to clarify, the data that we're loading SSTables from (v1.0.3) doesn't
have compression enabled on any of the CF's.
So in theory the compression should occur on the receiving end (v1.1.1) as
we're going from uncompressed data to compressed data.
So I'm not sure if the bug you mention is cau
Bug: https://lkml.org/lkml/2012/6/30/122
Simple fix to reset the leap second flag: date; date `date
+"%m%d%H%M%C%y.%S"`; date;
/Henrik
On Mon, Jul 2, 2012 at 1:56 PM, Jean Paul Adant
wrote:
> Hi,
>
> I did have the same problem with cassandra 1.1.1 on Ubuntu 11.10
> I had to reboot all nodes
>
Hi,
I did have the same problem with cassandra 1.1.1 on Ubuntu 11.10
I had to reboot all nodes
I'm interested in any information about this.
Thanks
Jean Paul
2012/7/2 Filippo Diotalevi
> Hi,
> we had some really weird issues during the weekend, with our cassandra
> nodes starting marking as
On Mon, Jul 2, 2012 at 1:24 PM, jmodha wrote:
> Out of interest, we're not specifying a specific chunk size on the schema
> (in the hope that it would just use the default of 64kb), so it reads
> something like:
Actually, we've had bugs related to the handling of the chunk size in early 1.0
relea
On Mon, Jul 2, 2012 at 1:09 PM, Abhijit Chanda
wrote:
> Hi All,
>
> I am using cassandra 1.0.8. How can i use cql 3.0.0 in this?
You can't, CQL 3 is only in Cassandra 1.1 onwards.
--
Sylvain
>
>
> --
> Abhijit Chanda
> Analyst
> VeHere Interactive Pvt. Ltd.
> +91-974395
>
Thanks Sylvain.
I had a look at a node where we streamed data to and I do indeed see the
"..-CompressionInfo.db" files..
However, prior to running the "upgradesstables" command, the total size of
all the SSTables was 27GB and afterwards its 12GB.
So even though the CompressionInfo files were the
Hi All,I am using cassandra 1.0.8. How can i use cql 3.0.0 in this?
--
Abhijit Chanda
Analyst
VeHere Interactive Pvt. Ltd.
+91-974395
Hi,
we had some really weird issues during the weekend, with our cassandra nodes
starting marking as dead other (working) nodes in the cluster. That happened
all Sunday, and it's still happening. Node are marked dead and up all the time….
Some example logs:
INFO [GossipTasks:1] 2012-07-02 06:
Hello Yuki,
Could you give me hints about where to find these files. I have a look
in the installation folder of Cassandra and in the /var/lib/cassandra
folder?
Thanks very much for your help.
Thierry
That was bug in 1.1.1 and fixed in
https://issues.apache.org/jira/browse/CASSANDRA-4331.
Wo
Thanks ,
Will give it a go now.
Andy
On 02/07/2012 08:13, "Sylvain Lebresne" wrote:
>Yeah, we tried to catch when Snappy couldn't load (and deactivate it
>when that happens) but apparently we've missed a few of the exceptions
>that can be thrown in that case. I've created
>https://issues.apach
I'm afraid not. It's too much change for an oldstable release series,
and the bulk of the change is to AtomicSortedColumns which doesn't
exist in 1.0, so even if we wanted to take a "maybe it's okay if we
release it first in 1.1.3 and then backport" approach it wouldn't
improve our safety margin si
On Mon, Jul 2, 2012 at 12:14 AM, jmodha wrote:
> Sure, before I create a ticket, is there a way I can confirm that the
> sstables are indeed not compressed other than running the "rebuildsstables"
> nodetool command (and observing the live size go down)?
If the sstable is compressed it will have
On Sun, Jul 1, 2012 at 3:31 PM, Bill Hastings wrote:
> Could someone please tell me where I should start looking at code to
> understand how cassandra bootstrap process works?
The bootstrap phase pretty much start in the bootstrap() method in
StorageService.java, though a good part of the code is
Yeah, we tried to catch when Snappy couldn't load (and deactivate it
when that happens) but apparently we've missed a few of the exceptions
that can be thrown in that case. I've created
https://issues.apache.org/jira/browse/CASSANDRA-4400 to fix that. If
you could try the patch on that issue and ch
56 matches
Mail list logo
