All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zhijian <lizhijian@cn.fujitsu.com>
To: Wen Congyang <wency@cn.fujitsu.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Changlong Xie <xiecl.fnst@cn.fujitsu.com>,
	zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: Simon Kollberg <dv11skg@cs.umu.se>, Luis Tomas <luis@cs.umu.se>,
	qemu devel <qemu-devel@nongnu.org>,
	qemu block <qemu-block@nongnu.org>, Abel Souza <abel@cs.umu.se>
Subject: Re: [Qemu-devel] COLO: how to flip a secondary to a primary?
Date: Mon, 25 Jan 2016 10:11:13 +0800	[thread overview]
Message-ID: <56A58441.4030704@cn.fujitsu.com> (raw)
In-Reply-To: <56A57B43.1040103@cn.fujitsu.com>



On 01/25/2016 09:32 AM, Wen Congyang wrote:
>> >    f) I've not thought about the colo-proxy that much yet - I guess that
>> >       existing connections need to keep their sequence number offset but

Strictly speaking, after failover, we only need to keep servicing for the tcp connections which are
established after the last checkpoint but not all existing connections. Because after a checkpoint
(primary and secondary node works well), primary vm and secondary vm is same, that means the existing
tcp connection has the same sequence。

>> >       new connections made by what is now the primary dont need to do anything
>> >       special.
Yes, you are right.


> Hailiang or Zhijian can answer this question.


Thanks
Li Zhijian

  reply	other threads:[~2016-01-25  2:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 19:35 [Qemu-devel] COLO: how to flip a secondary to a primary? Dr. David Alan Gilbert
2016-01-25  1:32 ` Wen Congyang
2016-01-25  2:11   ` Li Zhijian [this message]
2016-01-25 20:20     ` Dr. David Alan Gilbert
2016-01-26  1:16       ` Li Zhijian
2016-01-25 18:59   ` Dr. David Alan Gilbert
2016-01-26  1:06     ` Wen Congyang

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=56A58441.4030704@cn.fujitsu.com \
    --to=lizhijian@cn.fujitsu.com \
    --cc=abel@cs.umu.se \
    --cc=dgilbert@redhat.com \
    --cc=dv11skg@cs.umu.se \
    --cc=luis@cs.umu.se \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wency@cn.fujitsu.com \
    --cc=xiecl.fnst@cn.fujitsu.com \
    --cc=zhang.zhanghailiang@huawei.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.