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 <jus...@erenkrantz.com> wrote: > On Fri, Dec 5, 2014 at 12:46 PM, Mark Nelson <mark.nel...@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 majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
