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 si
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 wrote:
> On Thu, Jun 28, 2012 at 1:39 PM, Joost van de Wijgerd
> wrote:
>> the currentThoughput is increased even before the data is me
On Thu, Jun 28, 2012 at 1:39 PM, Joost van de Wijgerd
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
Hi Jonathan,
The problem is not that I haven't allocated enough memory to the memtables,
the problem is that the memtable for this particular CF flushes too early
because the liveRation stays at 1.0. When looking at the code it seems to
me the the liveRatio is calculated based on
the throughput of
[moving to user list]
1.0 doesn't care about throughput or op count anymore, only whether
the total memory used by the *currrent* data in the memtables has
reached the global limit. So, it automatically doesn't count
"historical" data that's been overwritten in the current memtable.
So, you may
Hi,
I work for eBuddy, We've been using Cassandra in production since 0.6
(using 0.7 and 1.0, skipped 0.8) and use it for several Use Cases. One of
our uses is to persist our sessions.
Some background, in our case sessions are long lived, we have a mobile
messaging platform where sessions are ess
