Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: TiDB Dashboard 如何从PD 拆离?
[TiDB Usage Environment] Testing
[TiDB Version] 6.2.0-6.5.0
[Encountered Issues: Problem Description and Impact]
- How to separate TiDB Dashboard from PD when deploying the cluster using tiup?
- For an already deployed cluster (deployed with tiup), can the Dashboard be separated from PD? If so, what are the steps?
Currently, it should not be supported. The dashboard itself is a functional module of PD.
I saw this part in the 6.2 Release Notes, but I couldn’t find the specific configuration method.
TiDB 6.2.0 Release Notes | PingCAP Docs
The new version’s features have just been released, so there might be fewer people who have tried them out. If you have a suitable environment, you can give it a try as well. Looking forward to your new article~
After version 6.2, it has been separated from PD and requires a separate configuration for the dashboard.
It should be possible, looking forward to your sharing.
This should be an extension of another issue. Currently, it seems that the official configuration file has added the tidb-dashboard component, but unfortunately, it is not included in the offline package. @Billmay It seems that this was probably missed when packaging the tiup offline package.
In the previous question, that user generated the template file using --full, which included the tidb_dashboard component, but it couldn’t be deployed using the offline deployment method.
Currently, I’m hesitant to upgrade glibc casually as it might crash the OS. We only have one test environment, and there are quite a few tasks towards the end of the year. Once I set up the environment, I’ll definitely share my findings. However, I believe by then, others will have already published their practical articles. 
TiUP standalone deployment of TiDB Dashboard is expected to be supported in v6.6.0.
You can refer to the post by Biaomei: 关于 6.5.0 版本中 TiDB-Dashboard 依赖包版本太高的问题 -
建议&反馈 - TiDB 的问答社区 (asktug.com)
For now, let’s not bother with the high dependency package version issue in the current version and wait until full support is available to study the splitting issue.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.