This repository was archived by the owner on Apr 8, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 38
Workers do not reconnect after TRANSIENT_FAILURE #152
Comments
Yeah, this is still an issue. It looks like this with DEBUG level logging:
|
Same here. I try to deploy a WorkflowInstance with the zeebe brocker being down:
Then I start the brocker but zeebe-node never reconnect. |
jwulf
added a commit
to jwulf/zeebe-client-node-js
that referenced
this issue
May 6, 2020
Fixed in 0.23.0 |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like workers do not reconnect after a TRANSIENT_FAILURE with the pure JS Grpc implementation.
My hypothesis about this is that the channel goes to TRANSIENT_FAILURE, and it takes another gRPC call before the channel state switches.
In order to deal with this, I am changing the GrpcClient failure logic to wait for 5 seconds on a TRANSIENT_FAILURE, then resolve to reconnected and unblock further operations.
The text was updated successfully, but these errors were encountered: