From: Vladimir Bashkirtsev <vladimir@bashkirtsev.com>
To: ceph-devel@vger.kernel.org
Subject: Ceph and KVM live migration
Date: Sun, 01 Jul 2012 10:12:25 +0930 [thread overview]
Message-ID: <4FEF9CF1.6030008@bashkirtsev.com> (raw)
Dear all,
Currently I testing KVMs running on ceph and particularly testing recent
cache feature. Performance is of course vastly improved but still have
occasional KVM hold ups - not sure who is at blame ceph of KVM. But I
will deal with it later. Right now I've got myself a question which I
could not get answered myself: if I do live migration of KVM while there
some uncommitted data in ceph cache will this cache be committed prior
cut-over to another host? Reading through the list I've got an
impression that it may be left uncommitted and thus it may cause data
corruption. I just would like a simple confirmation if code which
commits cache on cut-over to new host does exist and no data corruption
due to RBD cache+live migration should happen.
Regards,
Vladimir
next reply other threads:[~2012-07-01 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 0:42 Vladimir Bashkirtsev [this message]
2012-07-01 1:17 ` Ceph and KVM live migration Josh Durgin
2012-07-01 2:15 ` Vladimir Bashkirtsev
2012-07-01 2:29 ` Josh Durgin
2012-07-01 3:21 ` Vladimir Bashkirtsev
2012-07-02 18:21 ` Gregory Farnum
2012-07-02 19:00 ` Josh Durgin
2012-07-02 19:02 ` Christian Brunner
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=4FEF9CF1.6030008@bashkirtsev.com \
--to=vladimir@bashkirtsev.com \
--cc=ceph-devel@vger.kernel.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 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.