[
https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583577#action_12583577
]
V.Narayanan commented on DERBY-3552:
------------------------------------
Documentation related observation
----------------------------------------------
>Path two requires a complete restart of replication after installing jars
>(including copying the database
>to the slave location). On the other hand, path 2 ensures that the slave is
>100% up to date and ready for use
>after a failover has occurred.
I think we should mention that the restart would mean deleting the original
slave DB and doing
the replication setup from the beginning.
General observation (not to be documented)
-------------------------------------------------------
>On the other hand, path 2 ensures that the slave is 100% up to date and ready
>for use after a failover has
>occurred.
Path 1 also ensures that the database is up to date and ready for use provided
the user following the re-installation
of jars that would be required after failover.
General
I feel that stopping and restarting replication everytime a jar is installed is
onerous.
But then probably both the steps mentioned can be automated with legerdemain
during
development of the application that uses replication.
> Handle jar files that are installed when replication is enabled
> ---------------------------------------------------------------
>
> Key: DERBY-3552
> URL: https://issues.apache.org/jira/browse/DERBY-3552
> Project: Derby
> Issue Type: Sub-task
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
