[
https://issues.apache.org/jira/browse/DERBY-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511732
]
Jørgen Løland commented on DERBY-2922:
--------------------------------------
When the master and slave have connected and the database has been sent to the
slave, log records generated on the master side should be forwarded to the
slave.
In the proof of concept code in DERBY-2872, this is performed by calling
LogToFile.appendLogRecord on the slave via RMI. This is not a good idea because
forcing an RMI call for every log write will result in high performance
degradation. It would be better to append these log records to a buffer on the
master, and have a separate log shipping service that reads log records from
the buffer and sends them to the slave every now and then.
The current plan-sketch for the master includes:
* add a buffer for log records
* modify LogFactory in rawstore to append log records to the buffer (only in
master mode of course)
* add a log shipping service that reads log records from the buffer and sends
them to the slave
> Replication: Add master replication mode
> -----------------------------------------
>
> Key: DERBY-2922
> URL: https://issues.apache.org/jira/browse/DERBY-2922
> Project: Derby
> Issue Type: New Feature
> Components: Miscellaneous
> Affects Versions: 10.4.0.0
> Reporter: Jørgen Løland
> Assignee: Jørgen Løland
>
> One Derby instance will have the master role and another Derby instance will
> have the slave role when a database is replicated. See the functional
> specification of DERBY-2872 for more details about the roles.
> This JIRA is for issues that are part of the master role.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
