public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
* cluster/cmirror/src functions.c
@ 2007-11-28 20:34 jbrassow
0 siblings, 0 replies; 3+ messages in thread
From: jbrassow @ 2007-11-28 20:34 UTC (permalink / raw)
To: cluster-cvs
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: jbrassow@sourceware.org 2007-11-28 20:34:22
Modified files:
cmirror/src : functions.c
Log message:
- Bug 387601
- If the sync bit is already set, do not increment the sync_count. This
can lead to a sync_count > the number of regions.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror/src/functions.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.1.2.4&r2=1.1.2.5
^ permalink raw reply [flat|nested] 3+ messages in thread
* cluster/cmirror/src functions.c
@ 2008-02-13 15:06 jbrassow
0 siblings, 0 replies; 3+ messages in thread
From: jbrassow @ 2008-02-13 15:06 UTC (permalink / raw)
To: cluster-cvs
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: jbrassow@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
^ permalink raw reply [flat|nested] 3+ messages in thread
* cluster/cmirror/src functions.c
@ 2007-12-06 22:12 jbrassow
0 siblings, 0 replies; 3+ messages in thread
From: jbrassow @ 2007-12-06 22:12 UTC (permalink / raw)
To: cluster-cvs
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: jbrassow@sourceware.org 2007-12-06 22:12:21
Modified files:
cmirror/src : functions.c
Log message:
- Bug 384901: RHEL5 cmirror tracker: unable to create a --nosync mirror
- fix argument counting.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror/src/functions.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.1.2.5&r2=1.1.2.6
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-02-13 15:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-11-28 20:34 cluster/cmirror/src functions.c jbrassow
2007-12-06 22:12 jbrassow
2008-02-13 15:06 jbrassow
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 read-only IMAP folder(s) and NNTP newsgroup(s).