public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: jbrassow@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW daemons/cmirrord/functions.c
Date: Mon, 30 Aug 2010 18:37:00 -0000	[thread overview]
Message-ID: <20100830183743.13927.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	jbrassow@sourceware.org	2010-08-30 18:37:42

Modified files:
	.              : WHATS_NEW 
	daemons/cmirrord: functions.c 

Log message:
	This patch fixes an issue where cluster mirror write I/O
	can be opprobriously slow if created with '--nosync'.
	
	One of the ways cluster mirrors coordinate I/O and recovery
	amoung the different machines is by the use of the log
	function 'is_remote_recovering()' which lets nodes know if
	a region they wish to perform a write on is currently being
	recovered on another node.  If the region is being recovered,
	the I/O is delayed.
	
	The 'is_remote_recovering' routine has been optimized to
	avoid the deluge of requests that would be issued to the
	userspace log server by maintaining a marker of how far
	the recovery has gotten.  It can then immediately return
	'not recovering' if the region being inquired about is
	less than this mark.  Additionally, if the region of
	concern is greater than the mark, the function will
	limit the number of transmissions to userspace by assuming
	the region /is/ being recovered when skipping the
	transmission.  This limits the amount of processing
	and updates the mark in 1/4 sec time steps.
	
	This patch fixes a problem where 'the mark' is not being
	updated because of faulty logic in the userspace log
	daemon.  When '--nosync' is used to create a cluster
	mirror, the userspace log daemon never has a chance
	to update the mark in the normal way.  The fix is to set
	the mark to "complete" if the mirror was created with
	the --nosync flag.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1726&r2=1.1727
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/cmirrord/functions.c.diff?cvsroot=lvm2&r1=1.23&r2=1.24

--- LVM2/WHATS_NEW	2010/08/26 16:29:12	1.1726
+++ LVM2/WHATS_NEW	2010/08/30 18:37:42	1.1727
@@ -1,5 +1,6 @@
 Version 2.02.74 - 
 ==================================
+  Fix opprobriously slow I/O to cluster mirrors created with --nosync.
   Make poll_mirror_progress report PROGRESS_CHECK_FAILED if LV is not a mirror.
   Like mirrors, don't scan origins if ignore_suspended_devices() is set.
   Fix return type qualifier to avoid compiler warning. (2.02.69)
--- LVM2/daemons/cmirrord/functions.c	2010/08/17 23:56:24	1.23
+++ LVM2/daemons/cmirrord/functions.c	2010/08/30 18:37:42	1.24
@@ -1268,6 +1268,7 @@
 		LOG_SPRINT(lc, "GET - SEQ#=%u, UUID=%s, nodeid = %u:: "
 			   "Resync work complete.",
 			   rq->seq, SHORT_UUID(lc->uuid), originator);
+		lc->sync_search = lc->region_count + 1;
 		return 0;
 	}
 


             reply	other threads:[~2010-08-30 18:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 18:37 jbrassow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-08 11:34 zkabelac
2011-09-06 18:24 zkabelac
2010-12-20 13:57 zkabelac
2010-08-17 23:56 jbrassow
2010-08-04 18:18 jbrassow
2010-06-18 20:58 jbrassow
2010-01-15 18:48 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=20100830183743.13927.qmail@sourceware.org \
    --to=jbrassow@sourceware.org \
    --cc=lvm-devel@redhat.com \
    --cc=lvm2-cvs@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 read-only IMAP folder(s) and NNTP newsgroup(s).