Re: [Nbd] how does NBD handle disconnections?
- To: email@example.com
- Subject: Re: [Nbd] how does NBD handle disconnections?
- From: Francis Giraldeau <francis.giraldeau@...132...>
- Date: Tue, 31 Jul 2007 12:17:24 -0400
- Message-id: <46AF6094.2070800@...132...>
- In-reply-to: <20070731081854.GE5573@...39...>
- References: <46AE9E6A.3010703@...132...> <20070731081854.GE5573@...39...>
Wouter Verhelst a écrit :
> On Mon, Jul 30, 2007 at 10:28:58PM -0400, Francis Giraldeau wrote:
>> I would like to use the -persist option of NBD. I thought that using
>> this option would make nbd-client reconnect if the corresponding
>> nbd-server is killed, but it didn't.
> Never the less, that is the behaviour that nbd-client tries to achieve.
> How is it failing? Could you provide a bit more detail?
As you may know, LTSP is using NBD to replace NFS root. I'm concerned
about high availability. It was easy to setup high available NFS server
with heartbeat. The problem with NBD is that one process is started for
each connexion on one server. If a failover occur, the client must start
a new process on the other server. The client should tolerate a
disconnection and create a new one until it succeed.
Another example, if the LTSP server reboots, then you need to reboot all
the thin-clients, that may even not respond anymore. The nbd-client
should handle this.
Since the NBD device is read only, so it should be easy to do it.
I saw also that nbd-server process are sometime left behind and never
terminate. Should look to that also.
The nbd-monitor could be a solution. Does work is done to it?
Thanks a lot for all your time. NBD is realy cool, and I would like to
make it cooler.
Have a nice day,