Thanks a lot for clarifying. We'll complete the upgrade of all nodes.
Regards.
On Mon, Sep 17, 2012 at 3:51 PM, Sylvain Lebresne wrote:
> On Mon, Sep 17, 2012 at 11:06 AM, B R
> wrote:
> > Could this problem be due to running repair on a node upgraded to 1.0.11
> but
> > the other node in the c
On Mon, Sep 17, 2012 at 11:06 AM, B R wrote:
> Could this problem be due to running repair on a node upgraded to 1.0.11 but
> the other node in the cluster is still at 0.8.x ?
Yes, repair (as all operation requiring streaming) doesn't work
correctly across major Cassandra version. First thing you
Sorry for the delay; been out of the loop.
Could this problem be due to running repair on a node upgraded to 1.0.11
but the other node in the cluster is still at 0.8.x ?
On Fri, Sep 7, 2012 at 9:11 PM, Sylvain Lebresne wrote:
> That obviously shouldn't happen and I don't remember any open ticket
That obviously shouldn't happen and I don't remember any open ticket
related to that. You might want to open a ticket on jira
(https://issues.apache.org/jira/browse/CASSANDRA).
--
Sylvain
On Fri, Sep 7, 2012 at 10:50 AM, B R wrote:
> We have upgraded a 0.8 cluster to 1.0.11. After upgrading the
We have upgraded a 0.8 cluster to 1.0.11. After upgrading the first node
and running upgradesstables, we have run a routine repair operation, This
operation has been running for a long time and does not seem to be
progressing.
Running netstats has shown unexpected values for percentages as shown
b
