[DERBY-3632] Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.4.2.0, 10.5.1.1
• Fix Version/s: 10.4.2.1, 10.6.1.0
• Component/s: Replication, Test
• Environment: All
• Assignee: Ole Solberg
• Reporter: Ole Solberg
• Created: 18/Apr/08 10:26
• Updated: 23/Jan/15 01:34
• Resolved: 23/Jan/15 01:34

Description

When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.

This causes intermittent errors in replication tests.

Issue Links

• is related to: DERBY-3709 Exception printed by replication test: Could not perform operation because the database is not in replication master mode.
• is related to: DERBY-3719 '...replication.buffer.LogBufferFullException' causes failover to fail w/ 'XRE07, SQLERRMC: Could not perform operation because the database is not in replication master mode.'
• is related to: DERBY-4186 After master stop, test fails when it succeeds in connecting (rebooting) shut-down ex-slave
• is related to: DERBY-4175 Instability in some replication tests under load, since tests don't wait long enough for final state or anticipate intermediate states
• is related to: DERBY-4231 testReplication_Local_StateTest_part1: Unexpected SQL state. expected:<XRE[20]> but was:<XRE[07]>
• is related to: DERBY-4277 ReplicationRun_Local and ReplicationRun_Local_StateTest_part1 failed after testing fix of 4268
• is related to: DERBY-4185 Make timeout settable or increase default for one replication message layer protocol.