[
https://issues.apache.org/jira/browse/DERBY-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Solberg updated DERBY-3617:
-------------------------------
Attachment: 3617_NotForCommit.stat.txt
3617_NotForCommit.diff.txt
Hi Narayanan!
I am uploading a patch (3617_NotForCommit) for the replication tests which
includes tests for the following 4 cases:
A) (as above)
.
.
startSlave
startMaster
# No bigInsert
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) (as above)
.
.
startSlave
startMaster
# No bigInsert
# No sleep(10000L)
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.'
failOver
HANGS!
C) (B + "insert...")
.
.
startSlave
startMaster
bigInsert
# No: sleep(10000L)
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.'
failOver
OK! Failover returns a Connection.
connect slave:
[localhost:4527//export/home/tmp/os136789/testingInMyDerbySandbox/db_slave/wombat]
CONNECTED
D) (A + "insert...")
.
.
startSlave
startMaster
bigInsert
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
These test cases are located in ReplicationRun_Local_3_p2 as
Id) insert,immediate - method() [failover response, connect response] ...
A) false, false -
testReplication_Local_3_p2_StateTests_smallInsert_sleepBeforeStopMaster()
[XRE07, CONNECTED]
B) false, true -
testReplication_Local_3_p2_StateTests_smallInsert_immediateStopMaster()
[HANGS!, -] (DISABLED)
C) true, true -
testReplication_Local_3_p2_StateTests_bigInsert_immediateStopMaster()
[CONNECTED, CONNECTED]
D) true, false -
testReplication_Local_3_p2_StateTests_bigInsert_sleepBeforeStopMaster()
[XRE07, CONNECTED]
> 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: 3617_NotForCommit.diff.txt, 3617_NotForCommit.stat.txt,
> 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.
