db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4196) Document initiation of replication from cleanly shut down database
Date Mon, 13 Jul 2009 18:31:15 GMT

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

Kim Haase commented on DERBY-4196:

Thanks, Knut, I was wondering about those sentences. Those are great suggestions.

I am wondering about the later part of the paragraph on unlogged operations -- it describes
exactly what the error message says:

"The message instructs the user to unfreeze the database to allow the operations to complete,
and then to specify startMaster=true again."

I think I should just remove that sentence and have the paragraph end with "an error message

That leaves the issue of the actual error message text. XRE23 says, "Replication master cannot
be started since unlogged operations are in progress, unfreeze to allow unlogged operations
to complete and restart replication." Should it be left as it is, since the only way it's
likely to come up is if someone did freeze the database instead of shutting it down?

I'll post a patch that includes your suggestions.

> Document initiation of replication from cleanly shut down database
> ------------------------------------------------------------------
>                 Key: DERBY-4196
>                 URL: https://issues.apache.org/jira/browse/DERBY-4196
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, Replication
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
>            Priority: Minor
> The admin guide describes how to start replication.
> http://db.apache.org/derby/docs/dev/adminguide/cadminreplicstartrun.html
> It describes two steps that must be performed before the database is copied from the
master to the slave:
> 1. Boot the database on the master system
> 2. Freeze the database (CALL SYSCS_UTIL.SYSCS_FREEZE_DATABASE())
> Those two steps could be replaced with a single step:
> 1-2) Make sure the database on the master system is shut down cleanly
> This works because then there is no recovery to be performed when the database later
is booted in master mode, and neither the log nor the database will be modified during boot,
so the master database will stay completely in sync with the slave.
> Advantages with the alternative procedure are:
> - no need to keep a process running with the database booted and frozen while copying
the database from the master system to the slave system
> - uncommitted transactions that are active at the time of the copying won't cause any
problems (DERBY-3896)

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

View raw message