-
Notifications
You must be signed in to change notification settings - Fork 501
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
2/4 PD in error state #568
Comments
oh, I should have said 2/4. It seems that PD has recovered now. However, there is still a demo-pd-3 in an error state. Why is that? |
The |
demo-pd-3 join file:
https://transfer.sh/oS8B4/demo-pd-0.log @nolouch PTAL |
pd3 no output? |
Thanks, the |
fixed by tikv/pd#1643, closing. |
We can close this out when we specify a PD version with the bug fix. Next possible fix version will be 3.0.2 |
We've changed the default TiDB version to v3.0.4, shall we close this issue now? @gregwebs |
🎉 |
Using the latest stable release (beta 3), after the cluster has been running for several hours I observe pods in an Error state. The log looks very suspicious that there is a problem with how PD are joining after experiencing a failure.
kubectl logs -p -n tidb180007 demo-pd-3
kubectl logs -p -n tidb180007 demo-pd-1
The text was updated successfully, but these errors were encountered: