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.

Sign up for GitHub

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

pdms: remove pd playground (#16919) #16920

Merged
merged 3 commits into from
Apr 2, 2024
Merged

pdms: remove pd playground (#16919) #16920

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b4fe8d6
remove playground
HuSharp Apr 1, 2024
686dccc
remove release note
HuSharp Apr 1, 2024
d85a25f
Apply suggestions from code review
HuSharp Apr 2, 2024
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
15 changes: 1 addition & 14 deletions pd-microservices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,7 @@ In addition, when the scheduling module is changed, you can update the `scheduli

## Usage

Currently, PD microservices can be deployed using TiDB Operator or TiUP Playground.

<SimpleTab>
<div label="TiDB Operator">
Currently, PD microservices can be deployed using TiDB Operator.

For detailed information on using TiDB Operator, see the following documents:

Expand All @@ -52,16 +49,6 @@ For detailed information on using TiDB Operator, see the following documents:
- [Modify PD microservices](https://docs.pingcap.com/tidb-in-kubernetes/dev/modify-tidb-configuration#modify-pd-microservice-configuration)
- [Scale PD microservice components](https://docs.pingcap.com/tidb-in-kubernetes/dev/scale-a-tidb-cluster#scale-pd-microservice-components)

</div>
<div label="TiUP Playground">

For detailed information on using TiUP Playground, see the following document:

- [Deploy PD microservices](/tiup/tiup-playground.md#deploy-pd-microservices)

</div>
</SimpleTab>

When deploying and using PD microservices, pay attention to the following:

- After you enable microservices and restart PD for a cluster, PD stops allocating TSO for the cluster. Therefore, you need to deploy the `tso` microservice in the cluster when you enable microservices.
Expand Down
2 changes: 1 addition & 1 deletion releases/release-8.0.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ Quick access: [Quick start](https://docs.pingcap.com/tidb/v8.0/quick-start-with-

Each microservice is deployed as an independent process. If you configure more than one replica for a microservice, the microservice automatically implements a primary-secondary fault-tolerant mode to ensure high availability and reliability of the service.

Currently, PD microservices can only be deployed using TiDB Operator and TiUP playground. It is recommended to consider this mode when PD becomes a significant performance bottleneck that cannot be resolved by scaling up.
Currently, PD microservices can only be deployed using TiDB Operator. It is recommended to consider this mode when PD becomes a significant performance bottleneck that cannot be resolved by scaling up.

For more information, see [documentation](/pd-microservices.md).

Expand Down
15 changes: 1 addition & 14 deletions tiup/tiup-playground.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,17 +170,4 @@ You can specify a `pid` in the `tiup playground scale-in` command to scale in th

```shell
tiup playground scale-in --pid 86526
```

## Deploy PD microservices

Starting from v8.0.0, PD supports the [microservice mode](/pd-microservices.md) (experimental). You can deploy the `tso` microservice and `scheduling` microservice for your cluster using TiUP Playground as follows:

```shell
tiup playground v8.0.0 --pd.mode ms --pd.api 3 --pd.tso 2 --pd.scheduling 3
```

- `--pd.mode`: setting it to `ms` means enabling the microservice mode for PD.
- `--pd.api num`: specifies the number of APIs for PD microservices. It must be at least `1`.
- `--pd.tso num`: specifies the number of instances to be deployed for the `tso` microservice.
- `--pd.scheduling num`: specifies the number of instances to be deployed for the `scheduling` microservice.
```
Loading