[DERBY-3527] The slave will not notice that a network cable is unplugged and will therefore reject failover/stopSlave commands

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.1.3, 10.5.1.1
• Fix Version/s: 10.4.1.3, 10.5.1.1
• Component/s: Replication
• Assignee: Jorgen Loland
• Reporter: Jorgen Loland
• Created: 12/Mar/08 14:47
• Updated: 02/Jun/10 11:13
• Resolved: 02/Apr/08 11:48

Description

If a network cable between the master and slave is unplugged (or a switch crashes etc), ObjectInputStream#readObject will not get an exception. Neither the socket nor the input stream can be queried for information on whether or not the connection is working. AFAIK, the only way to find out if the network is down is to send a message.

The slave commands stopSlave and failover are rejected if the network connection is working. To be absolutely sure that the connection is working, we need to ping the master when these commands are requested.

Issue Links

• is related to: DERBY-3639 Slave on Windows stops replication when network connection is broken, failover fails