[
https://issues.apache.org/jira/browse/DERBY-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-3384:
-------------------------------
Attachment: Derby_3384_v2.stat
Derby_3384_v2.diff
>I wonder whether unfreeze() should be called after startReplicationMasterRole
>is called?
>Otherwise, I would think there will be a window where transactions may generate
>log records that will not be replicated.
Thank you for looking at the patch and for the comments Oystein!
I have followed your suggestion!
> Replication: startMaster does not unfreeze DB
> ---------------------------------------------
>
> Key: DERBY-3384
> URL: https://issues.apache.org/jira/browse/DERBY-3384
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0
> Reporter: Øystein Grøvlen
> Assignee: V.Narayanan
> Fix For: 10.4.0.0
>
> Attachments: Derby_3384_v1.diff, Derby_3384_v1.stat,
> Derby_3384_v2.diff, Derby_3384_v2.stat
>
>
> ij version 10.4
> ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass';
> ij> call SYSCS_UTIL.SYSCS_FREEZE_DATABASE();
> 0 rows inserted/updated/deleted
> ij> connect
> 'jdbc:derby:masterDB;user=oystein;password=pass;startMaster=true;slaveHost=localhost';
> ij(CONNECTION1)> select * from t order by i;
> I
> -----------
> 1
> 2
> 3
> 4
> 5
> 6
> 7
> 8
> 10
> 12
> 20
> 22
> 30
> 32
> 40
> 42
> 16 rows selected
> ij(CONNECTION1)> insert into t values (9), (10), (11), (12);
> The last statement never completes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
