[
https://issues.apache.org/jira/browse/DERBY-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589500#action_12589500
]
Ole Solberg commented on DERBY-3617:
------------------------------------
I am running the test programmatically which means the timing will be different
from when testing manually via ij.
Here is what I found by instrumenting the test some more:
A)
If I add a sleep between the startMaster and the stopMaster the failover will
not hang:
.
.
startSlave
startMaster
sleep(10000L)
stopMaster
failOver
Gets SQLSTATE: XRE07, SQLERRMC: Could not perform operation because the
database is not in replication master mode.
connect slave:
[localhost:4527//export/home/tmp/os136789/testingInMyDerbySandbox/db_slave/wombat]
CONNECTED
B)
Without this sleep the hang occurs:
.
.
startSlave
startMaster
stopMaster
connect slave: SQLSTATE: 08004, SQLERRMC: Connection refused to database
'/export/home/tmp/os136789/testingInMyDerbySandbox/db_slave/wombat' because it
is in replication slave mode.'
sleep(10000L) // No effect.
connect slave: SQLSTATE: 08004, SQLERRMC: Connection refused to database
'/export/home/tmp/os136789/testingInMyDerbySandbox/db_slave/wombat' because it
is in replication slave mode.'
failOver
HANGS!
In case A): should not the failover ('connect failover=true') return a valid
connection according to the spec.?
> 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.
