cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Burton <bur...@spinn3r.com>
Subject Re: [Marketing Mail] Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.
Date Thu, 04 Aug 2016 18:45:16 GMT
BTW. we think we tracked this down to using large partitions to implement
inverted indexes.  C* just doesn't do a reasonable job at all with large
partitions so we're going to migrate this use case to using Elasticsearch

On Wed, Aug 3, 2016 at 1:54 PM, Ben Slater <ben.slater@instaclustr.com>
wrote:

> Yep,  that was what I was referring to.
>
>
> On Thu, 4 Aug 2016 2:24 am Reynald Bourtembourg <
> reynald.bourtembourg@esrf.fr> wrote:
>
>> Hi,
>>
>> Maybe Ben was referring to this issue which has been mentioned recently
>> on this mailing list:
>> https://issues.apache.org/jira/browse/CASSANDRA-11887
>>
>> Cheers,
>> Reynald
>>
>>
>> On 03/08/2016 18:09, Romain Hardouin wrote:
>>
>> > Curious why the 2.2 to 3.x upgrade path is risky at best.
>> I guess that upgrade from 2.2 is less tested by DataStax QA because DSE4
>> used C* 2.1, not 2.2.
>> I would say the safest upgrade is 2.1 to 3.0.x
>>
>> Best,
>>
>> Romain
>>
>>
>> --
> ————————
> Ben Slater
> Chief Product Officer
> Instaclustr: Cassandra + Spark - Managed | Consulting | Support
> +61 437 929 798
>



-- 

We’re hiring if you know of any awesome Java Devops or Linux Operations
Engineers!

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>

Mime
View raw message