cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Kjellman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5102) upgrading from 1.1.7 to 1.2.0 caused upgraded nodes to only know about other 1.2.0 nodes
Date Thu, 03 Jan 2013 16:58:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543066#comment-13543066
] 

Michael Kjellman commented on CASSANDRA-5102:
---------------------------------------------

at this point i just went ahead and upgraded all the nodes (was more worried about getting
the cluster back up)

I do notice though that the 1.2.0 nodes show net_version of 6.

as nodes were upgraded to 1.2.0 they didn't show up in the ring on the 1.1.7 side anymore.

gossipinfo on 1.2.0 nodes (ubuntu 12.04) look like:

/10.8.30.14
  RELEASE_VERSION:1.2.0
  NET_VERSION:6
  RPC_ADDRESS:0.0.0.0
  HOST_ID:24647d52-41eb-4df3-993e-51d4f841ca62
  LOAD:2.0129361318E11
  STATUS:NORMAL,70892159775195513221536376548285044050
  DC:DC1
  SCHEMA:da921e0b-4154-3601-9c76-6f61ca5f2872
  RACK:RAC1
  SEVERITY:-3.991605743852711E-11
/10.8.25.101
  RELEASE_VERSION:1.2.0
  RPC_ADDRESS:0.0.0.0
  NET_VERSION:6
  HOST_ID:dd3a40e2-fef1-4574-87b8-e2929fd80235
  LOAD:1.56018171896E11
  STATUS:NORMAL,42535295865117307932921825928971026436
  DC:DC1
  SCHEMA:da921e0b-4154-3601-9c76-6f61ca5f2872
  RACK:RAC2
  SEVERITY:0.019533560597218058 
                
> upgrading from 1.1.7 to 1.2.0 caused upgraded nodes to only know about other 1.2.0 nodes
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5102
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5102
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Michael Kjellman
>            Assignee: Brandon Williams
>            Priority: Blocker
>
> I upgraded as I have since 0.86 and things didn't go very smoothly.
> I did a nodetool drain to my 1.1.7 node and changed my puppet config to use the new merged
config. When it came back up (without any errors in the log) a nodetool ring only showed itself.
I upgraded another node and sure enough now nodetool ring showed two nodes.
> I tried resetting the local schema. The upgraded node happily grabbed the schema again
but still only 1.2 nodes were visible in the ring to any upgraded nodes.
> "Interesting" Log Lines:
>  INFO 14:43:41,997 Using saved token [42535295865117307932921825928971026436]
> ....
>  WARN 23:04:03,361 No host ID found, created 5cef7f51-688d-46c3-9fe4-6c82bde4bb98 (Note:
This should happen exa
> ctly once per node).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message