# AWX control pod restart

**URL:** <https://forum.ansible.com/t/awx-control-pod-restart/37370>\
**Category:** AWX Project\
**Tags:** azure, awx, ee\
**Created:** [November 20, 2022, 10:34am UTC](https://forum.ansible.com/t/awx-control-pod-restart/37370 "2022-11-20T10:34:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mani3887](https://avatars.discourse-cdn.com/v4/letter/m/9f8e36/32.png) [@mani3887](https://forum.ansible.com/u/mani3887)\
**Post date:** [November 20, 2022, 10:34am UTC](https://forum.ansible.com/t/awx-control-pod-restart/37370/1 "2022-11-20T10:34:20Z")

</div>

Hi Folks,

Thanks for the AWX office hours. I went through the recording and other videos listed in Ansible AWX community. The videos were helpful in giving clarity of some of the designs followed in AWX. We are running AWX version 21.4 in AKS cluster. At our application we observe a below issue:

When AWX control pod restarts, it seems like it abandons the previous control pod’s AWX EE pods, i.e. it seems like the new AWX control pod does not detect the already running AWX EE pods. Would it help if we move the redis cache from in-memory to cloud(azure redis cache)? Is there support for this in AWX? If there is, if we have multiple AWX replicas, and all having redis cache in cloud, would there be sync issues across the AWX instances? I understand that if we did move to a cloud-based solution from in-memory, the latency would be higher.

Thanks in advance.

Regards,  
Mani

---

<div class="post-metadata">

**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\
**Post date:** [December 2, 2022, 6:55pm UTC](https://forum.ansible.com/t/awx-control-pod-restart/37370/2 "2022-12-02T18:55:16Z")

</div>

You mean the job pods that are running? If the AWX services are restarted, those jobs will be marked as failed. Under what conditions is the awx control pod restarting for you? upgrades?

AWX Team