Skip to content

Increase hs client timeout to 2 min - #213

Merged
JonoPrest merged 1 commit into
mainfrom
jp/increase-client-timeout
Sep 18, 2024
Merged

Increase hs client timeout to 2 min#213
JonoPrest merged 1 commit into
mainfrom
jp/increase-client-timeout

Conversation

@JonoPrest

Copy link
Copy Markdown
Collaborator

Closes #212

@JonoPrest
JonoPrest requested a review from DZakh September 18, 2024 08:04
url,
enableChecksumAddresses: true,
bearerToken: Env.envioApiToken->Belt.Option.getWithDefault(defaultToken),
httpReqTimeoutMillis: Env.hyperSyncClientTimeoutMillis->Belt.Option.getWithDefault(120_000),

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default is 30s in the client

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we pass this to the HyperFuel client as well?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Possibly, I've never seen this issue TBH until trying this configuration of an indexer. There is something to do with decompressing the transaction input in the client that takes super long. HyperSync should never take longer than 5s per query. The rest of the time is either in the network or in the local operations. A timeout and retry makes sense if it's network latency but definitely needs to be increased if it's deterministically hitting the timeout.

@JonoPrest
JonoPrest merged commit 0f7b114 into main Sep 18, 2024
@JonoPrest
JonoPrest deleted the jp/increase-client-timeout branch September 18, 2024 08:13
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

Successfully merging this pull request may close these issues.

HyperSync Client Times Out on large queries with transaction input

2 participants