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 duncan.sands@gmail.com
 designates 74.125.82.172 as permitted sender)
Message-ID: <55115D9B.5080303@gmail.com>
Date: Tue, 24 Mar 2015 13:50:35 +0100
From: Duncan Sands <duncan.sands@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: error deleting messages
References: 
 <CAKD3BwAppozFsQgMow7EV160jPGSe2cHt_EvGv=oi-xzBEZW5A@mail.gmail.com>
In-Reply-To: 
 <CAKD3BwAppozFsQgMow7EV160jPGSe2cHt_EvGv=oi-xzBEZW5A@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Hi Joss,

On 24/03/15 12:58, joss Earl wrote:
> I run into trouble after a while if I delete rows, this happens in both 2.1.3
> and 2.0.13, and I encountered the same problem when using either the datastax
> java driver or the stock python driver.
> The problem is reproducible using the attached python program.
>
> Once the problem is encountered, the table becomes unusable..
>
> cqlsh:test1> select id from msg limit 1;
> Request did not complete within rpc_timeout.

my guess is that due to previous delete attempts your table is filled with 
tombstones, and this is why the read times out: it hits the tombstone limit. 
Check your Cassandra node logs to see if they mention tombstones.

Ciao, Duncan.

>
> So, questions are:
> am I doing something wrong ?
> is this expected behaviour ?
> is there some way to fix the table and make it usable again once this has happened ?
> if this is a bug, what is the best way of reporting it ?
>
> Many thanks
> Joss