db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3428) Doing a replication failover should shutdown the database and the connection should no longer be available
Date Sun, 24 Feb 2008 10:08:14 GMT

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

V.Narayanan updated DERBY-3428:
-------------------------------

    Attachment: Derby3428_v1.stat
                Derby3428_v1.diff

* This patch is not for a commit *

I tried integrating the Derby-3455 and the Derby-3428 patches
and tried running the repro. It runs fine.

During the course of the run I observed that if a slave is started
on a port that is being already used I get the following exception

ERROR XJ040: Failed to start database 'masterDB', see the next exception for details.
ERROR XRE04: Could not establish a connection to the peer of the replicated database 'masterDB'
on address 'localhost:8001'.

I am not sure this is the right message in this situation. I think port in use will be
a better exception here.I will wait till tomorrow and raise a JIRA.

I also observed that startmaster on a port other than the port at which
the slave is listening does not allow subsequent attempts at the right port.
I guess there is a JIRA for this already.

> Doing a replication failover should shutdown the database and the connection should no
longer be available
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3428
>                 URL: https://issues.apache.org/jira/browse/DERBY-3428
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: Derby3428.diff, Derby3428.stat, Derby3428_v1.diff, Derby3428_v1.stat
>
>
> Oystein says (as part of comments in Derby-3205)
> After executing a failover, I am told that the database is shut down, but I still able
to use the connection to access the database:
> 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)> call syscs_util.syscs_unfreeze_database();
> 0 rows inserted/updated/deleted
> ij(CONNECTION1)> connect 'jdbc:derby:masterDB;user=oystein;password=pass;failover=true';
> ERROR XRE20: Failover performed successfully for database 'null', the database has been
shutdown.
> ij(CONNECTION1)> select * from t;
> I
> -----------
> 1
> 2
> 3
> 4
> 5
> 6
> 7
> 8
> 9
> 10
> 10
> 11 rows selected
> ij(CONNECTION1)>

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