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 michalm@opera.com designates
 213.236.208.81 as permitted sender)
Message-ID: <51754112.8010406@opera.com>
Date: Mon, 22 Apr 2013 15:54:26 +0200
From: Michal Michalski <michalm@opera.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Unable to drop secondary index
References: <516FE96C.7040301@opera.com>
 <F1C863AC-9E1C-4718-B0A7-90ACF7730AF7@thelastpickle.com>
 <51710846.40808@opera.com> <517149C6.4050902@opera.com>
 <B0BBB562-E29C-49C8-90D1-7C5A60D41169@thelastpickle.com>
In-Reply-To: <B0BBB562-E29C-49C8-90D1-7C5A60D41169@thelastpickle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

W dniu 21.04.2013 22:17, aaron morton pisze:
> This is a tricky one to diagnose remotely. I could try using nodetool resetlocalschema on each node, it's just wild guess incase there is something odd one one node.

I've run it on one node (let's call it A) and it finished without any 
problems. Then I've run it on the second one (B) and I ended up with my 
production keyspace missing. I can see entries in system.schema_column*, 
data are - obviously - on disk, but I can't use it and node reports 205 
KB of data.

Shortly after this, node A went OOM (never happened before). After 
restart it reports different schema version at first (describe cluster 
in CLI), but it is fixed after a while. However, few minutes later it is 
reported as Down by other nodes and it doesn't see other nodes as 
well... After restart - the same.

Will try to investigate the problem with A first; For now B seems to be 
a candidate for removing/rejoining the ring and setting it up from 
scratch ;-)

M.