Comment 14 for bug 2043336
Revision history for this message
| Christian Rohmann (christian-rohmann) wrote | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Tyler I suppose you are referring to e.g. https://<email address hidden>
Yes, mClock seems, also reading through the other recent posts, to be something operators have issues with.
Either with slow convergence (recovery), influence of scrubbing, ....
And there are more fixes incoming: https:/
But considering the SRU / update from 17.2.6 to 17.2.7 those might also not be problems / regressions of this particular point release. All of 17.x (Quincy) is using mClock scheduler by default. I believe it's more about more installations moving to mClock that we now see more and more issues.
What I am trying to say is that 17.2.7 might actually not make things any worse, but could actually deliver fixes / improvements that Ceph has done.