Symptoms
When an Azure Synapse process runs a RunPipelineRequest, and the request receives a Read timeout, RMJ is retriggering the RunPipelineRequest Creating 2 pipelines from a single RMJ process.
This is not expected; if we ever receive a Read Timeout exception, we need to error the RMJ process. Because the Read Timeout does not mean the process failed in Azure, but that they didn't reply within the expected time.
Cause
This is being caused at the code level; the request is made to be re-triggered in the Synapse connector.
Steps to reproduce: There's no way to reproduce it; we depend on Synapse timing out on replying.
Workaround
The Connection and Socket timeouts can be modified according to the documentation
With higher timeouts, this issue is less likely to happen, but it will change the behavior.
Affected version
Azure Synapse 1.0.0.2 and lower
Resolution
ETA Azure Synapse 1.0.0.3 / 2026 - Q1
Reference
Error
INFO 2025-07-19 12:00:03,341 GMT [Redwood Job Thread Pool: ENERGIZER_PRD.Synapse_ProcessServer.ServiceForRedwood_AzureSynapse worker 0-Executor 5265296] job.SYNW_MDL_XTEL_MasterData.62668855758 - Running pipeline MO_PopulatePipelineQueue_KantarInbound ERROR 2025-07-19 12:00:19,597 GMT [Redwood Job Thread Pool: ENERGIZER_PRD.Synapse_ProcessServer.ServiceForRedwood_AzureSynapse worker 0-Executor 5265296] job.SYNW_MDL_XTEL_MasterData.62668855758 - POST https://azsw-prd-mdl-001.dev.azuresynapse.net/pipelines/MO_PopulatePipelineQueue_KantarInbound/createRun?api-version=2020-12-01 request failed java.net.SocketTimeoutException: Read timed out ... WARN 2025-07-19 12:00:29,598 GMT [Redwood Job Thread Pool: ENERGIZER_PRD.Synapse_ProcessServer.ServiceForRedwood_AzureSynapse worker 0-Executor 5265296] job.SYNW_MDL_XTEL_MasterData.62668855758 - POST https://azsw-prd-mdl-001.dev.azuresynapse.net/pipelines/MO_PopulatePipelineQueue_KantarInbound/createRun?api-version=2020-12-01 (retry = 1/10) INFO 2025-07-19 12:00:30,499 GMT [Redwood Job Thread Pool: ENERGIZER_PRD.Synapse_ProcessServer.ServiceForRedwood_AzureSynapse worker 0-Executor 5265296] job.SYNW_MDL_XTEL_MasterData.62668855758 - Pipeline runId: b9a963be-3b21-4408-95ac-679e5df63cc8
Comments
0 comments
Please sign in to leave a comment.