From: Mark Nelson <mark.nelson@inktank.com>
To: Fred Yang <frederic.yang@gmail.com>,
Justin Erenkrantz <justin@erenkrantz.com>
Cc: Gregory Farnum <greg@gregs42.com>, Sage Weil <sweil@redhat.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
ceph-users <ceph-users@ceph.com>
Subject: Re: experimental features
Date: Mon, 08 Dec 2014 08:33:25 -0600 [thread overview]
Message-ID: <5485B6B5.8010802@redhat.com> (raw)
In-Reply-To: <CAPHS-z7cOLokgHe7Ky+SJQMGPbZmY26o+EeA1i=qo+i_XnYg5g@mail.gmail.com>
I've been thinking for a while that we need another more general command
than Ceph health to more generally inform you about your cluster. IE I
personally don't like having min/max PG warnings in Ceph health (they
can be independently controlled by ceph.conf options but that kind of
approach won't scale). I'd like another command that I can run that
tells me about this kind of thing. Same thing with experimental
features. I don't want ceph health warning me if they've been enabled,
but I do want to know if they've ever been enabled, when, and whether
they are still in effect.
Mark
On 12/08/2014 06:57 AM, Fred Yang wrote:
> You will have to consider in the real world whoever built the cluster
> might not document the dangerous option to let support stuff or
> successor aware. Thus any experimental feature considered not safe for
> production should be included in a warning message in 'ceph health', and
> logs, either log it periodically or log the warning msg upon restart.
> Feature-wise, 'ceph health detail' should give you a report over all
> important features/options of the cluster as well.
>
> -Fred
>
> On Sun, Dec 7, 2014, 11:15 PM Justin Erenkrantz <justin@erenkrantz.com
> <mailto:justin@erenkrantz.com>> wrote:
>
> On Fri, Dec 5, 2014 at 12:46 PM, Mark Nelson
> <mark.nelson@inktank.com <mailto:mark.nelson@inktank.com>> wrote:
> > I'm in favor of the "allow experimental features" but instead
> call it:
> >
> > "ALLOW UNRECOVERABLE DATA CORRUPTING FEATURES" which makes things
> a little
> > more explicit. With great power comes great responsibility.
>
> +1.
>
> For Subversion, we utilize SVN_I_LOVE_CORRUPTED_XXX for a few options
> that can cause data corruption. -- justin
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/__majordomo-info.html
> <http://vger.kernel.org/majordomo-info.html>
>
next prev parent reply other threads:[~2014-12-08 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 17:36 experimental features Sage Weil
2014-12-05 17:39 ` Gregory Farnum
2014-12-05 17:46 ` Mark Nelson
2014-12-08 4:10 ` Justin Erenkrantz
2014-12-08 12:57 ` Fred Yang
2014-12-08 14:33 ` Mark Nelson [this message]
2014-12-09 5:25 ` [ceph-users] " Christian Balzer
[not found] ` <CAOGLoJN2wSxMgtok6aATSW5o-Abqcv2bdVo+dVfaEbG4iyiQSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-25 22:27 ` Sage Weil
[not found] ` <alpine.DEB.2.00.1412050927150.24079-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-12-05 17:47 ` David Champion
2014-12-05 21:46 ` [ceph-users] " Nigel Williams
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=5485B6B5.8010802@redhat.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.com \
--cc=frederic.yang@gmail.com \
--cc=greg@gregs42.com \
--cc=justin@erenkrantz.com \
--cc=mnelson@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.