cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] waiting in init.d/cman
Date: Thu, 6 Aug 2009 11:05:15 -0500	[thread overview]
Message-ID: <20090806160515.GD15669@redhat.com> (raw)
In-Reply-To: <1249500724.23450.124.camel@cerberus.int.fabbione.net>

On Wed, Aug 05, 2009 at 09:32:04PM +0200, Fabio M. Di Nitto wrote:
> On Wed, 2009-08-05 at 13:20 -0500, David Teigland wrote:
> > On Wed, Aug 05, 2009 at 07:25:53PM +0200, Fabio M. Di Nitto wrote:
> > > I can see the possibility to block the boot for quorum when quorum might
> > > never be available. As above, I don't mind to add that to the init
> > > script, but it will need yet another timeout.
> > 
> > Sure, but as I mentioned, if cman doesn't wait for quorum, then clvmd,
> > rgmanager or gfs mount will... and those don't time out and sometimes
> > can't be cancelled, whereas cman_tool wait -q can be.
> 
> During the boot process you can't issue ctrl+c no matter what. IIRC somebody
> suggested to use boot options. Perhaps forcing a wait for quorum in our init
> script is sensible if we allow a boot option to not run cman at all. The
> other daemons will fail if cman is not there and boot would be "unblocked".

During 'service cman start' you could cancel via ctrl+c if it's blocked on
quorum, but during 'service gfs start' you may not be able to cancel if it's
blocked on quorum.

During boot init.d/cman you can cancel via timeout if it's blocked on quorum,
but during boot init.d/gfs you may not be able to cancel via timeout if it's
blocked on quorum.

So, I think we end up with the best option being our current approach: do all
waiting with timeouts in cman.  This gives us the best options for boot start
and manual start.

Dave



      parent reply	other threads:[~2009-08-06 16:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 16:12 [Cluster-devel] waiting in init.d/cman David Teigland
2009-08-05 17:25 ` Fabio M. Di Nitto
2009-08-05 18:20   ` David Teigland
2009-08-05 19:32     ` Fabio M. Di Nitto
2009-08-05 19:43       ` Bob Peterson
2009-08-06 16:05       ` David Teigland [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=20090806160515.GD15669@redhat.com \
    --to=teigland@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).