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] Commented: (DERBY-2921) Replication: Add a network service that connects the master and slave Derby instances
Date Wed, 11 Jul 2007 14:08:04 GMT

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

V.Narayanan commented on DERBY-2921:

The Proof of concept attached to 2872 achieves the most basic level of tranfer that might
be required, namely the transfer of individual log records using RMI.

This needs to be built into a framework for generic message transfer between the master and
the slave

I believe lot of considerations would go into such a communication channel

A few already pointed out by Rick in the previous discussion in Derby-2872 like handling
Man in the middle attacks and the associated security precautions that we will take for the
same etc.

But as a first step I believe that we should look into building the basic communication
system, and plan in such a way that we are able to plug in security seamlessly later, (i.e.)
concentrate on building the functionality first ,documenting and appropriately coding for
enhancements that may be required later.

Here are a few random thoughts towards this

1) we need a socket server on the slave to listen to incoming log records and other
    information from the master
2) The master connects to this socket server that will be running on the slave.
3) Decide on the data structure that will be sent to this socket server and ensure that
    it is able to accomodate not only logRecords but also other messages that may be required.
4) would SSL need to be enabled in the communication between the master and slave?
    if yes,
    Should the sockets be created the same way it is being done in  
    org.apache.derby.client.net.OpenSocketAction and NetworkServerControlImpl 
    supporting only SSL_OFF in the first version and the other SSL modes later?
5) How do we write the communication data structures such that encryption 
    IF NECESSARY can be plugged in at a later stage?
6) Would we need to support any other authentication mechanishms?

Any additional cases that need to be handled and views in the direction of this issue
will be highly appreciated.

> 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
> 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