Rolling Back heading-link-icon

In summary, the upgrade from Corda 5.2.1 to 5.2.2 requires you to perform the following steps:

  • Scale back all Corda workers to zero replicas.
  • Bring the workers back at the latest version.

To roll back this process, all that you need to do is bring Corda 5.2.1 workers back up.

You can roll back an upgrade up until the point where Corda 5.2.2 workers are brought back up to a running state. At this point, the 5.2.2 workers start publishing the 5.2.1 messages to Kafka and the 5.2.1 worker software cannot necessarily read them.

To bring Corda 5.2.1 workers back, perform one of the following actions:

  • You can use kubectl scale with a replica count greater than one, reversing the step below where they were scaled to zero replicas.
  • Or you can issue a Helm upgrade command which resets the values you installed Corda 5.2.1 with, including replica counts, for example:
helm upgrade corda -n corda \
helm fetch oci://registry-1.docker.io/corda/corda --version 5.2.1
--version "5.2.1" \
--values artifactory_values.yaml \
--wait

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.