[
https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583571#action_12583571
]
jorgenlo edited comment on DERBY-3552 at 3/31/08 12:00 AM:
----------------------------------------------------------------
Summarizing the documentation discussion. As I see it, there are two
(suboptimal) paths for installing jars on the slave database:
1: Manually install the jar files on the "used-to-be-slave" database after a
failover has occurred, or
2: When jar files have been installed on the master, replication is stopped and
restarted from step 1
It is up to the DB owner to decide which of these paths is the better choice
for a database. 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.
was (Author: jorgenlo):
Summarizing the documentation discussion. There are two paths for
installing jars on the slave database:
> 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.
