[
https://issues.apache.org/jira/browse/DERBY-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517632
]
Rick Hillegas commented on DERBY-2921:
--------------------------------------
Thanks for the patch, Naryanan. I have an initial question about
ReplicationMessage. It appears to implement Serializable. That means that the
exchange protocol relies on both ends of the connection being at the same rev
level of Derby and perhaps even compiled by the same machine. I'm not sure this
is what you want, particularly since the architecture allows for large webs of
Derby nodes, each of which may host both slaves and masters. I think that the
functional spec should address the topic of version agreement between nodes.
For instance, do you envision that newly upgraded masters will propagate the
new Derby rev to their slaves?
> Replication: Add a network service that connects the master and slave Derby
> instances
> -------------------------------------------------------------------------------------
>
> Key: DERBY-2921
> URL: https://issues.apache.org/jira/browse/DERBY-2921
> Project: Derby
> Issue Type: Sub-task
> Components: Services
> Affects Versions: 10.4.0.0
> Reporter: Jørgen Løland
> Assignee: V.Narayanan
> Attachments: Replication_Network_v1.diff, Replication_Network_v1.stat
>
>
> A network connection is required between the master and slave Derby instances
> of a replicated database. The connection will be used to send many kinds of
> messages, including:
> * log records
> * the database (when replication is started)
> * master -> slave commands (like "stop replication")
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
