# Deadlock on SG/FLX & ES 9.3.x during configuration **URL:** \ **Category:** Search Guard\ **Created:** [May 4, 2026, 3:15pm UTC](https://forum.search-guard.com/t/deadlock-on-sg-flx-es-9-3-x-during-configuration/5029 "2026-05-04T15:15:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![issac.garcia](https://avatars.discourse-cdn.com/v4/letter/i/9dc877/32.png) [@issac.garcia](https://forum.search-guard.com/u/issac.garcia)\ **Post date:** [May 4, 2026, 3:15pm UTC](https://forum.search-guard.com/t/deadlock-on-sg-flx-es-9-3-x-during-configuration/5029/1 "2026-05-04T15:15:49Z")
**Elasticsearch version: 9.3** **Describe the issue:** Running `sgctl update-config` against a two-node ES 9.3.3 + SG FLX 4.1.10 cluster hangs indefinitely. If the pool size is 1, the ES management thread on the master node blocks inside `ConfigUpdateAction.nodeOperation()` and never completes. The problem does not happen on ES 9.2 neither on ES 8.19; the root cause is an ES 9.3 behaviour change: `auto_put_mapping` is now dispatched to the MANAGEMENT thread pool. In earlier versions it ran on a different pool, so the deadlock did not occur. **Steps to reproduce:** 1. See attached file & README **Expected behavior:** No sgctl hangs **Provide configuration:** In attached file [searchguard-es-9\_3-deadlock.zip](https://forum.search-guard.com/uploads/short-url/sJnaTMg12a972ukn2jbOsN2LY0m.zip) (6.7 KB) ---
**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/pablo/32/1443_2.png) [@pablo](https://forum.search-guard.com/u/pablo)\ **Post date:** [May 6, 2026, 5:36pm UTC](https://forum.search-guard.com/t/deadlock-on-sg-flx-es-9-3-x-during-configuration/5029/2 "2026-05-06T17:36:09Z")
@issac.garcia Which versions of SG plugin did you test with 9.2 and 8.19? Also what where exact ELK tested versions? ---
**Author:** ![issac.garcia](https://avatars.discourse-cdn.com/v4/letter/i/9dc877/32.png) [@issac.garcia](https://forum.search-guard.com/u/issac.garcia)\ **Post date:** [May 6, 2026, 6:12pm UTC](https://forum.search-guard.com/t/deadlock-on-sg-flx-es-9-3-x-during-configuration/5029/3 "2026-05-06T18:12:17Z")
Hi @pablo For 9.2 I tested with 4.0.1-es-9.2.6, for 8.19 I tested with 4.0.1-es-8.19.13 In those two it worked, In 4.1.0-es-9.3.3 there is the deadlock issue We discover the deadlock in an integration test environment, in the attached file you can see how to reproduce ---
**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/pablo/32/1443_2.png) [@pablo](https://forum.search-guard.com/u/pablo)\ **Post date:** [May 6, 2026, 6:30pm UTC](https://forum.search-guard.com/t/deadlock-on-sg-flx-es-9-3-x-during-configuration/5029/4 "2026-05-06T18:30:46Z")
Thank you @issac.garcia for sharing the info. Could you tell me why you need to set the node.processors to 1? Is it for testing or you have limited resources? ---
**Author:** ![issac.garcia](https://avatars.discourse-cdn.com/v4/letter/i/9dc877/32.png) [@issac.garcia](https://forum.search-guard.com/u/issac.garcia)\ **Post date:** [May 6, 2026, 7:11pm UTC](https://forum.search-guard.com/t/deadlock-on-sg-flx-es-9-3-x-during-configuration/5029/5 "2026-05-06T19:11:07Z")
I don’t need to set the node to 1, our testing cluster was using 1 by default when we discover the deadlock. It took us a while to understand the issue because it didn’t happen on previous ES versions. We change it and now we don’t have any problem. I just share what we found with you guys to improve your software ---
**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/pablo/32/1443_2.png) [@pablo](https://forum.search-guard.com/u/pablo)\ **Post date:** [May 6, 2026, 7:19pm UTC](https://forum.search-guard.com/t/deadlock-on-sg-flx-es-9-3-x-during-configuration/5029/6 "2026-05-06T19:19:47Z")
@issac.garcia Thank you for sharing your findings. We will investigate it further. ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/system/32/1870_2.png) [@system](https://forum.search-guard.com/u/system)\ **Post date:** [May 27, 2026, 7:20pm UTC](https://forum.search-guard.com/t/deadlock-on-sg-flx-es-9-3-x-during-configuration/5029/7 "2026-05-27T19:20:26Z")
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.