On Fri, Jul 1, 2011 at 3:16 AM, Sylvain Lebresne wrote:
> To make it clear what the problem is, this is not a repair problem. This is
> a gossip problem. Gossip is reporting that the remote node is a 0.7 node
> and repair is just saying "I cannot use that node because repair has changed
> and the
Hi All, sorry for taking so long to answer. I was away from the
internet.
>> Héctor, when you say "I have upgraded all my cluster to 0.8.1", from
> >> which version was
> >> that: 0.7.something or 0.8.0 ?
0.7.6-2 to 0.8.1
> This is the same behavior I reported in 2768 as Aaron referenced ...
> >
To make it clear what the problem is, this is not a repair problem. This is
a gossip problem. Gossip is reporting that the remote node is a 0.7 node
and repair is just saying "I cannot use that node because repair has changed
and the 0.7 node will not know how to answer me correctly", which is the
This is the same behavior I reported in 2768 as Aaron referenced ...
What was suggested for us was to do the following:
- Shut down the entire ring
- When you bring up each node, do a nodetool repair
That didn't immediately resolve the problems. In the end, I backed up
all the data, removed the
Héctor, when you say "I have upgraded all my cluster to 0.8.1", from
which version was
that: 0.7.something or 0.8.0 ?
If this was 0.8.0, did you run successful repair on 0.8.0 previous to
the upgrade ?
--
Sylvain
On Fri, Jul 1, 2011 at 5:59 AM, Terje Marthinussen
wrote:
> Unless it is a 0.8.1 R
Unless it is a 0.8.1 RC or beta
On Fri, Jul 1, 2011 at 12:57 PM, Jonathan Ellis wrote:
> This isn't 2818 -- (a) the 0.8.1 protocol is identical to 0.8.0 and
> (b) the whole cluster is on the same version.
>
> On Thu, Jun 30, 2011 at 9:35 PM, aaron morton
> wrote:
> > This seems to be a known is
This isn't 2818 -- (a) the 0.8.1 protocol is identical to 0.8.0 and
(b) the whole cluster is on the same version.
On Thu, Jun 30, 2011 at 9:35 PM, aaron morton wrote:
> This seems to be a known issue related
> to https://issues.apache.org/jira/browse/CASSANDRA-2818 e.g. https://issues.apache.org/
This seems to be a known issue related to
https://issues.apache.org/jira/browse/CASSANDRA-2818 e.g.
https://issues.apache.org/jira/browse/CASSANDRA-2768
There was some discussion on the IRC list today, driftx said the simple fix was
a full cluster restart. Or perhaps a rolling restart with the
Hi all,
I have upgraded all my cluster to 0.8.1. Today one of the disks in one
of the nodes died. After replacing the disk I tried running repair, but
this message appears:
INFO [manual-repair-bdb4055a-d370-4d2a-a1dd-70a7e4fa60cf] 2011-06-30
20:36:25,085 AntiEntropyService.java (line 179) Exclud
