# User pod stuck in Terminating status when a node goes down

**URL:** <https://discourse.jupyter.org/t/user-pod-stuck-in-terminating-status-when-a-node-goes-down/1958>\
**Category:** Zero to JupyterHub on Kubernetes\
**Created:** [August 21, 2019, 7:51pm UTC](https://discourse.jupyter.org/t/user-pod-stuck-in-terminating-status-when-a-node-goes-down/1958 "2019-08-21T19:51:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![celine168](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/celine168/32/1822_2.png) [@celine168](https://discourse.jupyter.org/u/celine168)\
**Post date:** [August 21, 2019, 7:51pm UTC](https://discourse.jupyter.org/t/user-pod-stuck-in-terminating-status-when-a-node-goes-down/1958/1 "2019-08-21T19:51:46Z")

</div>

We tested our cluster by powering down one of the nodes, which contained a `proxy-xxx` pod and my user pod. The `proxy-xxx` pod restarted right away on another node in the cluster, but the user pod remained `Terminating` without restarting on another node. I could not start a server on my account after logging in because JupyterHub stalled while trying to stop the server (which it couldn’t do since the node was down).

Is this normal behavior? I was under the impression that if a user had a server open and the node goes down, then the user should still be able to access their account without any intervention.