This is the log after enabling TRACE on
org.apache.cassandra.net.OutboundTcpConnection:
DEBUG [WRITE-/54.215.70.YY] 2013-10-03 18:01:50,237
OutboundTcpConnection.java (line 338) Target max version is -2147483648; no
version information yet, will retry
TRACE [HANDSHAKE-/10.177.14.XX] 2013-10-03 18:
Hello,
During a rolling upgrade between 1.1.10 and 1.2.10, the newly upgrade nodes
keep showing the following log message:
INFO [HANDSHAKE-/10.176.249.XX] 2013-10-03 17:36:16,948
OutboundTcpConnection.java (line 399) Handshaking version with
/10.176.249.XX
INFO [HANDSHAKE-/10.176.182.YY] 2013-1
Nevermind the question. It was a firewall problem. Now the nodes between
different versions are able to see ach other! =)
Cheers,
Paulo
2013/10/2 Paulo Motta
> Hello,
>
> I just started the rolling upgrade procedure from 1.1.10 to 2.1.10. Our
> strategy is to simultaneously upgrade one server
Hello,
I just started the rolling upgrade procedure from 1.1.10 to 2.1.10. Our
strategy is to simultaneously upgrade one server from each replication
group. So, if we have a 6 nodes with RF=2, we will upgrade 3 nodes at a
time (from distinct replication groups).
My question is: do the newly upgra
Hello Charles,
Thank you very much for your detailed upgrade report. It'll be very helpful
during our upgrade operation (even though we'll do a rolling production
upgrade).
I'll also share our findings during the upgrade here.
Cheers,
Paulo
2013/9/24 Charles Brophy
> Hi Paulo,
>
> I just co
Hi Paulo,
I just completed a migration from 1.1.10 to 1.2.10 and it was surprisingly
painless.
The course of action that I took:
1) describe cluster - make sure all nodes are on the same schema
2) shutoff all maintenance tasks; i.e. make sure no scheduled repair is
going to kick off in the middle
On Tue, Sep 24, 2013 at 2:33 PM, Paulo Motta wrote:
> If anyone has upgraded from 1.1.X to 1.2.X, please feel invited to share
> any tips on issues you're encountered that are not yet documented.
>
Exceptions like the below relate to the change in hinted handoff format and
can be safely ignored a
Cool, sounds fair enough. Thanks for the help, Rob!
If anyone has upgraded from 1.1.X to 1.2.X, please feel invited to share
any tips on issues you're encountered that are not yet documented.
Cheers,
Paulo
2013/9/24 Robert Coli
> On Tue, Sep 24, 2013 at 1:41 PM, Paulo Motta wrote:
>
>> Doesn
On Tue, Sep 24, 2013 at 1:41 PM, Paulo Motta wrote:
> Doesn't the probability of something going wrong increases as the gap
> between the versions increase? So, using this reasoning, upgrading from
> 1.1.10 to 1.2.6 would have less chance of something going wrong then from
> 1.1.10 to 1.2.9 or 1.2
Doesn't the probability of something going wrong increases as the gap
between the versions increase? So, using this reasoning, upgrading from
1.1.10 to 1.2.6 would have less chance of something going wrong then from
1.1.10 to 1.2.9 or 1.2.10.
I'm hoping this reasoning is wrong and I can update dir
On Tue, Sep 24, 2013 at 1:17 PM, Paulo Motta wrote:
> What is the best version to upgrade from C* 1.1.10 to 1.2.X? Any
> suggestions?
>
Not sure what you're asking, but go to at-least-1.2.9. Current is 1.2.10,
so use that.
=Rob
11 matches
Mail list logo
