Elli Kotoula: Hello guys! We have dockerised zeebe with image versions: camunda/zeebe:0.25.1 and camunda/operate:0.25.0 . When we create workers it seems that at the beginning they consume very quickly the messages and after a while they consume messages slower than they receive the requests and as a result many active instances remain in the queue. We get the error: ERROR: Grpc Stream Error: 8 RESOURCE_EXHAUSTED: Expected to activate jobs of type 'workerHandler', but no jobs available and at least one broker returned 'RESOURCE_EXHAUSTED'. Please try again later. . We have used long polling too, but the same error occurs as well. Do you have any idea? Thank you!
kristoffer.bakkejord: By default the Zeebe backoff rules are a bit strict.
See the documentation here: https://docs.camunda.io/docs/0.26/product-manuals/zeebe/deployment-guide/operations/backpressure/#backpressure-tuning
Elli Kotoula: Ok thank you! Is there any example on how we can use backpressure with docker? I would really appreciate it.
kristoffer.bakkejord: As mentioned in <https://camunda-cloud.slack.com/archives/C6WGNHV2A/p1621548224021000?thread_ts=1621515977.013400&cid=C6WGNHV2A|another thread> It’s recommended to set up Prometheus/Grafana to monitor the state of the zeebe cluster.
kristoffer.bakkejord: You can try changing the backpressure algorithm to one listed here
Elli Kotoula: Thank you, I will check the above and try it.
Note: This post was generated by Slack Archivist from a conversation in the Zeebe Slack, a source of valuable discussions on Zeebe (get an invite). Someone in the Slack thought this was worth sharing!
If this post answered a question for you, hit the Like button - we use that to assess which posts to put into docs.