[
https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582000#action_12582000
]
V.Narayanan commented on DERBY-3551:
------------------------------------
Thank you for watching this issue Kim.
I decided that we should not unfreeze. So now we just throw an exception if it
is found that
unlogged operations were running. The user needs to decide if he wants to
unfreeze.
So when the user calls the startMaster command we check to see if there were
any unlogged
operations running when the user called a freeze. If there were any unlogged
operations running
we throw an exception with the following message
"Replication master cannot be started since unlogged operations are in
progress, unfreeze to allow unlogged operations to complete and restart
replication"
> Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()
> ----------------------------------------------------------
>
> Key: DERBY-3551
> URL: https://issues.apache.org/jira/browse/DERBY-3551
> Project: Derby
> Issue Type: Sub-task
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Fix For: 10.5.0.0
>
> Attachments: Derby3551_1.diff, Derby3551_1.stat, Derby3551_2.diff,
> Derby3551_2.stat, Derby3551_3.diff, Derby3551_3.stat, runscript_import.sql
>
>
> Jorgen says-
> I suggest that the replication step in which the master database is frozen is
> replaced by a new system procedure to solve index and import:
> Old: SYSCS_UTIL.SYSCS_FREEZE_DATABASE()
> New: SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()
> The new system procedure should:
> 1) Freeze the database
> 2) Check if there are any ongoing transactions with unlogged operations. If
> so - unfreeze and abort. Otherwise:
> 3) Enable logging of unlogged operations
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
