<p>We have been running tidb cluster in k8s. and its working fine since. But suddenly i am getting  following issue only in new statsfull pods <code>tidb-tidb-1</code> after scaling tidb-tidb statsfulset. Interestingly tidb-tidb-2 is running. All others pd and tikv pods are also running fine.I have checked the pd url which is not reachable from problematic pods but fine for other pods.Can you please help me to solve this issue.</p>
<p><code>tidb-tidb-1 logs:</code></p>
<pre><code>[2021/04/11 16:15:44.526 +00:00] [WARN] [base_client.go:180] [&quot;[pd] failed to get cluster id&quot;] 
[2021/04/11 16:15:48.527 +00:00] [WARN] [base_client.go:180] [&quot;[pd] failed to get cluster id&quot;]  [error=&quot;[PD:client:ErrClientGetMember]error:rpc error: code = DeadlineExceeded desc = latest connection error: connection error: desc = \&quot;transport: Error while dialing dial tcp: i/o timeout\&quot; target:test-tidb-pd:2379 status:CONNECTING

</code></pre>

Taybur Rahman
<ol>
<li>Could you please show namespace information?
kubectl get all -n  -o wide</li>
<li>Please check node information.
<a href="https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-isolation-restriction" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-isolation-restriction</a></li>
<li>Please check the network. If two nodes could ping successful?
transport: Error while dialing dial TCP: i/o timeout</li>
</ol>
