cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathiresan S <kathiresanselva...@gmail.com>
Subject Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)
Date Tue, 15 Mar 2016 17:46:53 GMT
ok, thanks...

On Tue, Mar 15, 2016 at 1:29 PM, ssivikt@gmail.com <ssivikt@gmail.com>
wrote:

> Note, that DataStax Enterprise still uses C* v2.1......
>
>
> On 03/15/2016 08:25 PM, Kathiresan S wrote:
>
> Thank you all !
>
> Thanks,
> Kathir
>
>
> On Tue, Mar 15, 2016 at 5:50 AM, <ssivikt@gmail.com>ssivikt@gmail.com <
> ssivikt@gmail.com> wrote:
>
>> I think that it's not ready, since it has critical bugs. See emails about
>> C* memory leaks....
>>
>>
>> On 03/15/2016 01:15 AM, Robert Coli wrote:
>>
>> On Mon, Mar 14, 2016 at 12:40 PM, Kathiresan S <
>> <kathiresanselvaraj@gmail.com>kathiresanselvaraj@gmail.com> wrote:
>>
>>> We are planning for Cassandra upgrade in our production environment.
>>> Which version of Cassandra is stable and is advised to upgrade to, at
>>> the moment?
>>>
>>
>>
>> https://www.eventbrite.com/engineering/what-version-of-cassandra-should-i-run/
>>
>> (IOW, you should run either 2.1.MAX or 2.2.5)
>>
>> Relatively soon, the answer will be "3.0.x", probably around the time
>> where 3.0.x is >= 6.
>>
>> After this series, the change in release cadence may change the above
>> rule of thumb.
>>
>> =Rob
>>
>>
>> --
>> Thanks,
>> Serj
>>
>>
>
> --
> Thanks,
> Serj
>
>

Mime
View raw message