Is Cassandra-jdbc-1.2.5 compatible with Cassandra 1.2,x version?

Hi all, Can I know $subject? Thanks, Harsha -- *Harsha Kumara* *Software Engineer* *WSO2 Inc.* *Sri Lanka.*

Re: Setting up DSE 4.5 for mixed workload with BYOH

Yes. It greatly increases the splits and the random io. -Tupshin On Jul 2, 2014 6:09 PM, "Clint Kelly" wrote: > Sorry BTW in case what I wrote below is unclear, is the concern that > the Hadoop InputFormat (as an example) will need to have a separate > InputSplit (which corresponds to a "SELECT

Re: Setting up DSE 4.5 for mixed workload with BYOH

Sorry BTW in case what I wrote below is unclear, is the concern that the Hadoop InputFormat (as an example) will need to have a separate InputSplit (which corresponds to a "SELECT foo FROM bar WHERE token(baz) > min AND token(baz) < max") for every vnode instead of for every token? (I assume this

Re: Setting up DSE 4.5 for mixed workload with BYOH

Hi Tupshin, Thanks for the quick reply. Is the performance concern from the Hadoop integration needing to set up separate SELECT operations for all of the unique vnode ranges? Best regards, Clint On Wed, Jul 2, 2014 at 6:00 PM, Tupshin Harper wrote: > For performance reasons, you shouldn't ena

Re: Setting up DSE 4.5 for mixed workload with BYOH

For performance reasons, you shouldn't enable vnodes on any Cassandra/DSE datacenter that is doing hadoop analytics workloads. Other DCs in the cluster can use vnodes. -Tupshin On Jul 2, 2014 5:50 PM, "Clint Kelly" wrote: > Hi everyone, > > Apologies if this is the incorrect forum for a questio

Setting up DSE 4.5 for mixed workload with BYOH

Hi everyone, Apologies if this is the incorrect forum for a question like this. I am going to set up a mixed-workload (real-time and analytics) installation of DSE 4.5 using bring-your-own Hadoop (BYOH). We are using CDH 5.0. I was reviewing the installation instructions, and I came across the

Re: unable to find sufficient sources for streaming range

Are you using the "-Dcassandra.replace_address=address_of_dead_node" flag to replace the removed node, according to http://www.datastax.com/documentation/cassandra/1.2/cassandra/operations/ops_replace_node_t.html ? If yes and the new node has the same address as the replaced node, you might be hit

unable to find sufficient sources for streaming range

We are running Cassandra 1.2.5 We have 8 nodes cluster, and we removed one machine from cluster and try to add it back(the purpose is we are using vnodes, some node has more tokens so by rejoining this machine we hope it could get some loads from the busy machines). But we got following exception

Re: keyspace with hundreds of columnfamilies

The official answer, engraved in stone tablets, and carried down from the mountain: “Although having more than dozens or hundreds of tables defined is almost certainly a Bad Idea (just as it is a design smell in a relational database), it's relatively straightforward to allow disabling the Slab

Re: output interpretation of cassandra-stress

Thanks Senhua for the info. Le 2 juil. 2014 01:18, "Senhua Huang" a écrit : > Hi Duyhai, > > According to a reply I got from a Datastax member, the unit is in > milli-second. > > Thanks, > Senhua > > From: DuyHai Doan > Reply-To: "user@cassandra.apache.org" > Date: Saturday, June 21, 2014

Re: keyspace with hundreds of columnfamilies

Hi, thank you for you replies on this; regarding the arena memory is this a fixed memory allocation or is some sort of in memory caching? I ask because I think that a substantial portion of the column families created will not be queried that frequently (and some will become inactive and stay like

Re: keyspace with hundreds of columnfamilies

Arena allocation is an improvement feature, not a limitation. It was introduced in Cassandra 1.0 in order to lower memory fragmentation (and therefore promotion failure). AFAIK It's not intended to be tweaked so it might not be a good idea to change it. Best, Romain tommaso barbugli a écrit s

Re: keyspace with hundreds of columnfamilies

1MB per column family sounds pretty bad to me; is this something I can tweak/workaround somehow? Thanks Tommaso 2014-07-02 17:21 GMT+02:00 Romain HARDOUIN : > The trap is that each CF will consume 1 MB of memory due to arena > allocation. > This might seem harmless but if you plan thousands of

RE: keyspace with hundreds of columnfamilies

The trap is that each CF will consume 1 MB of memory due to arena allocation. This might seem harmless but if you plan thousands of CF it means thousands of mega bytes... Up to 1,000 CF I think it could be doable, but not 10,000. Best, Romain tommaso barbugli a écrit sur 02/07/2014 10:13:41

Re: keyspace with hundreds of columnfamilies

Hi, I am building a sort of db as a service (more, one db table as a service) and I want every user to have their own storage as much isolated as possible (and give them some freedom in terms of schema customisation and the ability to build 2i indexes). You know what kind of memory cost we are talk

Re: [RELEASE] Apache Cassandra 1.2.17 released

TL;DR: unless you plan on compiling the source for this 1.2.17 release with java 6, or want to use the new CloudStack snitch with java 6, you can ignore this. Otherwise, read on. The source for this 1.2.17 release won't compile with java 6 due to a regression from CASSANDRA-7147

Re: keyspace with hundreds of columnfamilies

Hello There is overhead for memory with each col family. This type of configuration could cause heap issues. What is driving the requirement for so many Cfs? > On Jul 2, 2014, at 4:14 AM, tommaso barbugli wrote: > > Hi, > Are there any known issues, shortcomings about organising data in hundr

keyspace with hundreds of columnfamilies

Hi, Are there any known issues, shortcomings about organising data in hundreds of column families? At this present I am running with 300 column families but I expect that to get to a couple of thousands. Is this something discouraged / unsupported (I am using Cassandra 2.0). Thanks Tommaso

Re: RPC timeout paging secondary index query results

Ken Hancock wrote > You didn't post any timings, only when it started failing so it's unclear > whether performance is dropping off or scaling in some sort of linear or > non-linear fashion. Second the recommendation to do some traces which > should be much more telling. I'm afraid I've not yet ha