db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled
Date Mon, 31 Mar 2008 18:40:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583791#action_12583791

Øystein Grøvlen commented on DERBY-3552:

The difference between the two approaches is that when using the first approach, you do nothing
when the jar files are installed.  Instead, you wait until failover is needed.  At that time,
you will have to install the jar file on the former slave before clients that depend on this
jar file can continue.

With the second approach, you stop and restart replication in order to get the jar files installed
at the slave before a failover is actually needed.  This way, clients that depend on the jar
file can continue immediately after failover is performed.  In other words, the first approach,
is a lazy approach, while the second, is an eager approach.

> 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:,
>            Reporter: V.Narayanan

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message