great tips. I will investigate further with your suggestions in mind.
Hopefully the problem has gone away since I pulled in fresh data on the node
with problems.
On Apr 13, 2011, at 3:54 AM, aaron morton wrote:
> Ah, unreadable rows and in the validation compaction no less. Makes a little
>
Ah, unreadable rows and in the validation compaction no less. Makes a little
more sense now.
Anyone help with the EOF when deserializing columns ? Is the fix to run scrub
or drop the sstable ?
Here's a a theory, AES is trying to...
1) Create TreeRequest 's that specify a range we want to vali
There is no "Repair session" message either. It just starts with a message
like:
INFO [manual-repair-2af33a51-f46a-4ba2-b1fb-ead5159dc723] 2011-04-10
14:00:59,051 AntiEntropyService.java (line 770) Waiting for repair requests:
[#, #, #, #]
NETSTATS:
Mode: Normal
Not sending any streams.
Not
Do you see a message starting "Repair session " and ending with "completed
successfully" ?
Or do you see any streaming activity using "nodetool netstats"
Repair can hang if a neighbour dies and fails to send a requested stream. It
will timeout after 24 hours (I think).
Aaron
On 12 Apr 2011,
On 12/04/2011 13:31, Jonathan Colby wrote:
There are a few other threads related to problems with the nodetool repair in
0.7.4. However I'm not seeing any errors, just never getting a message that
the repair completed successfully.
In my production and test cluster (with just a few MB data)
There are a few other threads related to problems with the nodetool repair in
0.7.4. However I'm not seeing any errors, just never getting a message that
the repair completed successfully.
In my production and test cluster (with just a few MB data) the repair
nodetool prompt never returns and
