From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Designing a new prio_callout
Date: Fri, 10 Aug 2007 17:07:00 +0200 [thread overview]
Message-ID: <46BC7F14.80302@suse.de> (raw)
In-Reply-To: <d61540a40708091055u725fa5e4wa182ac1d778323be@mail.gmail.com>
Ethan John wrote:
> Is it possible to manually set the priority of a path after a connection has
> been established?
>
> Since we're doing failover-only (only 1 active path at a time), it would be
> nice to tell users that they can manually reset priority after a failure.
> For example, in a configuration with two paths, where one is active and the
> other is passive for two differeent volumes, a failure of one path will
> result in all traffic going through the one remaining path. After the second
> path comes back up, all traffic will still be written to the first path
> (paths are not rebalanced after a failure).
>
Not necessarily. There is the keyword 'failback', which can be set to
IMMEDIATE, causing all paths to fail back to the original path once it
comes back.
And as you don't actually need to send any commands for facilitate
the failover I doubt you'd need to develop your own hardware handler.
The existing tweaks should be enough, I think.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2007-08-10 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 21:42 Designing a new prio_callout Ethan John
2007-07-25 11:37 ` Hannes Reinecke
2007-07-29 16:03 ` Ethan John
2007-07-30 6:31 ` Hannes Reinecke
2007-08-09 17:55 ` Ethan John
2007-08-10 15:07 ` Hannes Reinecke [this message]
2007-08-10 15:40 ` Ethan John
2007-08-14 17:05 ` Ethan John
2007-08-15 8:45 ` Stefan Bader
2007-08-15 15:57 ` Ethan John
2007-08-16 10:58 ` Stefan Bader
2007-08-16 17:30 ` Ethan John
2007-08-27 15:09 ` Hannes Reinecke
2007-08-27 15:50 ` Ethan John
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=46BC7F14.80302@suse.de \
--to=hare@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.