[
https://issues.apache.org/jira/browse/DERBY-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-3527:
---------------------------------
Attachment: derby-3527-1d.diff
What could happen with patch 1c is that the thread calling isConnected... would
have to wait for 5 seconds before returning a connection confirmed message
instead of returning this immediately. But I agree - this possibility should be
removed. Patch 1d addresses this. Replication test suite passed (no
non-replication code affected). Requesting review.
> The slave will not notice that a network cable is unplugged and will
> therefore reject failover/stopSlave commands
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3527
> URL: https://issues.apache.org/jira/browse/DERBY-3527
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: Jørgen Løland
> Assignee: Jørgen Løland
> Attachments: derby-3527-1a.diff, derby-3527-1a.stat,
> derby-3527-1b.diff, derby-3527-1b.stat, derby-3527-1c.diff,
> derby-3527-1c.stat, derby-3527-1d.diff
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
