迁移中控机与备份,新增离线部署场景需要备份.json文件
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 1.2k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 31
Description
File: /release-6.5/tiup/tiup-cluster.md
离线部署情况下,如果不做此操作,会报如下错误:
tiup cluster list
Error: stat /opt/soft/tidb-community-server-v6.1.1-linux-amd64: no such file or directory
/opt/soft/tidb-community-server-v6.1.1-linux-amd64 这是当前集群离线安装的软件目录。
建议文档新增离线部署场景需要备份.json文件
离线部署场景需要备份.json文件
把软件解压目录下面的.json结尾的文件拷贝过来后就可以拉。
原中控机:将json结尾的文件拷贝到共享目录下或者通过scp等命令拷贝到目标中控机,也可以从官方下载对应版本的离线安装包解压获取相应的.json文件。
[tidb@centos-bsf36cfx ~]$ cp /opt/soft/tidb-community-server-v6.1.1-linux-amd64/*json /backup/tidb-test/tidb-community-server-v6.1.1-linux-amd64/
如果目标中控机镜像目录跟原来的不一致,需要手动设置
目标中控机:tiup mirror set 重新设置下镜像目录
[tidb@centos-gxb9vid4 ~]$ tiup mirror set /backup/tidb-test/tidb-community-server-v6.1.1-linux-amd64/
Successfully set mirror to /backup/tidb-test/tidb-community-server-v6.1.1-linux-amd64
再次运行tiup命令,正常了。
[tidb@centos-gxb9vid4 ~]$ tiup cluster list
tiup is checking updates for component cluster ...
Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.10.3/tiup-cluster list
Name User Version Path PrivateKey
---- ---- ------- ---- ----------
tidb-test tidb v6.1.1 /home/tidb/.tiup/storage/cluster/clusters/tidb-test /home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open release-6.5/tiup/tiup-cluster.md and review the existing offline deployment or migration guidance. Add the reported offline backup procedure for the .json files and the tiup mirror set step, using the commands and output in the issue; done means the recovery steps are clear and complete for this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100