From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Global heartbeat - drop#1
Date: Wed, 28 Jul 2010 09:40:28 -0700 [thread overview]
Message-ID: <4C505D7C.9020209@oracle.com> (raw)
In-Reply-To: <20100728144533.GA3128@laptop.jp.oracle.com>
If the io stack on a non-hb device fails, the apps will start getting
EIOs. Possibly leading to application death. But the system will stay
up.
The dlm domain should remain available.
One case I can see happening is if the journal op fail (say commit
triggered by downconvert). In that case, the fs will fence the box.
Do you have a specific example?
On 07/28/2010 07:45 AM, Wengang Wang wrote:
> Hi Sunil,
>
> The global heartbeat also introduce a difference comparing with local heart.
> With the ghb, what if the non-heartbeat ocfs2 volume(s) fail(s)? Say some lower
> layer(raid/disk-driver) become unhappy to work anymore. In case, no failover
> since no self-fence I think. So it could cause the domain in question
> unavailable(finally), isn't it? With the original lhb scheme, no such problem.
> Is there a solution?
>
> regards,
> wengang.
>
> On 10-07-23 16:55, Sunil Mushran wrote:
>
>> This is the first drop of the global heartbeat patches for ocfs2/kernel.
>>
>> The first few patches add support for heartbeat mode in sysfs, the new
>> incompat clusterinfo flag and the new mount option heartbeat=global.
>>
>> 0001-ocfs2-cluster-Add-heartbeat-mode-configfs-parameter.patch
>> 0002-ocfs2-Add-an-incompat-feature-flag-OCFS2_FEATURE_INC.patch
>> 0003-ocfs2-Add-support-for-heartbeat-global-mount-option.patch
>> 0004-ocfs2-dlm-Expose-dlm_protocol-in-dlm_state.patch
>>
>> The next few patches enhance the join domain protocol to get the list
>> of configured nodes and heartbeating regions to ensure that all nodes
>> in the cluster have the same view of the cluster.
>>
>> 0005-ocfs2-cluster-Get-all-heartbeat-regions.patch
>> 0006-ocfs2-dlm-Add-message-DLM_QUERY_HBREGION.patch
>> 0007-ocfs2-Print-message-if-user-mounts-without-starting-.patch
>> 0008-ocfs2-dlm-Add-message-DLM_QUERY_NODEINFO.patch
>>
>> The one known missing bit concerns quorum calculation. I am still
>> working on it.
>>
>> http://oss.oracle.com/osswiki/OCFS2/DesignDocs/NewGlobalHeartbeat
>>
>> Thanks
>> Sunil
>>
>> _______________________________________________
>> Ocfs2-devel mailing list
>> Ocfs2-devel at oss.oracle.com
>> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>>
next prev parent reply other threads:[~2010-07-28 16:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 23:55 [Ocfs2-devel] Global heartbeat - drop#1 Sunil Mushran
2010-07-23 23:55 ` [Ocfs2-devel] [PATCH 1/8] ocfs2/cluster: Add heartbeat mode configfs parameter Sunil Mushran
2010-07-23 23:55 ` [Ocfs2-devel] [PATCH 2/8] ocfs2: Add an incompat feature flag OCFS2_FEATURE_INCOMPAT_CLUSTERINFO Sunil Mushran
2010-07-23 23:55 ` [Ocfs2-devel] [PATCH 3/8] ocfs2: Add support for heartbeat=global mount option Sunil Mushran
2010-07-23 23:55 ` [Ocfs2-devel] [PATCH 4/8] ocfs2/dlm: Expose dlm_protocol in dlm_state Sunil Mushran
2010-07-23 23:55 ` [Ocfs2-devel] [PATCH 5/8] ocfs2/cluster: Get all heartbeat regions Sunil Mushran
2010-07-23 23:55 ` [Ocfs2-devel] [PATCH 6/8] ocfs2/dlm: Add message DLM_QUERY_HBREGION Sunil Mushran
2010-07-28 16:21 ` Wengang Wang
2010-07-28 16:47 ` Sunil Mushran
2010-07-29 5:03 ` Wengang Wang
2010-07-29 17:22 ` Sunil Mushran
2010-07-30 1:55 ` Wengang Wang
2010-07-29 5:08 ` Wengang Wang
2010-07-29 17:24 ` Sunil Mushran
2010-07-23 23:55 ` [Ocfs2-devel] [PATCH 7/8] ocfs2: Print message if user mounts without starting global heartbeat Sunil Mushran
2010-07-23 23:55 ` [Ocfs2-devel] [PATCH 8/8] ocfs2/dlm: Add message DLM_QUERY_NODEINFO Sunil Mushran
2010-07-29 6:49 ` Wengang Wang
2010-07-29 18:59 ` Sunil Mushran
2010-07-28 14:45 ` [Ocfs2-devel] Global heartbeat - drop#1 Wengang Wang
2010-07-28 16:40 ` Sunil Mushran [this message]
2010-07-29 3:08 ` Wengang Wang
2010-07-29 17:28 ` Sunil Mushran
2010-07-30 1:58 ` Wengang Wang
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=4C505D7C.9020209@oracle.com \
--to=sunil.mushran@oracle.com \
--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.