dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Benjamin Marzinski <bmarzins@redhat.com>
To: christophe.varoqui@opensvc.com
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: multipath-tools/path_priority pp_alua/rtpg.c p ...
Date: Mon, 7 Nov 2011 08:06:36 -0600	[thread overview]
Message-ID: <20111107140636.GU24133@ether.msp.redhat.com> (raw)
In-Reply-To: <1320357858.16195.30.camel@lapoo.opensvc.com>

On Thu, Nov 03, 2011 at 11:04:18PM +0100, Christophe Varoqui wrote:
> On jeu., 2011-11-03 at 16:58 -0500, Benjamin Marzinski wrote:
> > On Wed, Nov 02, 2011 at 10:51:50PM +0100, Christophe Varoqui wrote:
> > > > --- multipath-tools/path_priority/pp_alua/rtpg.c	2009/08/18 21:12:02	1.3.2.5
> > > > +++ multipath-tools/path_priority/pp_alua/rtpg.c	2011/10/24 13:41:32	1.3.2.6
> > > > @@ -29,7 +29,7 @@
> > > >  #include "rtpg.h"
> > > >  
> > > >  #define SENSE_BUFF_LEN  32
> > > > -#define DEF_TIMEOUT     300000
> > > > +#define DEF_TIMEOUT     60000
> > > >  
> > > 
> > > Do you want that part merged into upstream's alua prioritizer shared
> > > object ?
> > 
> > In the RHEL5 code, this is a seperate callout program.  Upstream it
> > would be better if we could make this configurable via multipath.conf,
> > like the checker timeouts.
> > 
> Sure, but you did not implement that in the callout either. Is the 60s
> timeout value controversial ? Is that change a worthy quick-fix ?

Sure.  We've had a number of complaints about how long multipath can get
stuck in some corner cases.  This was one that caused some problems, so
I'd be happy to see the default changed.

-Ben

> 
> Regards,
> -- 
> Christophe Varoqui
> OpenSVC - Tools to scale
> http://www.opensvc.com/

      reply	other threads:[~2011-11-07 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 13:41 multipath-tools/path_priority pp_alua/rtpg.c p bmarzins
2011-11-02 21:51 ` Christophe Varoqui
2011-11-03 21:58   ` Benjamin Marzinski
2011-11-03 22:04     ` Christophe Varoqui
2011-11-07 14:06       ` Benjamin Marzinski [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=20111107140636.GU24133@ether.msp.redhat.com \
    --to=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.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;
as well as URLs for NNTP newsgroup(s).