You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, MetaDataUpgrader is only invoked during full cluster restart. Since 6.0 needs to support rolling upgrades we need to also invoke the same processes during rolling restart. This call should be performed when the last node with a version older than master leaves the cluster. A special meta data marker should be placed into cluster state to prevent old nodes from rejoining the cluster after the metadata is updated.
The text was updated successfully, but these errors were encountered:
In elastic#24379 we added ability to upgrade templates on full cluster startup. This PR invokes the same update procedure also when a new node first joins the cluster allowing to update templates on a full cluster restart.
Closeselastic#24680
In #24379 we added ability to upgrade templates on full cluster startup. This PR invokes the same update procedure also when a new node first joins the cluster allowing to update templates on a rolling cluster restart as well.
Closes#24680
In #24379 we added ability to upgrade templates on full cluster startup. This PR invokes the same update procedure also when a new node first joins the cluster allowing to update templates on a rolling cluster restart as well.
Closes#24680
Currently, MetaDataUpgrader is only invoked during full cluster restart. Since 6.0 needs to support rolling upgrades we need to also invoke the same processes during rolling restart. This call should be performed when the last node with a version older than master leaves the cluster. A special meta data marker should be placed into cluster state to prevent old nodes from rejoining the cluster after the metadata is updated.
The text was updated successfully, but these errors were encountered: