From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/6] ocfs2: o2hb: add negotiate timer
Date: Fri, 22 Jan 2016 11:23:33 +0800 [thread overview]
Message-ID: <56A1A0B5.10200@oracle.com> (raw)
In-Reply-To: <20160121154239.ef8a8581d5acea63bae22436@linux-foundation.org>
Hi Andrew,
On 01/22/2016 07:42 AM, Andrew Morton wrote:
> On Wed, 20 Jan 2016 11:13:34 +0800 Junxiao Bi <junxiao.bi@oracle.com> wrote:
>
>> When storage down, all nodes will fence self due to write timeout.
>> The negotiate timer is designed to avoid this, with it node will
>> wait until storage up again.
>>
>> Negotiate timer working in the following way:
>>
>> 1. The timer expires before write timeout timer, its timeout is half
>> of write timeout now. It is re-queued along with write timeout timer.
>> If expires, it will send NEGO_TIMEOUT message to master node(node with
>> lowest node number). This message does nothing but marks a bit in a
>> bitmap recording which nodes are negotiating timeout on master node.
>>
>> 2. If storage down, nodes will send this message to master node, then
>> when master node finds its bitmap including all online nodes, it sends
>> NEGO_APPROVL message to all nodes one by one, this message will re-queue
>> write timeout timer and negotiate timer.
>> For any node doesn't receive this message or meets some issue when
>> handling this message, it will be fenced.
>> If storage up at any time, o2hb_thread will run and re-queue all the
>> timer, nothing will be affected by these two steps.
>>
>> ...
>>
>> +static void o2hb_nego_timeout(struct work_struct *work)
>> +{
>> + struct o2hb_region *reg =
>> + container_of(work, struct o2hb_region,
>> + hr_nego_timeout_work.work);
>
> It's better to just do
>
> struct o2hb_region *reg;
>
> reg = container_of(work, struct o2hb_region, hr_nego_timeout_work.work);
>
> and avoid the weird 80-column tricks.
OK. Will update this in V2.
>
>> + unsigned long live_node_bitmap[BITS_TO_LONGS(O2NM_MAX_NODES)];
>
> the bitmap.h interfaces might be nicer here. Perhaps. A little bit.
Will consider this in v2.
>
>> + int master_node;
>> +
>> + o2hb_fill_node_map(live_node_bitmap, sizeof(live_node_bitmap));
>> + /* lowest node as master node to make negotiate decision. */
>> + master_node = find_next_bit(live_node_bitmap, O2NM_MAX_NODES, 0);
>> +
>> + if (master_node == o2nm_this_node()) {
>> + set_bit(master_node, reg->hr_nego_node_bitmap);
>> + if (memcmp(reg->hr_nego_node_bitmap, live_node_bitmap,
>> + sizeof(reg->hr_nego_node_bitmap))) {
>> + /* check negotiate bitmap every second to do timeout
>> + * approve decision.
>> + */
>> + schedule_delayed_work(®->hr_nego_timeout_work,
>> + msecs_to_jiffies(1000));
>
> One second is long enough to unmount the fs (and to run `rmmod
> ocfs2'!). Is there anything preventing the work from triggering in
> these situations?
Yes, this delayed work will by sync before the umount.
Thanks,
Junxiao.
>
>> +
>> + return;
>> + }
>> +
>> + /* approve negotiate timeout request. */
>> + } else {
>> + /* negotiate timeout with master node. */
>> + }
>> +
>> }
>
next prev parent reply other threads:[~2016-01-22 3:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 3:13 [Ocfs2-devel] ocfs2: o2hb: not fence self if storage down Junxiao Bi
2016-01-20 3:13 ` [Ocfs2-devel] [PATCH 1/6] ocfs2: o2hb: add negotiate timer Junxiao Bi
2016-01-21 23:42 ` Andrew Morton
2016-01-22 3:23 ` Junxiao Bi [this message]
2016-01-22 0:56 ` Joseph Qi
2016-01-22 3:19 ` Junxiao Bi
2016-01-20 3:13 ` [Ocfs2-devel] [PATCH 2/6] ocfs2: o2hb: add NEGO_TIMEOUT message Junxiao Bi
2016-01-21 23:47 ` Andrew Morton
2016-01-22 5:12 ` Junxiao Bi
2016-01-22 5:45 ` Andrew Morton
2016-01-22 5:46 ` Junxiao Bi
2016-01-25 3:18 ` Eric Ren
2016-01-25 4:28 ` Junxiao Bi
2016-01-25 5:59 ` Eric Ren
2016-01-20 3:13 ` [Ocfs2-devel] [PATCH 3/6] ocfs2: o2hb: add NEGOTIATE_APPROVE message Junxiao Bi
2016-01-20 3:13 ` [Ocfs2-devel] [PATCH 4/6] ocfs2: o2hb: add some user/debug log Junxiao Bi
2016-01-25 3:28 ` Eric Ren
2016-01-25 4:29 ` Junxiao Bi
2016-01-25 6:00 ` Eric Ren
2016-01-20 3:13 ` [Ocfs2-devel] [PATCH 5/6] ocfs2: o2hb: don't negotiate if last hb fail Junxiao Bi
2016-01-20 3:13 ` [Ocfs2-devel] [PATCH 6/6] ocfs2: o2hb: fix hb hung time Junxiao Bi
2016-01-20 6:00 ` [Ocfs2-devel] ocfs2: o2hb: not fence self if storage down Gang He
2016-01-20 8:09 ` Junxiao Bi
2016-01-20 9:18 ` Joseph Qi
2016-01-20 13:27 ` Junxiao Bi
2016-01-21 0:46 ` Joseph Qi
2016-01-21 1:48 ` Junxiao Bi
2016-01-22 4:25 ` Joseph Qi
2016-01-22 5:08 ` Junxiao Bi
2016-01-21 8:34 ` rwxybh
2016-01-21 8:41 ` Junxiao Bi
-- strict thread matches above, loose matches on Subject: below --
2016-05-23 21:50 [Ocfs2-devel] [patch 1/6] ocfs2: o2hb: add negotiate timer akpm at linux-foundation.org
2016-05-24 22:35 ` Mark Fasheh
2016-05-25 1:44 ` Junxiao Bi
2016-05-25 23:26 ` 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=56A1A0B5.10200@oracle.com \
--to=junxiao.bi@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 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).