To roll back the Corda 5.0 to Corda 5.1 upgrade process, restore the database backups and restart the Corda 5.0 workers.
You can no longer roll back an upgrade after:
- Kafka topics or ACLs are deleted. R3 recommends that you do not delete old topics or ACLs until the upgrade to Corda 5.1 is complete.
- Corda 5.1 workers are launched and marked as
To restart the Corda 5.0 workers, you can do one of the following:
Reverse the commands in Scale Down the Running Corda Worker Instances that scaled the workers to zero replicas.
Issue a Helm upgrade command that resets the values you installed Corda 5.0 with, which includes replica counts. For example:
helm upgrade corda -n corda \ oci://corda-os-docker.software.r3.com/helm-charts/release-22.214.171.124/corda \ --version "5.0.0" \ --values 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
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.