[
https://issues.apache.org/jira/browse/DERBY-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568903#action_12568903
]
Øystein Grøvlen commented on DERBY-3382:
----------------------------------------
When I test this, I do not get the error message I expected on the master.
Below is an example where I do not connect to the masterDB and freeze it before
it is copied. Instead of the out-of-synch message, I get a could not establish
connection message. The slave prints the out-of-synch message. Note also that
if I try a normal connect afterwards, a first attempt to freeze the DB will
fail with NPE, both a second attempt to call freeze or 'quit' will then hang.
ij version 10.4
ij> connect
'jdbc:derby:masterDB;user=oystein;password=pass;startMaster=true;slaveHost=localhost';
ERROR XRE04: Could not establish a connection to the peer of the replicated
database 'masterDB' on address 'localhost:-1'.
ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass';
ij> select sum(i), avg(i), count(*), max(i) from t;
1 |2 |3 |4
-----------------------------------------------
528 |16 |32 |32
1 row selected
ij> call syscs_util.syscs_freeze_database();
ERROR 38000: The exception 'java.lang.NullPointerException' was thrown while
evaluating an expression.
ERROR XJ001: Java exception: ': java.lang.NullPointerException'.
ij> quit
<hangs>
> 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
>
>
> 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.
