【紧急！！！】k8s pd启动失败（非tiup）

[atidat]

还是聚焦在 etcd 那块吧。crash 的 Log 输出这些栈后就挂掉了。所以切入点应该是 选主 这方便

[2022/08/26 02:03:13.164 +00:00] [INFO] [stream.go:250] ["set message encoder"] [from=caab82c67f3f4ad1] [to=caab82c67f3f4ad1] [stream-type="stream MsgApp v2"]
[2022/08/26 02:03:13.164 +00:00] [WARN] [stream.go:277] ["established TCP streaming connection with remote peer"] [stream-writer-type="stream MsgApp v2"] [local-member-id=caab82c67f3f4ad1] [remote-peer-id=6b27cfc0d7490063]
[2022/08/26 02:03:13.177 +00:00] [ERROR] [etcdutil.go:70] ["failed to get cluster from remote"] [error="[PD:etcd:ErrEtcdGetCluster]could not retrieve cluster information from the given URLs"]
2022/08/26 02:03:13.177 log.go:85: [warning] etcdserver: [could not get cluster response from http://basic-pd-1.basic-pd-peer.tidb-cluster.svc:2380: Get "http://basic-pd-1.basic-pd-peer.tidb-cluster.svc:2380/members": dial tcp 10.0.3.33:2380: connect: connection refused]
[2022/08/26 02:03:13.390 +00:00] [PANIC] [cluster.go:460] ["failed to update; member unknown"] [cluster-id=d9e392fb342bfa96] [local-member-id=caab82c67f3f4ad1] [unknown-remote-peer-id=2b86c59db64a77fc]
panic: failed to update; member unknown
goroutine 418 [running]:
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc0008260c0, 0xc000826000, 0x3, 0x3)
        /nfs/cache/mod/go.uber.org/zap@v1.16.0/zapcore/entry.go:234 +0x58d
go.uber.org/zap.(*Logger).Panic(0xc0000f64e0, 0x2759a56, 0x20, 0xc000826000, 0x3, 0x3)
        /nfs/cache/mod/go.uber.org/zap@v1.16.0/logger.go:226 +0x85
...

[wuxiangdong]

目前看只有basi-pd-2这个pod是可用的，basi-pd-1这个pod没起来，所以会报 http://basic-pd-1.basic-pd-peer.tidb-cluster.svc:2380这个错误。。。

[atidat]

根据 log 看，pd-2是第一个启动的 pd，pd-1其次加入集群，pd-0最后加入集群。