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

“pd-ctl cluster” failed with error "Failed to get the cluster information: [PD:client:ErrClientNoAvailableMember]no available member" #7721

Closed
Lily2025 opened this issue Jan 17, 2024 · 2 comments · Fixed by #7744
Assignees
Labels
severity/moderate type/bug The issue is confirmed as a bug.

Comments

@Lily2025
Copy link

Bug Report

What did you do?

run "pd-ctl cluster"

What did you expect to see?

cmd can success

What did you see instead?

pd-ctl cluster failed with error "Failed to get the cluster information: [PD:client:ErrClientNoAvailableMember]no available member"

What version of PD are you using (pd-server -V)?

./pd-server -V
Release Version: v8.0.0-alpha
Edition: Community
Git Commit Hash: 3a12148
Git Branch: heads/refs/tags/v8.0.0-alpha
UTC Build Time: 2024-01-16 11:36:44
2024-01-17T09:36:16.314+0800

@Lily2025 Lily2025 added the type/bug The issue is confirmed as a bug. label Jan 17, 2024
@Lily2025
Copy link
Author

/type bug
/severity moderate

@Lily2025 Lily2025 changed the title pd-ctl cluster failed with error "Failed to get the cluster information: [PD:client:ErrClientNoAvailableMember]no available member" “pd-ctl cluster” failed with error "Failed to get the cluster information: [PD:client:ErrClientNoAvailableMember]no available member" Jan 17, 2024
@Lily2025
Copy link
Author

/assign HuSharp

ti-chi-bot bot added a commit that referenced this issue Jan 23, 2024
#7744)

close #7721

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/moderate type/bug The issue is confirmed as a bug.
Projects
Development

Successfully merging a pull request may close this issue.

2 participants