cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Memtable tuning in 1.0 and higher
Date Mon, 02 Jul 2012 07:43:30 GMT
I'm afraid not. It's too much change for an oldstable release series,
and the bulk of the change is to AtomicSortedColumns which doesn't
exist in 1.0, so even if we wanted to take a "maybe it's okay if we
release it first in 1.1.3 and then backport" approach it wouldn't
improve our safety margin since you'd basically need to rewrite the
patch.

On Sun, Jul 1, 2012 at 6:40 AM, Joost Van De Wijgerd <jwijgerd@gmail.com> wrote:
> Hi Jonathan,
>
> Looks good, any chance of porting this fix to the 1.0 branch?
>
> Kind regards
>
> Joost
>
> Sent from my iPhone
>
>
> On 1 jul. 2012, at 09:25, Jonathan Ellis <jbellis@gmail.com> wrote:
>
>> On Thu, Jun 28, 2012 at 1:39 PM, Joost van de Wijgerd
>> <jwijgerd@gmail.com> wrote:
>>> the currentThoughput is increased even before the data is merged into the
>>> memtable so it is actually measuring the throughput afaik.
>>
>> You're right.  I've attached a patch to
>> https://issues.apache.org/jira/browse/CASSANDRA-4399 to fix this.
>>
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of DataStax, the source for professional Cassandra support
>> http://www.datastax.com



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Mime
View raw message