From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/3] ocfs2/cluster: Increase the live threshold
Date: Thu, 21 Apr 2011 16:39:48 -0700 [thread overview]
Message-ID: <20110421233947.GA20184@noexit> (raw)
In-Reply-To: <4DB0AC1A.5020303@oracle.com>
On Thu, Apr 21, 2011 at 03:13:46PM -0700, Sunil Mushran wrote:
> We have seen isolated cases (very few, I might add) of o2hb not
> detecting all live nodes on startup. One plausible reasoning for it
> is that other node had a hb io delay at the same time. The live
> threshold currently is 2. That's as low as it can be. As we set it to
> that because we start the heartbeat on mount.
>
> With global heartbeat we can afford to increase that timeout. The
> patch increases it for only global heartbeat and that too only for
> the first heartbeat region.
>
> Makes sense?
I think Mark wants this in the patch description. We won't find
this email a year from now ;-)
Joel
--
Bram's Law:
The easier a piece of software is to write, the worse it's
implemented in practice.
http://www.jlbec.org/
jlbec at evilplan.org
next prev parent reply other threads:[~2011-04-21 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 22:21 [Ocfs2-devel] Few bug fixes Sunil Mushran
2011-04-05 22:21 ` [Ocfs2-devel] [PATCH 1/3] ocfs2/dlm: Use negotiated o2dlm protocol version Sunil Mushran
2011-04-19 17:44 ` Mark Fasheh
2011-04-05 22:21 ` [Ocfs2-devel] [PATCH 2/3] ocfs2/cluster: Increase the live threshold Sunil Mushran
2011-04-21 21:49 ` Mark Fasheh
2011-04-21 22:13 ` Sunil Mushran
2011-04-21 23:39 ` Joel Becker [this message]
2011-04-21 23:49 ` Mark Fasheh
2011-04-05 22:21 ` [Ocfs2-devel] [PATCH 3/3] ocfs2/cluster: Heartbeat mismatch message improved Sunil Mushran
2011-04-21 21:50 ` Mark Fasheh
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=20110421233947.GA20184@noexit \
--to=jlbec@evilplan.org \
--cc=ocfs2-devel@oss.oracle.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.