Summary
After upgrading Airbyte to version >=0.63.1, encountering ‘rehydrateAndProcessClaimed failed’ error in workload-launcher pod with ‘java.net.SocketException: Operation not permitted’. Manually killing the pod resolves the issue. Syncs fail without workload launcher. Seeking hints for a fix while deploying Airbyte using helm chart.
Question
Hi Airbyte community 
!
I’ve been having a problem since Airbyte version >=0.63.1 with workload-launcher pod: whenever all the application pods are recreated (due to a rolling upgrade or a change in node), my workload-launcher presents this error:
dev.failsafe.FailsafeException: java.net.SocketException: Operation not permitted
at dev.failsafe.SyncExecutionImpl.executeSync(SyncExecutionImpl.java:196) ~[failsafe-3.3.2.jar:3.3.2]
at dev.failsafe.FailsafeExecutor.call(FailsafeExecutor.java:376) ~[failsafe-3.3.2.jar:3.3.2]
at dev.failsafe.FailsafeExecutor.get(FailsafeExecutor.java:112) ~[failsafe-3.3.2.jar:3.3.2]
at io.airbyte.workload.launcher.ClaimedProcessor.getWorkloadList(ClaimedProcessor.kt:111) ~[io.airbyte-airbyte-workload-launcher-0.63.15.jar:?]
at io.airbyte.workload.launcher.ClaimedProcessor.retrieveAndProcess(ClaimedProcessor.kt:60) ~[io.airbyte-airbyte-workload-launcher-0.63.15.jar:?]
at io.airbyte.workload.launcher.StartupApplicationEventListener$onApplicationEvent$1.invoke(StartupApplicationEventListener.kt:37) [io.airbyte-airbyte-workload-launcher-0.63.15.jar:?]
at io.airbyte.workload.launcher.StartupApplicationEventListener$onApplicationEvent$1.invoke(StartupApplicationEventListener.kt:35) [io.airbyte-airbyte-workload-launcher-0.63.15.jar:?]
at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30) [kotlin-stdlib-1.9.24.jar:1.9.24-release-822]```
Usually, if I manually kill the pod, it will resolve the issue. Without the workload launcher, the syncs fail as they can't create syncs.
Do you have any hints on how to fix it? I use the helm chart to deploy it without any drastic changes to the standard.
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1724172889262099) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["error", "workload-launcher", "pod", "upgrade", "java.net.SocketException", "syncs", "helm chart"]
</sub>