Sage,
It was backported to Jewel and Kraken, somewhat recently. It won't ever
be in Luminous because you removed it. It came in with the branch with
all the ENOSPC handling fixes. The backports include the tweak you did
to the config name(s), so the original name(s) were never in a release.
David
On 8/23/17 2:29 PM, Sage Weil wrote:
On Wed, 23 Aug 2017, David Zafman wrote:
Sage,
Should we backport http://tracker.ceph.com/issues/20730? ; It was removal of
the code to warn about OSDs space utilization differences.
It won't backport with a cherry-pick because in master the code moved then was
removed.
This was new in kraken, so I'm not sure there's anything to
backport (I don't think it's worth removing it from kraken)?
I think we should keep that ticket around because eventually this warning
probably makes sense. It might end up being generated by the balancer
module or something, though. But eventually we should address the
limitations (mainly making the warning not trigger when a new device is
added but hasn't been backfilled yet).
sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
