Re: State of triggers

[Matija Gobec]

There wasn't much work done on triggers since they "came out". Basically it
was always marked as experimental and never got to a usable production
ready state. CDC is going to become a new way of doing things that made you
look into triggers.
Other than that as Jeff said, I never met or heard about anyone using
triggers in production.

On Thu, Mar 2, 2017 at 8:41 PM, Jeff Jirsa  wrote:

> As far as I know, I've never met anyone who wrote and used their own
> triggers in production. I imagine the number of people doing so is very
> small, regardless of version.
>
> On Thu, Mar 2, 2017 at 11:04 AM, S G  wrote:
>
> > Hi,
> >
> > I am not able to find any documentation on the current state of triggers
> > being production ready.
> >
> > The post at
> > http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-
> > 0-prototype-triggers-support
> > says that "The current implementation is experimental, and there is some
> > work to do before triggers in Cassandra can be declared final and
> > production-ready."
> >
> > So which version of Cassandra should we expect triggers to be stable
> > enough?
> > Our requirement is to develop a solution for several Cassandra users all
> > running on different versions (they won't upgrade easily) and no one is
> > using 3.5+ versions.
> > So the smallest Cassandra version which has production ready triggers
> would
> > be really good to know.
> >
> > Also any advice on common gotchas with Cassandra triggers would be great
> to
> > know.
> >
> > Thanks
> > SG
> >
>

Re: Performance issue in 3.0.9

[Matija Gobec]

We ran for months with the same highly tuned setup on 2.1 and once we
switched to 3.0.9 the performance with the same configuration was crap.
Leveled compaction but a bit more nodes. There are differences in how 2.1
and 3.0 work so I guess you need to revisit your cassandra.yaml and os
settings.
Next to everything Jeff mentioned, is there any reason you have data on all
nodes and use QUORUM?
Also, is there any reason you are not using G1 with 3.0?

On Thu, Feb 2, 2017 at 6:28 AM, Jeff Jirsa  wrote:

> Can you quantify "major"?
>
> Latency or throughput?
> GC pauses?
> What did you see before? What do you see now?
> Do you have a stack dump?
>
>
> --
> Jeff Jirsa
>
>
> > On Feb 1, 2017, at 4:23 PM, Shashank Joshi 
> wrote:
> >
> > We are seeing major performance issues with about 100 GB of data in
> 3.0.9-E001. The exact same app runs very well in 2.1.
> >
> >
> >
> > It feels to us like something is wrong with our configuration because of
> the severity of the issues. Thanks in advance for any recommendations or
> suggestions.
> >
> >
> >
> > Details:
> >
> > Size of data: 100 GB+  all in one table, with a simple schema, couple of
> bigints and a double
> >
> > Cluster: 3 nodes with RF of 3
> >
> > Client: App uses read and write CL of QUORUM and we have a lots of
> timeouts due to inability to reach quorum
> >
> > Compaction: Leveled
> >
> > Nature of data usage: No updates/deletes, High reads, relatively low
> writes
> >
> >
> >
> >
> >
> > JVM:
> >
> > Using CMS GC and around 8 GB of max heap
> >
>

Re: Any idea when 3.0.11 will be released?

[Matija Gobec]

By looking at last DSE version it's already out

[cqlsh 5.0.1 | Cassandra 3.0.11.1485 | DSE 5.0.5 | CQL spec 3.4.0 | Native
protocol v4]

Matija

On Tue, Jan 24, 2017 at 6:24 PM, Johnny Miller 
wrote:

> Just wondering when 3.0.11 will be released?
>
> Thanks,
>
> Johnny
>