[
https://issues.apache.org/jira/browse/DERBY-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542970
]
Øystein Grøvlen commented on DERBY-3021:
----------------------------------------
Thank you for adressing my comments Jørgen. The changes looks good, but it
seems you have forgotten to add ReplicationLogger to the patch. (I am bit
surprised that you have used inheritance here, but I guess that is a matter of
personal taste.)
My comments to 1c, 1e, and 3, are misunderstandings on my side. For some
reason I thought you were dealing with system properties, I did not see that it
was already volatile, and part of the error message did not show up when I
printed your patch. My bad.
> Replication: Add a ReplicationSlave controller that will manage replication
> on the slave side
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-3021
> URL: https://issues.apache.org/jira/browse/DERBY-3021
> Project: Derby
> Issue Type: Sub-task
> Components: Services
> Affects Versions: 10.4.0.0
> Reporter: Jørgen Løland
> Assignee: Jørgen Løland
> Attachments: derby-3021-1.diff, derby-3021-1.stat,
> derby-3021-1b.diff, derby-3021-1b.stat, derby-3021-2a.diff,
> derby-3021-2a.stat, derby-3021-2b.diff, derby-3021-2b.stat
>
>
> The replication slave role includes many tasks:
> * set up a network connection with the master
> * receive chunks of log from the master, and parse these into individual log
> records
> * append log records to the local log file
> * make sure that the recovery process is not allowed to access the logfile we
> are currently writing to
> * etc
> This issue is for adding a controller that will start/stop/initiate all
> services needed for the replication slave role.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
