i was just testing an upgrade of some monitors in a test cluster from hammer (0.94.7) to jewel (10.2.5). after upgrade each of the first two monitors, i stopped and restarted a single osd to cause changes in the maps. the same error messages showed up in ceph -w. i haven't dug into it much but just wanted to second that i've seen this happen on a recent hammer to recent jewel upgrade.
mike On Wed, Jan 18, 2017 at 4:25 AM, Piotr Dałek <piotr.da...@corp.ovh.com> wrote: > On 01/17/2017 12:52 PM, Piotr Dałek wrote: > >> During our testing we found out that during upgrade from 0.94.9 to 10.2.5 >> we're hitting issue http://tracker.ceph.com/issues/17386 ("Upgrading >> 0.94.6 >> -> 0.94.9 saturating mon node networking"). Apparently, there's a few >> commits for both hammer and jewel which are supposed to fix this issue for >> upgrades from 0.94.6 to 0.94.9 (and possibly for others), but we're still >> seeing this upgrading to Jewel, and symptoms are exactly same - after >> upgrading MONs, each not yet upgraded OSD takes full OSDMap from monitors >> after failing the CRC check. Anyone else encountered this? >> > > http://tracker.ceph.com/issues/18582 > > -- > Piotr Dałek > piotr.da...@corp.ovh.com > https://www.ovh.com/us/ > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
