On Mon, Sep 17, 2007 at 03:49:37PM +0100, Richard W.M. Jones wrote:
Daniel Veillard wrote:
> Is there a configuration knob in the RPC layer to lower the
>timeout delay ? Some calls are slow, but we should not reach a 2mn
>timeout, that's very very long I think.
Migrations might take some time.
In any case the RPC code just does 'sendto' followed by 'recvfrom'.
There is no timeout to adjust on the client side.
Shuveb's problem is that TCP doesn't gracefully handle the case where
the ethernet cable is pulled out. There may be a socket option which
helps for this.
That depends on your definition of graceful.
Shuveb's definition is that he wants the connection to fail & give an error
back to the app.
My definition is that TCP should keep retrying until I plug the cable back
in, so I don't get unneccessary failures if i'm just switching cables
around. Likewise if there's temporary outages anywhere else in the link
between the client & server.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules:
http://search.cpan.org/~danberr/ -=|
|=- Projects:
http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|