Re: Consistent read timeouts for bursts of reads

Mike, Is that where you've bisected it to having been introduced? I'll see what I can do, but doubt it, since we've long since upgraded prod to 2.2.4 (and stage before that) and the tests I'm running were for a new feature. On Fri, 4 Mar 2016 03:54 Mike Heffner, wrote: > Emils, > > I realize t

Updating secondary index options

Hi, I'm using Cassandra 2.2.5 with a custom secondary index. It's created with the below syntax: https://docs.datastax.com/en/cql/3.1/cql/cql_reference/create_index_r.html CREATE CUSTOM INDEX ON users (email) USING 'path.to.the.IndexClass' WITH OPTIONS = {'some_setting': 'value'}; I'd like to up

Re: Updating secondary index options

DROP and re-create the index with the new options On Fri, Mar 4, 2016 at 3:45 PM, Jacques-Henri Berthemet < jacques-henri.berthe...@genesys.com> wrote: > Hi, > > > > I’m using Cassandra 2.2.5 with a custom secondary index. It’s created with > the below syntax: > > https://docs.datastax.com/en/cql

Unexplainably large reported partition sizes

Hi, I'm seeing warnings in my logs about compacting large partitions, e.g.: Compacting large partition drillster/subscriberstats:rqtPewK-1chi0JSO595u-Q (1,470,058,292 bytes) This means that this single partition is about 1.4GB large. This is much larger that it can possibly be, because of two r

Re: Consistent read timeouts for bursts of reads

Emils, We believe we've tracked it down to the following issue: https://issues.apache.org/jira/browse/CASSANDRA-11302, introduced in 2.1.5. We are running a build of 2.2.5 with that patch and so far have not seen any more timeouts. Mike On Fri, Mar 4, 2016 at 3:14 AM, Emīls Šolmanis wrote: >

RE: Modeling transactional messages

As you have it, this is not a good model for Cassandra. Your partition key has only 2 specific values. You would end up with only 2 partitions (perhaps owned by just 2 nodes) that would quickly get huge (and slow). Also, secondary indexes are generally a bad idea. You would either want to create

RE: Updating secondary index options

It’s not possible, it’s a PerRowSecondary index, potentially as big as the table itself (few TBs) it will take a very long time to drop and re-create. -- Jacques-Henri Berthemet From: DuyHai Doan [mailto:doanduy...@gmail.com] Sent: vendredi 4 mars 2016 14:52 To: user@cassandra.apache.org Subject

Re: Increase compaction performance

Any news on this ? We also have issues during repairs when using many LCS tables. We end up with 8k sstables, many pending tasks and dropped mutations We are using Cassandra 2.0.10, on a 24 cores server, with multithreaded compactions enabled. ~$ nodetool getstreamthroughput Current stream throu

Cassandra runing on top of NAS (RAIN storage) !?? anyone ?

Hi, Is there any info about running C* on top of a NAS storage, well, a RAIN storage (to be precise) in fact ? I expect C* to run on top of a RAIN like on top of a high-end SAN: that is, with a drop (-50%) in performance. Any return available ? Thanks. Regards, Dominique

Re: Cassandra runing on top of NAS (RAIN storage) !?? anyone ?

Don't do it On Fri, Mar 4, 2016 at 8:39 AM DE VITO Dominique < dominique.dev...@thalesgroup.com> wrote: > Hi, > > Is there any info about running C* on top of a NAS storage, well, a RAIN > storage (to be precise) in fact ? > > I expect C* to run on top of a RAIN like on top of a high-end SAN: that

RE: Cassandra runing on top of NAS (RAIN storage) !?? anyone ?

> Don't do it [C* on NAS storage] Yes, I know ;-) it’s an anti-pattern. Let’s me give more info. We expect moving from a high-end SAN (<= yes, I know !) to local hard drives. Due to lack time (I won’t dig into it here), we expect in fact moving like this: SAN => RAIN => local HDD (for storage)

Re: Updating secondary index options

Unfortunately for you, ALTER INDEX does not exist. And anyway, even if it exists, altering an index option is going likely to require index rebuild so you can't cut it anyway On Fri, Mar 4, 2016 at 4:59 PM, Jacques-Henri Berthemet < jacques-henri.berthe...@genesys.com> wrote: > It’s not possible

Re: Updating secondary index options

Is this a secondary indexer of your own design so that you know that changing the options will be safe for existing index entries? It might be worth a Jira. Otherwise, you may jus have to manually go in and hack the information under the hood. -- Jack Krupansky On Fri, Mar 4, 2016 at 12:14 PM,

RE: Updating secondary index options

Indeed it’s a custom implementation of PerRowSecondaryIndex, in my case I know it’s safe to update the particular setting I want update, and it won’t rebuild the index, just provide the ability to tune some settings. Even on regular Cassandra indexes that are based on SSTables you could want to

Re: Removing Node causes bunch of HostUnavailableException

Hi Jack, My answers below… What is the exact exception you are getting and where do you get it? Is it UnavailableException or NoHostAvailableException and does it occur on the client, using the Java driver? We saw different types of exceptions. One I could quickly grep are: com.datastax.driver.c

Re: Lot of GC on two nodes out of 7

Without looking at your GC logs (you never posted a gist), my assumption would be you're doing a lot of copying between survivor generations, and they're taking a long time. You're probably also copying a lot of data to your old gen as a result of having full-ish survivor spaces to begin with. On

Choosing production version

Before switching to tick-tock scheme one could choose latest previous x.y.z release, i.e. previous x.y with latest z to ensure maximum maturity and stability. Now obviously odd bug-fixes releases are preferable, but actually for even x.y (3.2, 3.4, etc.) only single bug fix release will be issue

Re: Unexplainably large reported partition sizes

On Fri, Mar 4, 2016 at 5:56 AM, Tom van den Berge wrote: > Compacting large partition > drillster/subscriberstats:rqtPewK-1chi0JSO595u-Q (1,470,058,292 bytes) > > This means that this single partition is about 1.4GB large. This is much > larger that it can possibly be, because of two reasons: >

RE: Modeling transactional messages

Thanks for answering. Yes, It is mainly a queue, but also has some functionality to allow resend the messages. Does anyone have experience handling this kind of scenario, within (or without) Cassandra? Thanks -- IPVP From: sean_r_dur...@homedepot.com R

Re: Modeling transactional messages

I think most people will tell you what Sean did- queues are considered an anti-pattern for many reasons in Cassandra, and while it's possible, you may want to consider something more suited for the job (RabbitMQ, redis queues are just a few ideas that come to mind). If you're sold on the idea of u

Re: MemtableReclaimMemory pending building up

Hi thanks for responding Alain. Going to provide more info inline. However a small update that is probably relevant: while the node was in this state (MemtableReclaimMemory building up), since this cluster is not serving live traffic I temporarily turned off ALL client traffic, and the node still

How can I make Cassandra stable in a 2GB RAM node environment ?

Hi, I'm working on some POCs for Cassandra with single 2GB RAM node environment and some issues came up with me, so let me ask here. I have tried to insert about 200 million records (about 11GB in size) to the node, and the insertion from an application program seems completed, but something (pro

Re: How can I make Cassandra stable in a 2GB RAM node environment ?

Please review the minimum hardware requirements as clearly documented: http://docs.datastax.com/en/cassandra/3.x/cassandra/planning/planPlanningHardware.html Please adjust your hardware usage to at least meet the clearly documented minimum requirements. If you continue to encounter problems once y