nd timestamp comparison etc.)
>
> -Original Message-
> From: Benedict Elliott Smith [mailto:bened...@apache.org]
> Sent: Tuesday, February 13, 2018 2:25 PM
> To: dev@cassandra.apache.org
> Subject: Re: Use of OpOrder in memtable
>
> If you look closely, there can be
d and timestamp comparison etc.)
-Original Message-
From: Benedict Elliott Smith [mailto:bened...@apache.org]
Sent: Tuesday, February 13, 2018 2:25 PM
To: dev@cassandra.apache.org
Subject: Re: Use of OpOrder in memtable
If you look closely, there can be multiple memtables extant at
If you look closely, there can be multiple memtables extant at once. While
all "new" writes are routed to the latest memtable, there may still be
writes that have begun but not yet completed. The memtable cannot be
flushed until any stragglers have completed, and some stragglers *may* still
need
Hi all,
I'm trying to understand the behavior of memtable when writes/flush operations
are going on in parallel.
In my understanding, once a memtable is full it is queued for flushing and a
new memtable is created for ongoing write operations.
However, I was looking at the code and it looks lik
