On 4/25/24 10:53, Vladislav Odintsov wrote:
> Hi Ilya,
>
> I’ve got question regarding upgrade of clustered ovsdb-servers from 3.1 to
> 3.2+ version.
> ovsdb(7) states that the recommended path for upgrade is to upgrade
> ovsdb-servers one-by-one
> and that after upgrade ovsdb-server should be started with option
> --disable-file-no-data-conversion
> and after whole cluster is upgradede, it is needed to enable no-data
> conversion via appctl.
>
> I’ve ran through code and did some upgrade tests, so my question is:
> Do I understand correctly, that if there is no necessity to call schema
> conversion after start
> and before end of cluster upgrade, so it is allowed just to restart
> ovsdb-servers without
> --disable-file-no-data-conversion option and this will not have any downsides?
Simply re-starting removing the option is enough. There is no need
to enable specifically via appctl in this case.
Also, we did actually backport parts of the format change to 3.1.
It should be in v3.1.2 release and newer. So, technically, if you're
performing upgrade from v3.1.2+, it should be safe to just upgrade as
usual. ovsdb-servr v3.1.2 understands new database format, though it
can't produce it on its own. See the following commit on branch-3.1:
9529e9aa967c ("ovsdb: Allow conversion records with no data in a clustered
storage.")
It would be painful to document all the combinations of minor versions,
so it's not an officially supported upgrade path, but it is there if
you know what are you doing.
Best regards, Ilya Maximets.
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
