Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of kohlisankalp@gmail.com
 designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20130709005809.GA6024@quantcast.com>
References: <20130709005809.GA6024@quantcast.com>
From: sankalp kohli <kohlisankalp@gmail.com>
Date: Mon, 8 Jul 2013 18:34:40 -0700
Message-ID: 
 <CAEPxca1rv41Dp+XNshboYZ6F7tJnYXPFOs8Yew2rn1NR=YxTJA@mail.gmail.com>
Subject: Re: Trying to write when at cassandra capacity
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a11c1de30985f8e04e10a2c8c

--001a11c1de30985f8e04e10a2c8c
Content-Type: text/plain; charset=ISO-8859-1

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 <fsareshwala@quantcast.com
> 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 dropped or
> cassandra will hit an OOM -- does anyone know which one?). The sstables on
> disk
> won't magically disappear so cassandra won't be able to service the write
> requests.
>
> Has anyone run into this situation before and does anyone know for sure
> what
> happens? I wanted to write in to confirm whether my intuition was correct
> or
> not.
>
> Faraaz
>

--001a11c1de30985f8e04e10a2c8c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I dont know what exactly will happen. These are the things=
 which might happen<div style>1) Commit log on disk gets recycled so I am a=
ssuming it might keep working.</div><div style>2) SStable wont be able to c=
reate new files so it will see an IO exception.=A0</div>

<div style><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Mon, Jul 8, 2013 at 5:58 PM, Faraaz Sareshwala <span dir=
=3D"ltr">&lt;<a href=3D"mailto:fsareshwala@quantcast.com" target=3D"_blank"=
>fsareshwala@quantcast.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">What does cassandra do when it is at its dat=
a capacity (disk drives and memtable<br>
is full) and writes continue to pour in? My intuition says that cassandra w=
on&#39;t<br>
be able to handle the new writes (they will either get silently dropped or<=
br>
cassandra will hit an OOM -- does anyone know which one?). The sstables on =
disk<br>
won&#39;t magically disappear so cassandra won&#39;t be able to service the=
 write<br>
requests.<br>
<br>
Has anyone run into this situation before and does anyone know for sure wha=
t<br>
happens? I wanted to write in to confirm whether my intuition was correct o=
r<br>
not.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Faraaz<br>
</font></span></blockquote></div><br></div>

--001a11c1de30985f8e04e10a2c8c--