Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1323733545.1206962546103.JavaMail.jira@brutus>
Date: Mon, 31 Mar 2008 04:22:26 -0700 (PDT)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.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
In-Reply-To: <1949557987.1205333326482.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-3527?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

J=C3=B8rgen L=C3=B8land updated DERBY-3527:
---------------------------------

    Attachment: derby-3527-1d.diff

What could happen with patch 1c is that the thread calling isConnected... w=
ould have to wait for 5 seconds before returning a connection confirmed mes=
sage 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 ther=
efore 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=C3=B8rgen L=C3=B8land
>            Assignee: J=C3=B8rgen L=C3=B8land
>         Attachments: derby-3527-1a.diff, derby-3527-1a.stat, derby-3527-1=
b.diff, derby-3527-1b.stat, derby-3527-1c.diff, derby-3527-1c.stat, derby-3=
527-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. Neit=
her the socket nor the input stream can be queried for information on wheth=
er 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 con=
nection is working. To be absolutely sure that the connection is working, w=
e need to ping the master when these commands are requested.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.