On Wed, Jul 12, 2017 at 11:31 AM, Dan van der Ster <dan@xxxxxxxxxxxxxx> wrote: > On Wed, Jul 12, 2017 at 5:51 PM, Abhishek L > <abhishek.lekshmanan@xxxxxxxxx> wrote: >> On Wed, Jul 12, 2017 at 9:13 PM, Xiaoxi Chen <superdebuger@xxxxxxxxx> wrote: >>> +However, it also introduced a regression that could cause MDS damage. >>> +Therefore, we do *not* recommend that Jewel users upgrade to this version - >>> +instead, we recommend upgrading directly to v10.2.9 in which the regression is >>> +fixed. >>> >>> It looks like this version is NOT production ready. Curious why we >>> want a not-recwaended version to be released? >> >> We found a regression in MDS right after packages were built, and the release >> was about to be announced. This is why we didn't announce the release. >> We're currently running tests after the fix for MDS was merged. >> >> So when we do announce the release we'll announce 10.2.9 so that users >> can upgrade from 10.2.7->10.2.9 > > Suppose some users already upgraded their CephFS to 10.2.8 -- what is > the immediate recommended course of action? Downgrade or wait for the > 10.2.9 ? I'm not aware of or see any changes that would make downgrading back to 10.2.7 a problem but the safest thing to do would be to replace the v10.2.8 ceph-mds binaries with the v10.2.7 binary. If that's not practical, I would recommend a cluster-wide downgrade to 10.2.7. -- Patrick Donnelly _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |