clean up min/max span warning
Sage cleaned up the name of the config and some minor output changes:
#7 Updated by Nathan Cutler over 3 years ago
David, do you mean daa0793c393a21bd2dd2ec52a0efd181e1032400 ?
smithfarm@wilbur:~/src/ceph/smithfarm/ceph> git log -S 'difference between min' src/mon/PGMonitor.cc commit daa0793c393a21bd2dd2ec52a0efd181e1032400 Author: Sage Weil <firstname.lastname@example.org> Date: Tue May 16 13:20:51 2017 -0400 mon/PGMonitor: move most of get_health into PGMap Leave the legacy full/nearfull stuff in PGMonitor (although we'll still need to clean out the PGMap fields too). This is cut and paste, some stripping of pg_map., g_conf -> cct->_conf, and a bit of whitespace cleanup. Signed-off-by: Sage Weil <email@example.com> commit 489e810c37ed6fb9d32d1015634041a577501ee4 Author: Sage Weil <firstname.lastname@example.org> Date: Tue Apr 18 13:54:56 2017 -0400 mon/PGMonitor: clean up min/max span warning Clean up option naming. Signed-off-by: Sage Weil <email@example.com>
#8 Updated by David Zafman over 3 years ago
7832c53375ad24f3b54a68a3c63b056e69e3fa0d removed it after it was moved by daa0793c393a21bd2dd2ec52a0efd181e1032400
commit 7832c53375ad24f3b54a68a3c63b056e69e3fa0d Author: Sage Weil <firstname.lastname@example.org> Date: Fri Jul 21 11:58:08 2017 -0400 mon/PGMap: remove skewed utilizatoin warning This has a few problems: 1- It does not do it's analysis over CRUSH rule roots/classes, which means that an innocent user of classes will see skewed usage (bc hdds are more full than ssds, say) 2- It does not take degraded clusters into account, which means the warning will appear when a fresh OSD is added. See http://tracker.ceph.com/issues/20730 Signed-off-by: Sage Weil <email@example.com>