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-3235) Implement the replication stop functionality
Date Thu, 03 Jan 2008 10:13:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555522#action_12555522
] 

Øystein Grøvlen commented on DERBY-3235:
----------------------------------------

It seems to me that there are still pieces that are missing from the implementation of stop
replication.  I cannot find any code that interrupts the ongoing booting of the database at
the slave.  When the patch for failover (DERBY-3254) is committed, executing stop will cause
the slave to complete its booting and be able to start serving clients.  I guess that is not
the intention.

> Implement the replication stop functionality
> --------------------------------------------
>
>                 Key: DERBY-3235
>                 URL: https://issues.apache.org/jira/browse/DERBY-3235
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: StopImplementation_v1.diff, StopImplementation_v1.stat, StopImplementation_v1_NotForCommit.diff,
StopImplementation_v1_NotForCommit.stat, StopImplementation_v2.diff, StopImplementation_v2.stat
>
>


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


Mime
View raw message