yujunjun/datahub
2
0
Fork 0
mirror of https://github.com/datahub-project/datahub.git synced 2025-09-07 00:00:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(nocode): Update migration docs with workaround for stuck upgrade(#2649)

Browse Source
This commit is contained in:
Dexter Lee 2021-06-04 00:18:41 -07:00 committed by GitHub
parent d5934f70bb
commit e187b07cf3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 19 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
docs/advanced/no-code-upgrade.md
View File

@ -74,6 +74,19 @@ You can either
To see the required environment variables, see the (datahub-upgrade)[../../docker/datahub-upgrade/README.md]
documentation
##### How to fix the "listening to port 5005" issue
Fix for this issue have been published to the acryldata/datahub-upgrade:head tag. Please pull latest master and rerun
the upgrade script.
However, we have seen cases where the problematic docker image is cached and docker does not pull the latest version. If
the script fails with the same error after pulling latest master, please run the following command to clear the docker
image cache.
```
docker images -a | grep acryldata/datahub-upgrade | awk '{print $3}' | xargs docker rmi -f
```
#### Helm Deployments
Upgrade to latest helm charts by running the following after pulling latest master.
@ -82,8 +95,8 @@ Upgrade to latest helm charts by running the following after pulling latest mast
helm upgrade datahub datahub/ --values datahub/quickstart-values.yaml
```
This will upgrade all pods to version 0.8.0, and once all pods are up and ready, datahub-upgrade job will start,
running the above docker image to migrate to the new stores.
This will upgrade all pods to version 0.8.0, and once all pods are up and ready, datahub-upgrade job will start, running
the above docker image to migrate to the new stores.
### Step 3 (Optional): Cleaning Up
@ -121,40 +134,9 @@ documentation
TODO
#### Docker Compose Deployments
The easiest option is to execute the `run_upgrade.sh` script located under `docker/datahub-upgrade/nocode`.
```
cd docker/datahub-upgrade/nocode
./upgrade.sh
```
In both cases, the default environment variables will be used (`docker/datahub-upgrade/env/docker.env`). These assume
that your deployment is local. If this is not the case, you'll need to define your own environment variables to tell the
upgrade system where your DataHub containers reside.
You can either
1. Change `docker/datahub-upgrade/env/docker.env` in place and then run one of the above commands OR
2. Define a new ".env" file containing your variables and
execute `docker pull acryldata/datahub-upgrade && docker run acryldata/datahub-upgrade:latest -u NoCodeDataMigration`
To see the required environment variables, see the (datahub-upgrade)[../../docker/datahub-upgrade/README.md]
documentation
#### Helm Deployments
TODO
## Support
The Acryl team will be on standby to assist you in your migration. Please do not hesitate to reach out to the following
folks if you find trouble with the upgrade or have feedback on the process. We will work closely to make sure you can
continue to operate DataHub smoothly.
- John Joyce
- Gabe Lyons
- Dexter Lee
If there is feedback on the process, please
The Acryl team will be on standby to assist you in your migration. Please
join [#release-0_8_0](https://datahubspace.slack.com/archives/C0244FHMHJQ) channel and reach out to us if you find
trouble with the upgrade or have feedback on the process. We will work closely to make sure you can continue to operate
DataHub smoothly.