Distinguish between cells v1 and v2 in upgrades doc
The note about rolling upgrades not being supported for cells was referring to cells v1, so let's make that clear. We will support rolling upgrades for cells v2 deployments, we just haven't documented it yet (or done it in a grenade job). Change-Id: I6a8b3d3aaa49859e8b769a296684ac96883719f8
This commit is contained in:
parent
bcd0221c46
commit
068d2565d1
@ -251,10 +251,13 @@ RPC version pinning
|
||||
|
||||
.. note::
|
||||
|
||||
This does not apply to cells deployments since cells does not currently
|
||||
support rolling upgrades. It is assumed that cells deployments are
|
||||
This does not apply to cells v1 deployments since cells v1 does not
|
||||
support rolling upgrades. It is assumed that cells v1 deployments are
|
||||
upgraded in lockstep so n-1 cells compatibility does not work.
|
||||
|
||||
The procedure for rolling upgrades with multiple cells v2 cells is not
|
||||
yet determined.
|
||||
|
||||
Online Configuration Reload
|
||||
During the upgrade, we pin new serves at the older RPC version. When all
|
||||
services are updated to use newer code, we need to unpin them so we are
|
||||
|
Loading…
x
Reference in New Issue
Block a user