db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2921) Replication: Add a network service that connects the master and slave Derby instances
Date Sat, 25 Aug 2007 13:45:31 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

V.Narayanan updated DERBY-2921:

    Attachment: Replication_Network_v3.stat

Changes from v2 of the patch

Introduction of a initiator message sent from the master to the

The initator contains the UID of the message that is sent
from the master to the slave. The slave upon reception of
the initiator message checks the UID to ensure that the
value is equal to the UID of its message class.

If it is not equal it throws sends a message tagged as a
error to the slave and throws an IOException and fails to

If it is equal it sends a message tagged as an acknowledgment
to the master.

readExternal() and writeExternal() now recognize a version
number that is marshalled between the slave and the master

This would be useful at a later stage when we decide that
a master and a slave that is at different UID of messages
can still be allowed to exchange messages with a switch on
the version number that is passed.

Slave now defaults to localhost and 8001

If the slave is started without mentioning the hostname
and the port number then it defaults to using localhost
and 8001 port number. This was missed out in v2.

> 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:
>            Reporter: Jørgen Løland
>            Assignee: V.Narayanan
>         Attachments: Replication_Network_v1.diff, Replication_Network_v1.stat, Replication_Network_v2.diff,
Replication_Network_v2.stat, Replication_Network_v3.diff, Replication_Network_v3.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.

View raw message