From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: zhanghailiang <zhang.zhanghailiang@huawei.com>,
quintela@redhat.com, qemu-devel@nongnu.org, wency@cn.fujitsu.com,
lizhijian@cn.fujitsu.com, xiecl.fnst@cn.fujitsu.com,
Luiz Capitulino <lcapitulino@redhat.com>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH COLO-Frame (Base) v21 12/17] COLO: Add 'x-colo-lost-heartbeat' command to trigger failover
Date: Wed, 26 Oct 2016 14:59:57 +0100 [thread overview]
Message-ID: <20161026135957.GF2029@work-vm> (raw)
In-Reply-To: <20161026055157.GL1679@amit-lp.rh>
* Amit Shah (amit.shah@redhat.com) wrote:
> On (Tue) 18 Oct 2016 [20:10:08], zhanghailiang wrote:
> > We leave users to choose whatever heartbeat solution they want,
> > if the heartbeat is lost, or other errors they detect, they can use
> > experimental command 'x_colo_lost_heartbeat' to tell COLO to do failover,
> > COLO will do operations accordingly.
> >
> > For example, if the command is sent to the PVM, the Primary side will
> > exit COLO mode and take over operation.
>
> Primary should already be in control, so there's nothing special
> needed to 'take over operation'? At max, it should not do periodic
> syncs anymore till it hears from a (new) secondary.
But it has to stop waiting for an ack from the secondary, and stop sending
copies of block data to it etc.
Dave
> > If sent to the Secondary, the
> > secondary will run failover work, then take over server operation to
> > become the new Primary.
> >
> > Cc: Luiz Capitulino <lcapitulino@redhat.com>
> > Cc: Eric Blake <eblake@redhat.com>
> > Cc: Markus Armbruster <armbru@redhat.com>
> > Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> > Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> > Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
> Reviewed-by: Amit Shah <amit.shah@redhat.com>
>
>
> Amit
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-10-26 14:00 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 12:09 [Qemu-devel] [PATCH COLO-Frame (Base) v21 00/17] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) zhanghailiang
2016-10-18 12:09 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 01/17] migration: Introduce capability 'x-colo' to migration zhanghailiang
2016-10-26 4:32 ` Amit Shah
2016-10-18 12:09 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 02/17] COLO: migrate COLO related info to secondary node zhanghailiang
2016-10-26 4:35 ` Amit Shah
2016-10-18 12:09 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 03/17] migration: Enter into COLO mode after migration if COLO is enabled zhanghailiang
2016-10-26 4:50 ` Amit Shah
2016-10-26 13:49 ` Hailiang Zhang
2016-10-27 3:58 ` Amit Shah
2016-10-27 6:10 ` Hailiang Zhang
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 04/17] migration: Switch to COLO process after finishing loadvm zhanghailiang
2016-10-26 5:01 ` Amit Shah
2016-10-26 13:55 ` Hailiang Zhang
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 05/17] COLO: Establish a new communicating path for COLO zhanghailiang
2016-10-26 5:06 ` Amit Shah
2016-10-26 14:05 ` Hailiang Zhang
2016-10-27 3:57 ` Amit Shah
2016-10-27 6:06 ` Hailiang Zhang
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 06/17] COLO: Introduce checkpointing protocol zhanghailiang
2016-10-26 5:25 ` Amit Shah
2016-10-26 14:18 ` Hailiang Zhang
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 07/17] COLO: Add a new RunState RUN_STATE_COLO zhanghailiang
2016-10-26 7:06 ` Amit Shah
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 08/17] COLO: Send PVM state to secondary side when do checkpoint zhanghailiang
2016-10-26 5:36 ` Amit Shah
2016-10-26 5:37 ` Amit Shah
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 09/17] COLO: Load VMState into QIOChannelBuffer before restore it zhanghailiang
2016-10-26 5:40 ` Amit Shah
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 10/17] COLO: Add checkpoint-delay parameter for migrate-set-parameters zhanghailiang
2016-10-26 5:45 ` Amit Shah
2016-10-26 13:39 ` Eric Blake
2016-10-26 14:43 ` Hailiang Zhang
2016-10-26 14:40 ` Hailiang Zhang
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 11/17] COLO: Synchronize PVM's state to SVM periodically zhanghailiang
2016-10-26 5:46 ` Amit Shah
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 12/17] COLO: Add 'x-colo-lost-heartbeat' command to trigger failover zhanghailiang
2016-10-26 5:51 ` Amit Shah
2016-10-26 13:59 ` Dr. David Alan Gilbert [this message]
2016-10-26 15:32 ` Hailiang Zhang
2016-10-26 14:50 ` Hailiang Zhang
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 13/17] COLO: Introduce state to record failover process zhanghailiang
2016-10-26 5:54 ` Amit Shah
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 14/17] COLO: Implement the process of failover for primary VM zhanghailiang
2016-10-26 5:58 ` Amit Shah
2016-10-26 14:59 ` Hailiang Zhang
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 15/17] COLO: Implement failover work for secondary VM zhanghailiang
2016-10-26 5:59 ` Amit Shah
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 16/17] docs: Add documentation for COLO feature zhanghailiang
2016-10-26 6:06 ` Amit Shah
2016-10-18 12:10 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 17/17] configure: Support enable/disable " zhanghailiang
2016-10-26 6:07 ` Amit Shah
2016-10-26 13:42 ` Eric Blake
2016-10-26 15:11 ` Hailiang Zhang
2016-10-27 3:54 ` Amit Shah
2016-10-26 15:09 ` Hailiang Zhang
2016-10-26 6:09 ` [Qemu-devel] [PATCH COLO-Frame (Base) v21 00/17] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) Amit Shah
2016-10-26 6:43 ` Hailiang Zhang
2016-10-26 8:26 ` Amit Shah
2016-10-26 9:53 ` Li Zhijian
2016-10-26 10:17 ` Li Zhijian
2016-10-26 10:14 ` Li Zhijian
2016-10-26 15:52 ` Hailiang Zhang
2016-10-27 3:52 ` Amit Shah
2016-10-27 5:55 ` Hailiang Zhang
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=20161026135957.GF2029@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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 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).