A rolling upgrade to 0.48 will be possible, provided the old version is reasonably recent (0.45ish or later; I need to confirm that). The upgrade will be a bit awkward because of teh disk format upgrade, however. Each ceph-osd will need to do a conversion on startup which can take a while, so you will want to restart them on a per-host basis or per-rack basis (depending on how your CRUSH map is structured). The monitors are also doing an ncoding change, but will only make the transition after all members of the quorum run the new code. If you start the upgrade with a degraded cluster and have another failure, you'll need to make sure the recovering node(s) run new code. The goal is to make all future upgrades possible using rolling upgrades. It will be tricky with some of the OSD changes coming, but that is the goal. sage On Fri, 22 Jun 2012, John Axel Eriksson wrote: > I guess this has been asked before, I'm just new to the list and > wondered whether it's possible to do > rolling upgrades of mons, osds and radosgw? We will soon be in the > process of migrating from our current > storage solution to Ceph/RGW. We will only use the object storage, > actually mainly the S3-interface radosgw > supplies. > > Right now we have a very small test-installation - 1 mon, 2 osds where > the mon also runs rgw. Next week I've > heard that 0.48 might be released, if we upgrade to that, do we have > to shut down the cluster during the upgrade > or can we do a rolling upgrade while still responding to PUTs and > GETs? If not possible yet, is this in the pipeline? > > Best, > John > -- > 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 > > -- 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
