From: David Zafman <dzafman@redhat.com>
To: Samuel Just <sjust@redhat.com>, Sage Weil <sweil@redhat.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Hammer incompat bits and ceph-objectstore-tool
Date: Tue, 17 Mar 2015 18:55:50 -0700 [thread overview]
Message-ID: <5508DB26.5000706@redhat.com> (raw)
During upgrade testing an error occurred because ceph-objectstore-tool
found during import on a Firefly node the compat_features from a export
from Hammer.
There are 2 new feature bits set as shown in the error message:
Export has incompatible features set
compat={},rocompat={},incompat={12=transaction hints,13=pg meta object}
In this case as far as I can tell these osd incompatible changes
wouldn't make the export data in any way incompatible. So we may have
to check compatibility bits on a case by case basis, if we want to allow
the tool to work in the most cases possible.
During upgrade testing it is interesting that one node has the
transaction hints feature, but other nodes still running firefly don't.
Is this a case where we don't have to wait for all OSDs to update
before the cluster can start handling OP_COLL_HINT operations?
David Zafman
next reply other threads:[~2015-03-18 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 1:55 David Zafman [this message]
2015-03-18 6:39 ` Hammer incompat bits and ceph-objectstore-tool Gregory Farnum
2015-03-18 13:50 ` Sage Weil
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=5508DB26.5000706@redhat.com \
--to=dzafman@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sjust@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.