Quoting Brett Chancellor (bchancellor@xxxxxxxxxxxxxx): > The error will go away once you start storing data in the other pools. Or, > you could simply silence the message with mon_pg_warn_max_object_skew = 0 Ran into this issue myself (again). Note to self: You need to restart the _active_ MGR to get this option active. That's not written anywhere, yet. I'll see if I can make a doc PR to fix that. Gr. Stefan P.s. this option really does more harm than good IMHO. Mixed clusters with cephfs / RGW mixed with RBD pools, and or newly created pools, will run into this issue sooner or later. -- | BIT BV http://www.bit.nl/ Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / info@xxxxxx _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |