Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of potekhin@bnl.gov designates
 130.199.3.132 as permitted sender)
Message-ID: <4EDACE10.6010804@bnl.gov>
Date: Sat, 03 Dec 2011 20:34:08 -0500
From: Maxim Potekhin <potekhin@bnl.gov>
User-Agent: Mozilla/5.0 (Windows NT 6.0;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Repair failure under 0.8.6
References: 
 <CACCYQcyG2rmJJzxQ_5YYYp8itxvX1pjey-dtXn1MS35dqjL2Lw@mail.gmail.com>
 <4EDAAF7E.40502@bnl.gov>
 <CAO5xsd3c8jk3BzKj2tsJXziKjO0PtJp53AiHj==+ZvC796JH1w@mail.gmail.com>
In-Reply-To: 
 <CAO5xsd3c8jk3BzKj2tsJXziKjO0PtJp53AiHj==+ZvC796JH1w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Thank you Peter. Before I look into details as you suggest,
may I ask what you mean "automatically restarted"? They way
the box and Cassandra are set up in my case is such that the
death of either if final.

Also, how do I look for full GC? I just realized that in the latest
install, I might have omitted capping the heap size -- and the
nodes have 48GB each. I guess this could be a problem, precipitating
GC death, right?

Thank you

Maxim


On 12/3/2011 7:46 PM, Peter Schuller wrote:
>> quite understand how Cassandra declared a node dead (in the below). Was is a
>> timeout? How do I fix that?
> I was about to respond to say that repair doesn't fail just due to
> failure detection, but this appears to have been broken by
> CASSANDRA-2433 :(
>
> Unless there is a subtle bug the exception you're seeing should be
> indicative that it really was considered Down by the node. You might
> grep the log for references ot the node in question (UP or DOWN) to
> confirm. The question is why though. I would check if the node has
> maybe automatically restarted, or went into full GC, etc.
>