Re: Recordset capabilities...

Yes, currently the resultSet will contain all the rows, there is no fetch size supported. This will change soon however since Cassandra 2.0 has some paging support at the protocol level and the driver will make use of that. But that won't be before 2.0. As an aside, this kind of question about

Deletion use more space.

Hi, all: I use cassandra 1.2.4 and I have 4 nodes ring and use byte order partitioner. I had inserted about 200G data in the ring previous days. Today I write a program to scan the ring and then at the same time delete the items that are scanned. To my surprise, the cassandra cost more

cassandra GC cpu usage

Hi C* user list, I have a curious recurring problem with Cassandra 1.2 and what seems like a GC issue. The cluster looks somewhat well balanced, all nodes are running HotSpot JVM 1.6.0_31-b04 and cassandra 1.2.3. Address RackStatus State LoadOwns 10.2.3.6

Re: Deletion use more space.

Deletion is not really removing data, but it's adding tombstones (markers) of deletion. They'll be later merged with existing data during compaction and - in the end (see: gc_grace_seconds) - removed, but by this time they'll take some space.

Re: Deletion use more space.

Hi, I use the follow cmd to update gc_grace_seconds. It reports error! Why? [default@WebSearch] update column family ScheduleInfoCF with gc_grace_seconds = 3600; java.lang.IllegalArgumentException: No enum const class org.apache.cassandra.cli.CliClient$ColumnFamilyArgument.GC_GRACE_SECONDS

Re: Deletion use more space.

Thank you! It should be update column family ScheduleInfoCF with gc_grace = 3600; Faint. - 原始邮件 - 发件人: 杨辉强 huiqiangy...@yunrang.com 收件人: user@cassandra.apache.org 发送时间: 星期二, 2013年 7 月 16日 下午 6:15:12 主题: Re: Deletion use more space. Hi, I use the follow cmd to update gc_grace_seconds.

Pig load data with cassandrastorage and slice filter param

hi all I trying to load data from cassandra with slice params option but ther are no much info about how to use i. I found only a quick reference in readme.txt in cassandra project .../examples/pig *...* *Slices on columns can also be specified:* *grunt rows = LOAD

Huge query Cassandra limits

Hi everybody, We are working on porting some life science applications to Cassandra, but we have to deal with its limits managing huge queries. Our queries are usually multiget_slice ones: many rows with many columns each. We have seen system start to slower until the entry point node crashes

Re: cassandra GC cpu usage

What's your replication factor? Can you check tp stats and net stats to see if you are getting more mutations on these nodes ? Sent from my iPhone On Jul 16, 2013, at 3:18 PM, Jure Koren jure.ko...@zemanta.com wrote: Hi C* user list, I have a curious recurring problem with Cassandra 1.2

Re: Node tokens / data move

vnodes currently do not brings any noticeable benefits to outweight trouble The main advantage of vnodes is that it lets you have flexibility with respect to adding and removing nodes from your cluster without having to rebalance your cluster (issuing a lot of moves). A shuffle is a lot of

Re: Node tokens / data move

Eric, Unfortunately if you've got a non-vnode cluster and are trying to convert, you are likely going to at least want, if not have to, run shuffle. It isn't a pleasant situation when you run into that because in order for the shuffle to execute safely and successfully you need to have

Re: Deletion use more space.

I don't think setting gc_grace_seconds to an hour is going to do what you'd expect. After gc_grace_seconds, if you haven't run a repair within that hour, the data you deleted will seem to have been undeleted. Someone correct me if I'm wrong, but in order to order to completely delete data and

Re: Deletion use more space.

The only time information is removed from the filesystem is during compaction. Compaction can remove tombstones after gc_grace_seconds, which, could result in reanimation of deleted data if the tombstone was never properly replicated to other replicas. Repair will make sure tombstones are

Repair needed on all nodes if RF == number of nodes?

Hello. I have a cluster with 3 nodes and RF is 3. I've noticed that when I run a repair on a node (I don't use -pr), all nodes are involved. So, does this mean the other nodes are repaired as well? Do I still need to run repair on the other 2 nodes inside the gc_grace_period? Thanks, André

Re: Node tokens / data move

if you've got a non-vnode cluster and are trying to convert, you are likely going to at least want, if not have to, run shuffle Fair enough. Running shuffle after upgrading to using vnodes is nearly mandatory or else you'll run into troubles when adding more nodes (see this Jira

Re: Recordset capabilities...

Thanks Sylvain for answering the question from a Cassandra perspective. I will use Datastax forum where appropiate. I have gone live with Cassandra so I will not be bringing these things up anymore I hope. Best Regards, -Tony From: Sylvain Lebresne

Re: Huge query Cassandra limits

On Tue, Jul 16, 2013 at 4:46 AM, cesare cugnasco cesare.cugna...@gmail.comwrote: We are working on porting some life science applications to Cassandra, but we have to deal with its limits managing huge queries. Our queries are usually multiget_slice ones: many rows with many columns each.

Re: V2 Beta 1 bootstrap behaviour ?

On Tue, Jul 16, 2013 at 1:16 AM, Andrew Cobley a.e.cob...@dundee.ac.ukwrote: I'm setting up a new test cluster using 2.0.0-beta1 and I noticed the following behaviour with vnodes turned on. I bring up one node all well and good. however if I bring up a second node, that can't contact the

Re: Repair needed on all nodes if RF == number of nodes?

On Tue, Jul 16, 2013 at 7:48 AM, André Cruz andre.c...@co.sapo.pt wrote: I have a cluster with 3 nodes and RF is 3. I've noticed that when I run a repair on a node (I don't use -pr), all nodes are involved. So, does this mean the other nodes are repaired as well? Do I still need to run

Re: V2 Beta 1 bootstrap behaviour ?

Righto ! Will do a JIRA report.. Many thanks Andy On 16 Jul 2013, at 18:50, Robert Coli rc...@eventbrite.commailto:rc...@eventbrite.com wrote: On Tue, Jul 16, 2013 at 1:16 AM, Andrew Cobley a.e.cob...@dundee.ac.ukmailto:a.e.cob...@dundee.ac.uk wrote: I'm setting up a new test cluster using

AbstractCassandraDaemon.java (line 134) Exception in thread

Hello, At least 2 times a day I'm having hundreds of log entry related to exception below, the network bottleneck seems, anyone know how to solve, or encountered this problem Using C* version 1.1.4 and Java version 1.7.0_21 Java(TM) SE Runtime Environment (build 1.7.0_21-b11) Java

Re: Alternate major compaction

On Fri, Jul 12, 2013 at 2:28 AM, Radim Kolar h...@filez.com wrote: with some very little work (less then 10 KB of code) is possible to have online sstable splitter and exported this functionality over JMX. Are you volunteering? If so, I'd totally dig using the patch! :D =Rob

Re: Deletion use more space.

Thanks, But Michael's answer confuse me more. I use list cf; in cassandra-cli. It seems lots of rows have been deleted, but keys exist. After the deletion, why the key still exists? It seems useless. RowKey: 3030303031306365633862356437636365303861303433343137656531306435 ---

Intresting issue with getting Order By to work...

Hi All, Well I got most everything working I wanted using Cassandra then discovered I needed to use an Order By. I am using Cassandra 1.2.5. The use of Order By requires Primary Key which appears to be only supported by by using CQL and not Cassandra-cli. So I dropped my table created uisng CLI