Expected Behaviour
I'm expecting the connection return to normal after the server drops cause of restart.
Actual Behaviour
I set the following options:
{
shouldRetry: () => true,
retryAttempts: 50,
}
to createClient but the retry mechanism doesn't kicks in.
As I see the process doesn't get to shouldRetryConnectOrThrow so the shouldRetry configuration doesn't get called.
Debug Information
I run Hasura graphql server which throws the following error on Kubernetes pod restart.
Screenshot
Expected Behaviour I'm expecting the connection return to normal after the server drops cause of restart.
Actual Behaviour I set the following options:
to
createClient
but the retry mechanism doesn't kicks in. As I see the process doesn't get toshouldRetryConnectOrThrow
so the shouldRetry configuration doesn't get called.Debug Information I run Hasura graphql server which throws the following error on Kubernetes pod restart.
The socket.onclose function gets called when server restarts without the retry functionality. The event type is
Normal Closure
.If any more information is needed, let me know.