[jira] Commented: (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:comment-tabpanel&focusedCommentId=12589529#action_12589529 ] V.Narayanan commented on DERBY-3617: Thanks a ton for the clarification Ole. Thank you for the test runs also. > 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12589511#action_12589511 ] Ole Solberg commented on DERBY-3617: Sorry Narayanan for missing your comment (16/Apr/08 04:03 AM). I can upload a preliminary patch for the replication tests soon, which contains this test. > 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.
[jira] Commented: (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: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(1L)
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(1L) // 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12589499#action_12589499 ] V.Narayanan commented on DERBY-3617: Hi Ole, would it be possible for you to pls attach the reproducible using which the test was run? Following the steps mentioned does not reproduce this bug. > 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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12589437#action_12589437 ] V.Narayanan commented on DERBY-3617: I tried a simple run without authentication enabled and and without executing any transactions it seemed to work. I will try this again with authentication enabled and after executing some transactions. On the master -- [EMAIL PROTECTED]:~/work/workspaces/Dery3617/master$ java org.apache.derby.tools.ij ij version 10.5 ij> connect 'jdbc:derby://localhost:1527/replicationdb'; ij> connect 'jdbc:derby://localhost:1527/replicationdb;startMaster=true;slaveHost=localhost;slavePort=8001'; ij(CONNECTION1)> connect 'jdbc:derby://localhost:1527/replicationdb;stopMaster=true;slaveHost=localhost;slavePort=8001'; ij(CONNECTION2)> On the slave --- [EMAIL PROTECTED]:~/work/workspaces/Dery3617/slave$ java org.apache.derby.tools.ij ij version 10.5 ij> connect 'jdbc:derby://localhost:1528/replicationdb;startSlave=true;slaveHost=localhost;slavePort=8001'; ERROR XRE08: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE08, SQLERRMC: Replication slave mode started successfully for database 'replicationdb'. Connection refused because the database is in replication slave mode. ij> connect 'jdbc:derby://localhost:1528/replicationdb;failover=true'; ERROR XRE11: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE11, SQLERRMC: failoverreplicationdbXRE11 ij> > 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.
