rpc:call has a delay in response when calling a nodedown

Magda Mansour <>
Mon Aug 30 09:50:55 CEST 2010


We are encountering the following problem :

The command below responds after a few seconds (~7 seconds)
     rpc:call(, erlang, whereis, [dummy_process]).
where dummy_host is defined in /etc/hosts but is unreachable

Adding a timeout in the fourth argument does not fasten the response of this command :
     rpc:call(, erlang, whereis, [dummy_process], 1000).

We are using OTP-R11B-5 on Red Hat Enterprise Linux ES release 4 (Nahant
Update 8) or Ubuntu

As a work around, we were obliged to check if  is
part of [node()|nodes()] before calling rpc:call.

Is this delay considered as the normal behaviour of rpc:call ? Is there
another work around or an alternative function to use ?

This example seems to be dummy, but on a live production cluster, where
one node has a problem, this delay can lead to real problems.

Thank you in advance,
Magda Mansour

This message, including attachments, is intended solely for the addressee indicated in this message and is strictly confidential or otherwise privileged. If you are not the intended recipient (or responsible for delivery of the message to such person) : - (1) please immediately (i) notify the sender by reply email and (ii) delete this message and attachments, - (2) any use, copy or dissemination of this transmission is strictly prohibited. If you or your employer does not consent to Internet email messages of this kind, please advise Myriad Group AG by reply e-mail immediately. Opinions, conclusions and other information expressed in this message are not given or endorsed by Myriad Group AG unless otherwise indicated by an authorized representative independent of this message.

More information about the erlang-questions mailing list