db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-3527) The slave will not notice that a network cable is unplugged and will therefore reject failover/stopSlave commands
Date Fri, 28 Mar 2008 07:38:24 GMT

     [ 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-1c.stat
                derby-3527-1c.diff

Thank you for reviewing. Patch 1c addresses your comments.

Most important differences:

* Instead of returning null, sendMessageWaitForReply now raises an exception if it does not
receive a reply message
* readMessage is recursive, and therefore handles any number of subsequent pong messages (i.e.,
not changed)
* ReplicationMessageReceive - I now use one monitor to send ping and one to wait for pong.
* With the newly introduced monitor, connectionConfirmed is not protected by receivePongSemaphore
in all cases. Leaving it volatile

All tests passed. 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
>
>
> 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.


Mime
View raw message