[
https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582770#action_12582770
]
Kim Haase commented on DERBY-3552:
----------------------------------
Thanks, Narayanan. Let me see if I understand this correctly. Is the following
rephrasing correct?
If you install jar files on the master system while replication is running, the
same jars are not automatically installed on the slave. To ensure that the jars
are installed correctly on both systems, you need to force a failover, then
install the jars on the slave system (using either sqlj.remove_jar followed by
sqlj.install_jar, or sqlj.replace_jar). Then you have to start replication
again.
I'm not quite sure how to restart replication after a failover, though. How
many of the steps in "Starting and running replication" would you have to
repeat? Would you just have to specify the startSlave attribute on the slave
and then the startMaster attribute on the master?
Thanks again.
> 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.
