On Mon, Nov 22, 2021 at 08:17:34PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 22.11.2021 19:30, Eric Blake wrote:
> > Reviving this thread, as a good as place as any for my question:
> >
> > But I can't
> > find anywhere in the code base that ensures that on a reconnect, the
> > new server
22.11.2021 19:30, Eric Blake wrote:
Reviving this thread, as a good as place as any for my question:
On Thu, Jun 10, 2021 at 01:07:50PM +0300, Vladimir Sementsov-Ogievskiy wrote:
Add an option for a thread to retry connection until succeeds. We'll
use nbd/client-connection both for reconnect
Reviving this thread, as a good as place as any for my question:
On Thu, Jun 10, 2021 at 01:07:50PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Add an option for a thread to retry connection until succeeds. We'll
> use nbd/client-connection both for reconnect and for initial connection
> in
On Thu, Jun 10, 2021 at 01:07:50PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Add an option for a thread to retry connection until succeeds. We'll
for a thread to retry connecting until it succeeds.
> use nbd/client-connection both for reconnect and for initial connection
> in nbd_open(), so
Add an option for a thread to retry connection until succeeds. We'll
use nbd/client-connection both for reconnect and for initial connection
in nbd_open(), so we need a possibility to use same NBDClientConnection
instance to connect once in nbd_open() and then use retry semantics for
reconnect.
