> It hits an OOM.
To add a little more colour because I stepped through this with someone the
other day.
When memtables are not removed from the memtable flush queue (because they have
not been written) the queue will fill up. When this happens the flush process
will block trying to fill the qu
On Mon, Jul 8, 2013 at 5:58 PM, Faraaz Sareshwala wrote:
> What does cassandra do when it is at its data capacity (disk drives and
> memtable
> is full) and writes continue to pour in? My intuition says that cassandra
> won't
> be able to handle the new writes (they will either get silently dropp
I dont know what exactly will happen. These are the things which might
happen
1) Commit log on disk gets recycled so I am assuming it might keep working.
2) SStable wont be able to create new files so it will see an IO exception.
On Mon, Jul 8, 2013 at 5:58 PM, Faraaz Sareshwala wrote:
> What
What does cassandra do when it is at its data capacity (disk drives and memtable
is full) and writes continue to pour in? My intuition says that cassandra won't
be able to handle the new writes (they will either get silently dropped or
cassandra will hit an OOM -- does anyone know which one?). The
