[TiDB Usage Environment] Production Environment / Testing / PoC
System: Ubuntu 18.04
[TiDB Version]
7.5.0
[Reproduction Path] Operations performed that led to the issue
I followed the single-node deployment method from the official website and executed the startup command tiup playground.
[Encountered Issue: Problem Description and Impact]
However, when I stop it by pressing Ctrl+C and then re-execute tiup playground, all the content in MySQL is cleared.
[Attachments: Screenshots/Logs/Monitoring]
When the Playground cluster exits from the command line, it will by default clear all cluster data. If you want to start a Playground cluster where the data is not automatically deleted, you need to specify a cluster tag at startup. After specifying, you can find the data of the cluster in the ~/.tiup/data path. The method to specify a tag when starting the cluster is as follows:
By default, exiting will clear the data. If you want to retain the data, you can follow the method mentioned above. However, it is still recommended to use tiup cluster deploy to deploy a real cluster. tiup playground is generally used for temporary deployments.
TiDB Playground is generally suitable for beginners in databases. If you don’t want the data to be deleted after exiting, add the parameter --tag. It is recommended to set up a single-node hybrid deployment.
Has this issue been resolved?
If it has been resolved, please mark the question as [Marked as Best Answer] so that it can be searchable and help others find the answer more efficiently.
If your issue has not been resolved, please continue to ask and provide feedback on the problems you encountered, including operation prompts or screenshots.
|
username: TiDBer_kMTvTIEv
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: