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

Jaakko Laine edited comment on CASSANDRA-559 at 11/17/09 1:18 PM:
------------------------------------------------------------------

I suppose this is because Header in 0.4 uses EndPoint while 0.5 uses 
InetAddress. EndPoint is basically String host + int port, so writing some 
kludgish stuff to bridge the gap should be relatively easy.

For version 0.5.0: On the wire use 0.4 Header format (convert InetAddress to 
EndPoint before serializing) and also build a mechanism to be able to 
deserialize 0.5 Header either from serialized 0.4 Header or 0.5 Header.

For 0.5.1 (or whatever the number might be): Start using 0.5 Header on the wire 
and remove the kludge to build 0.5 Header from serialized 0.4 Header.

This way 0.4 would be able to gossip with 0.5.0, and 0.5.1 with 0.5.0.

Don't know if it is worth the trouble especially since we would anyway lose the 
port number when converting to EndPoint.


      was (Author: jaakko):
    I suppose this is because Header in 0.4 uses EndPoint while 0.5 uses 
InetAddress. EndPoint is basically String host + int port, so writing some 
kludgish stuff to build 0.5 Header from serialized 0.4 Header and vice versa 
would not be very difficult. Don't know if this is worth the trouble though, as 
we're anyway going to lose port number when building 0.4 Header from 0.5 Header.

  
> Allow 0.5 node to participate in 0.4 gossip ring
> ------------------------------------------------
>
>                 Key: CASSANDRA-559
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-559
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: 559.patch
>
>
> this would allow incremental upgrading of 0.4 cluster to 0.5 instead of 
> having to shut down, upgrade, restart all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to