cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Roth <benjamin.r...@jaumo.com>
Subject Re: [VOTE] 3.X branch feature freeze
Date Fri, 13 Jan 2017 18:16:13 GMT
Progress:
Yes and no. I made a patch that made our cluster stable performance wise
but introduces a consistency issue I am aware of. We can deal with it and I
prefer this over severe performance problems. But this is nothing you can
offer to regular users. I created a bunch of tickets related to this.
Making bootstrap + decommision performant + consistent should not be much
effort.
Making repairs performant + consistent + fix incremental repairs will be
probably more effort. I wanted to investigate more before xmas but did not
find the time until now. It is on my agenda and I appreciate any support.

Tickets I created recently:
https://issues.apache.org/jira/browse/CASSANDRA-13073
https://issues.apache.org/jira/browse/CASSANDRA-13066
https://issues.apache.org/jira/browse/CASSANDRA-13065
https://issues.apache.org/jira/browse/CASSANDRA-13064

Also important:
https://issues.apache.org/jira/browse/CASSANDRA-12888


2017-01-13 18:55 GMT+01:00 Jonathan Haddad <jon@jonhaddad.com>:

> +1 (non binding) to feature freeze.
>
> I also like the idea of stabilizing MVs.  Ben, you've probably been the
> most vocal about the issues, have you made any progress towards making them
> work any better during bootstrap / etc?  Any idea of fixing them is a major
> undertaking?
>
> Jon
>
> On Fri, Jan 13, 2017 at 9:39 AM Benjamin Roth <benjamin.roth@jaumo.com>
> wrote:
>
> +1 also I appreciate any effort on MV stability. It is an official 3.x
> feature but not production ready for the masses.
>
> Am 13.01.2017 18:34 schrieb "Jonathan Ellis" <jbellis@gmail.com>:
>
> > +1
> >
> > On Fri, Jan 13, 2017 at 11:21 AM, Aleksey Yeschenko <aleksey@apache.org>
> > wrote:
> >
> > > Hi all!
> > >
> > > It seems like we have a general consensus on ending tick-tock at 3.11,
> > and
> > > moving
> > > on to stabilisation-only for 3.11.x series.
> > >
> > > In light of this, I suggest immediate feature freeze in the 3.X branch.
> > >
> > > Meaning that only bug fixes go to the 3.11/3.X branch from now on.
> > >
> > > All new features that haven’t be committed yet should go to trunk only
> > > (4.0), if the vote passes.
> > >
> > > What do you think?
> > >
> > > Thanks.
> > >
> > > --
> > > AY
> >
> >
> >
> >
> > --
> > Jonathan Ellis
> > co-founder, http://www.datastax.com
> > @spyced
> >
>



-- 
Benjamin Roth
Prokurist

Jaumo GmbH · www.jaumo.com
Wehrstraße 46 · 73035 Göppingen · Germany
Phone +49 7161 304880-6 · Fax +49 7161 304880-1
AG Ulm · HRB 731058 · Managing Director: Jens Kammerer

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message