From: jbrassow@sourceware.org <jbrassow@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cmirror/src functions.c
Date: 13 Feb 2008 15:06:18 -0000 [thread overview]
Message-ID: <20080213150618.25178.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: jbrassow at sourceware.org 2008-02-13 15:06:17
Modified files:
cmirror/src : functions.c
Log message:
- change the way 'is_remote_recovering' works to improve overall
performance.
Before a mirror issues a write, it must call 'is_remote_recovering'
to ensure that another machine will not be recovering the region during
the write. This function can dramatically slow things down. One way to
increase performance is to note when the mirror is in-sync - then
is_remote_recovering can return 0 without having to send the request
around the cluster. (This has already been done.) This greatly speeds up
I/O during nominal mirror operation. However, I/O during mirror resyncing
is still greatly reduced. The problem is that the cluster network is
consumed with handling 'is_remote_recovering' calls that it becomes hard
to actually do the recovery. The fix is to only allow one
is_remote_recovering call to go to the cluster every 1/4 sec. When the
call goes up to userspace, it also retrieves info about how far along
the resync is. If a request is determined to already be in sync by that
info, then the region is not recovering and can safely be answered without
having to send the request on to the cluster. This approach has greatly
improved both the recovery and nominal throughput.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror/src/functions.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.1.2.14&r2=1.1.2.15
--- cluster/cmirror/src/Attic/functions.c 2008/02/08 14:30:10 1.1.2.14
+++ cluster/cmirror/src/Attic/functions.c 2008/02/13 15:06:17 1.1.2.15
@@ -1359,8 +1359,8 @@
*/
static int clog_is_remote_recovering(struct clog_tfr *tfr)
{
- int *rtn = (int *)tfr->data;
uint64_t region = *((uint64_t *)(tfr->data));
+ struct { int is_recovering; uint64_t sync_search; } *pkg = (void *)tfr->data;
struct log_c *lc = get_log(tfr->uuid);
if (!lc)
@@ -1372,18 +1372,21 @@
if (lc->recovery_halted) {
LOG_DBG("[%s] Recovery halted... [not remote recovering]: %llu",
SHORT_UUID(lc->uuid), (unsigned long long)region);
- *rtn = 0;
+ pkg->is_recovering = 0;
+ pkg->sync_search = lc->region_count; /* none are recovering */
} else {
- *rtn = !log_test_bit(lc->sync_bits, region);
+ pkg->is_recovering = !log_test_bit(lc->sync_bits, region);
+ pkg->sync_search = lc->sync_search;
LOG_DBG("[%s] Region is %s: %llu",
SHORT_UUID(lc->uuid),
(region == lc->recovering_region) ?
"currently remote recovering" :
- (*rtn) ? "pending remote recovery" :
+ (pkg->is_recovering) ? "pending remote recovery" :
"not remote recovering", (unsigned long long)region);
}
- if (*rtn && (region != lc->recovering_region)) {
+ if (pkg->is_recovering &&
+ (region != lc->recovering_region)) {
struct recovery_request *rr;
/* Already in the list? */
@@ -1404,7 +1407,8 @@
}
out:
- tfr->data_size = sizeof(*rtn);
+
+ tfr->data_size = sizeof(*pkg);
return 0;
}
next reply other threads:[~2008-02-13 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 15:06 jbrassow [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-06 22:12 [Cluster-devel] cluster/cmirror/src functions.c jbrassow
2007-11-28 20:34 jbrassow
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=20080213150618.25178.qmail@sourceware.org \
--to=jbrassow@sourceware.org \
/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).