Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tidb-in-kubernetes: add force upgrade feature usage #1576

Merged
merged 2 commits into from
Jul 8, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions dev/how-to/maintain/tidb-in-kubernetes/tidb-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -222,6 +222,25 @@ helm upgrade ${releaseName} pingcap/tidb-cluster --version=${chartVersion} -f /h
>
> 目前,集群创建后修改 PD 的 `schedule` 和 `replication` 配置(`values.yaml` 中的`maxStoreDownTime` 和 `maxReplicas` 参数,PD 配置文件中所有 `[schedule]` 和 `[replication]` 部分的配置 )然后运行 `helm upgrade` 无法生效。集群创建后,你必须通过 `pd-ctl` 配置这些参数,请参考:[pd-ctl](/reference/tools/pd-control/)。

> **注意:**
>
> 如果 PD 集群不可用,[TiDB 集群伸缩](#TiDB-集群伸缩),[升级 TiDB 集群](#升级-TiDB-集群)和[修改 TiDB 集群配置](#修改-TiDB-集群配置)都无法操作,从 TiDB Operator 版本 > v1.0.0-beta.3 开始,支持 `force-upgrade`,在 PD 集群不可用的情况下,允许用户通过下面步骤强制升级集群以恢复集群功能:
>
> {{< copyable "shell-regular" >}}
>
> ```shell
> kubectl annotate --overwrite tc ${releaseName} -n ${namespace} tidb.pingcap.com/force-upgrade=true
> ```
> 然后执行对应操作中的 `helm upgrade` 命令。
>
> PD 集群恢复后,**必须**执行下面命令禁用强制升级功能,否则下次升级过程可能会出现异常:
>
> {{< copyable "shell-regular" >}}
>
> ```shell
> kubectl annotate tc ${releaseName} -n ${namespace} tidb.pingcap.com/force-upgrade-
> ```

## 销毁 TiDB 集群

要销毁 TiDB 集群,执行以下命令:
Expand Down
19 changes: 19 additions & 0 deletions v3.0/how-to/maintain/tidb-in-kubernetes/tidb-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -222,6 +222,25 @@ helm upgrade ${releaseName} pingcap/tidb-cluster --version=${chartVersion} -f /h
>
> 目前,集群创建后修改 PD 的 `schedule` 和 `replication` 配置(`values.yaml` 中的`maxStoreDownTime` 和 `maxReplicas` 参数,PD 配置文件中所有 `[schedule]` 和 `[replication]` 部分的配置 )然后运行 `helm upgrade` 无法生效。集群创建后,你必须通过 `pd-ctl` 配置这些参数,请参考:[pd-ctl](/reference/tools/pd-control/)。

> **注意:**
>
> 如果 PD 集群不可用,[TiDB 集群伸缩](#TiDB-集群伸缩),[升级 TiDB 集群](#升级-TiDB-集群)和[修改 TiDB 集群配置](#修改-TiDB-集群配置)都无法操作,从 TiDB Operator 版本 > v1.0.0-beta.3 开始,支持 `force-upgrade`,在 PD 集群不可用的情况下,允许用户通过下面步骤强制升级集群以恢复集群功能:
>
> {{< copyable "shell-regular" >}}
>
> ```shell
> kubectl annotate --overwrite tc ${releaseName} -n ${namespace} tidb.pingcap.com/force-upgrade=true
> ```
> 然后执行对应操作中的 `helm upgrade` 命令。
>
> PD 集群恢复后,**必须**执行下面命令禁用强制升级功能,否则下次升级过程可能会出现异常:
>
> {{< copyable "shell-regular" >}}
>
> ```shell
> kubectl annotate tc ${releaseName} -n ${namespace} tidb.pingcap.com/force-upgrade-
> ```

## 销毁 TiDB 集群

要销毁 TiDB 集群,执行以下命令:
Expand Down