From: Gris Ge <fge@redhat.com>
To: Martin Wilck <mwilck@suse.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 2/3] multipath-tools: libdmmp: Improve timeout mechanism
Date: Mon, 28 Aug 2017 20:58:48 +0800 [thread overview]
Message-ID: <20170828125848.GA15058@redhat.com> (raw)
In-Reply-To: <1503005396.7232.11.camel@suse.com>
[-- Attachment #1.1: Type: text/plain, Size: 623 bytes --]
On Thu, Aug 17, 2017 at 11:29:56PM +0200, Martin Wilck wrote:
> On Wed, 2017-08-16 at 20:34 +0800, Gris Ge wrote:
> > Issue:
> > libdmmp return error of timeout before user requested timeout was
> > met.
>
> Maybe I'm missing something here, but if you just retry the timed-out
> command, isn't it likely that you'll hit the uxsock_timeout again and
> again?
>
> Best,
> Martin
Hi Martin,
You will get timeout again after `uxsock_timeout` seconds if the
daemon/multipathd haven't finish its work on dm tables and invoking path
checker. But eventually, you will the requested data.
--
Gris Ge
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2017-08-28 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 12:34 [PATCH 1/3] multipath-tools: Remove the limitation of IPC command reply length Gris Ge
2017-08-16 12:34 ` [PATCH 2/3] multipath-tools: libdmmp: Improve timeout mechanism Gris Ge
2017-08-16 12:34 ` [PATCH 3/3] multipath-tools: libdmmp: New function to flush and reconfig Gris Ge
2017-08-17 21:29 ` [PATCH 2/3] multipath-tools: libdmmp: Improve timeout mechanism Martin Wilck
2017-08-28 12:58 ` Gris Ge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170828125848.GA15058@redhat.com \
--to=fge@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mwilck@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox