You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "V.Narayanan (JIRA)" <ji...@apache.org> on 2008/04/14 11:53:06 UTC

[jira] Assigned: (DERBY-3617) failover on slave hangs after stopmaster on master.

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

V.Narayanan reassigned DERBY-3617:
----------------------------------

    Assignee: V.Narayanan

> failover on slave hangs after stopmaster on master.
> ---------------------------------------------------
>
>                 Key: DERBY-3617
>                 URL: https://issues.apache.org/jira/browse/DERBY-3617
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.5.0.0
>         Environment: OS: Fedora release 7 (Moonshine) 32bits - Linux 2.6.23.15-80.fc7PAE #1 SMP Sun Feb 10 17:14:36 EST 2008 GNU/Linux
> JVM: java version "1.6.0_01"
> Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
> Java HotSpot(TM) Server VM (build 1.6.0_01-b06, mixed mode)
> SVN: 647063
>            Reporter: Ole Solberg
>            Assignee: V.Narayanan
>            Priority: Minor
>         Attachments: db_master-derby.log, db_slave-derby.log, log.out
>
>
> 0. Master and slave in repl. mode.
> 1. master: stopmaster
> 2. slave failover.
>    hangs.....
> According to "Functional Specification for Derby Replication" Rev. 9.0:
> "Failover": "... . The command is only accepted  on the slave if the network conection with the master is down." so expecting failover to return valid Connection.
> However, failover never finish.
> See attached master and slave derby.log and testrun log.out.

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