Timeout Issue After Updating Zeebe Broker Configuration in Camunda 8.3

Hi Team,

We are using Camunda 8.3 on AWS with Helm Charts. Initially, we encountered issues with the gRPC protocol in our environment, but our platform team resolved them and added certificates to the Zeebe Gateway for secure communication. Our initial Zeebe configuration had 3 brokers, 3 partitions, and 3 replicas, and we were able to process 10 process instances per second.

To better match our use case, we decided to reduce the replication factor to 1 and adjust the number of brokers and partitions. For the new deployment, we deleted the existing deployment along with the related PVCs. After deploying with the new configuration, I can retrieve the topology and successfully deploy BPMN and DMN files using the C# Zeebe client methods.

However, when I make requests to the Zeebe broker to process a record, I’m encountering a timeout between brokers after about a minute. I’m unable to determine the cause of this issue. Could someone please take a look at this?

Thank you!

Can anyone help me with this @camunda

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.