Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Back off on errors other than GRPC 8 (Backpressure) #366

Open
jwulf opened this issue Jan 31, 2025 · 0 comments
Open

Back off on errors other than GRPC 8 (Backpressure) #366

jwulf opened this issue Jan 31, 2025 · 0 comments
Assignees

Comments

@jwulf
Copy link
Member

jwulf commented Jan 31, 2025

Other errors, such as 16 UNAUTHENTICATED, should also cause a backoff. There is no way immediate retries of an unauthed request do anything other than DOS the gateway.

This should be implemented here: https://github.com/camunda/camunda-8-js-sdk/blob/main/src/zeebe/lib/ZBWorkerBase.ts#L511

The question is whether all error conditions should trigger a backoff, or if 16 should just be added to the list.

Intermittent network disruption, or waiting for a gateway to come up are examples where backing off reduces the recovery time of the system, but without protecting a gateway from DOS.

I think in the first instance, I'll add 16 UNAUTHENTICATED to the backoff conditions.

@jwulf jwulf self-assigned this Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant