The first deployment of the TiDB cluster involves inconsistent ownership groups of the created deploy_dir and data_dir.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
- What did you do?
When deploying and starting the cluster for the first time, it fails with the error "[PD:etcd:ErrStartEtcd]cannot access data directory". The owner group of the upper parent directory is the tidb user, but the owner group of the subdirectory deploy_dir is the tidb user, and the owner group of the subdirectory data_dir is the root user.
After destroying the cluster and deploying it again, start the cluster normally. (no changes made)
-
What did you expect to see?
Cluster started successfully -
What did you see instead?
The cluster failed to start. The owner group of the created data_dir is the root user.
- What version of TiUP are you using (
tiup --version)?
1.16.0 tiup
Go Version: go1.21.11
Git Ref: v1.16.0
GitHash: e543145831d44a863366ff8c379d25980730bbd1
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
Start by reproducing the first TiUP cluster deployment with version 1.16.0, then inspect the deployment and cluster-start entry points around creation of deploy_dir and data_dir. Done means the first deployment starts successfully and the created directories have consistent ownership without requiring destruction and redeployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100