Derby
  1. Derby
  2. DERBY-3617

failover on slave hangs after stopmaster on master.

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.5.1.1
    • Fix Version/s: None
    • Component/s: Replication
    • Environment:
    • Urgency:
      Normal
    • Issue & fix info:
      Repro attached

      Description

      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.

      1. 3617_NotForCommit.stat.txt
        1 kB
        Ole Solberg
      2. 3617_NotForCommit.diff.txt
        73 kB
        Ole Solberg
      3. db_slave-derby.log
        18 kB
        Ole Solberg
      4. db_master-derby.log
        41 kB
        Ole Solberg
      5. log.out
        44 kB
        Ole Solberg

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Ole Solberg
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development