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] Updated: (DERBY-3382) Replication: Slave must inform master if DBs are out of sync.
Date Tue, 01 Apr 2008 09:46:25 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Øystein Grøvlen updated DERBY-3382:
-----------------------------------

    Fix Version/s:     (was: 10.4.1.0)
                       (was: 10.5.0.0)
                   10.4.0.0

Reset fix version.  Bug was fixed before 10.4 release branch was created.  It was just the
test patch that needed to be merged.

> Replication: Slave must inform master if DBs are out of sync.
> -------------------------------------------------------------
>
>                 Key: DERBY-3382
>                 URL: https://issues.apache.org/jira/browse/DERBY-3382
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: Øystein Grøvlen
>            Assignee: Jørgen Løland
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3382-1a.diff, derby-3382-1a.stat, derby-3382-1b.diff, derby-3382-1b.stat,
derby-3382-test-1a.diff, derby-3382-test-1a.stat, derby-3382-test-1b.diff, derby-3382-test-1b.stat
>
>
> If I copy the database to the slave before booting the master, slave will be out of sync
with the master since new log records are created during booting.  The slave will then stop
replication, but the master will not be notified.
> If I then try to stop or failover the master the master will hang.

-- 
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