From: xxhdx1985126 <xxhdx1985126@163.com>
To: jdillama@redhat.com
Cc: Haomai Wang <haomai@xsky.com>, Sage Weil <sweil@redhat.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Re: Re:Re: Re:Re:Re:Re: How does rbd-mirror preserve the order of WRITE operations that finished on the primary cluster
Date: Wed, 14 Jun 2017 10:03:57 +0800 (CST) [thread overview]
Message-ID: <161277d6.3133.15ca457d04d.Coremail.xxhdx1985126@163.com> (raw)
In-Reply-To: CA+aFP1B6KpO4QV=gO0VLU6manv9vRiX6_aXBr50VUu9Xn=4b3Q@mail.gmail.com
Hi, thanks for your reply. Now, I have another question. Given all the writes are replicated in order, why is flush event replicated? As far as I know, what a flush does is just making previous writes committed and doesn't do any modification to the data, which makes it seem to me that replicating it or not doesn't make any difference.
Sent from my Mi phone
On Jason Dillaman <jdillama@redhat.com>, Jun 6, 2017 19:20 wrote:
On Tue, Jun 6, 2017 at 4:07 AM, xxhdx1985126 <xxhdx1985126@163.com> wrote:
> So, if that case happens, rbd-mirror will go on replicate subsequent writes, is this right?
Yes -- until it reaches a flush event and is stalled on the
uncommitted IO from the down OSD (or until it reaches the hard-stop of
100 in-flight, uncommitted IOs).
--
Jason
next prev parent reply other threads:[~2017-06-14 2:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 4:05 How does rbd-mirror preserve the order of WRITE operations that finished on the primary cluster xxhdx1985126
2017-06-05 12:00 ` Jason Dillaman
2017-06-05 15:49 ` xxhdx1985126
2017-06-05 16:21 ` Sage Weil
[not found] ` <428d3e79.3d2.15c7a56a64f.Coremail.xxhdx1985126@163.com>
2017-06-05 22:22 ` Sage Weil
2017-06-05 22:50 ` xxhdx1985126
2017-06-06 3:04 ` xxhdx1985126
2017-06-06 3:13 ` Haomai Wang
2017-06-06 4:05 ` xxhdx1985126
2017-06-06 7:34 ` xxhdx1985126
2017-06-06 7:40 ` xxhdx1985126
2017-06-06 7:49 ` Haomai Wang
2017-06-06 8:07 ` xxhdx1985126
2017-06-06 11:20 ` Jason Dillaman
2017-06-14 2:03 ` xxhdx1985126 [this message]
[not found] ` <47d3f4bc.3a4b.15c7b3fceb0.Coremail.xxhdx1985126@163.com>
2017-06-06 14:01 ` Sage Weil
2017-06-07 15:36 ` xxhdx1985126
2017-06-07 15:42 ` xxhdx1985126
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=161277d6.3133.15ca457d04d.Coremail.xxhdx1985126@163.com \
--to=xxhdx1985126@163.com \
--cc=ceph-devel@vger.kernel.org \
--cc=haomai@xsky.com \
--cc=jdillama@redhat.com \
--cc=sweil@redhat.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.