See to my next message:
>From time to time old monitor can’t connect to new monitors.
For example upgrade from 0.66 to 0.67
http://ceph.com/docs/master/release-notes/#upgrading-from-v0-66
• There is monitor internal protocol change, which means that v0.67
ceph-mon daemons cannot talk to v0.66 or older daemons. We recommend upgrading
all monitors at once (or in relatively quick succession) to minimize the
possibility of downtime.
I has test cluster on the 0.66 version and monitor upgrade was failed.
I the situation update one by one don’t help me when I upgrade middle monitor
instance.
Similar incompatible changes was few times. You can find it by word “protocol”
on the release notes page.
I want reserve storage for the situation when rolling update with incompatible
components will fail.
>
>
>> Le 28 avr. 2014 à 17:59, Timofey Koolin <[email protected]> a écrit :
>>
>> Now if I will upgrade monitors and upgrade will fail on second (of three)
>> monitor - cluster will down. Becouse it will have
>> 1 new monitor
>> 1 down monitor
>> 1 old monitor
>
> As of my compréhension, migration path is planned, between ceph release, to
> keep a minimum compatibility between old and new mon, in order ton keep the
> cluster up and running.
>
> In your case where you have 1new (upgraded), 1 old (non upgraded) and one
> down (being upgraded), the new and the old one still "speak" together, thus
> ceph -s should normally reports a healthy state, but with 2/3 mon up.
>
> Please correct if needed.
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
