-
Notifications
You must be signed in to change notification settings - Fork 75
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
List all graph node env variables for hedera #700
Comments
This may take some time to figure out, probably after other issues are resolved and the whole thin is stable and can be tested extendedly. |
even when in the docs says that this value defaults to 1000, i've seen is variable, and Hedera-Json-RPC-Relay does have a GRAPH_ETHEREUM_MAX_BLOCK_RANGE_SIZE=1000 |
@AlfredoG87 I recall going through the code a while back and it scales up/down based on failed calls, so |
Indeed the graph-node does scale up and down, but for the times it goes up, it fails. |
@AlfredoG87 let's update https://github.com/hashgraph/hedera-json-rpc-relay/tree/main/tools/subgraph-example#prerequisites section with any custom graph env variables for optimized ingestion. |
Problem
Hedera isn't supported by The Graph's hosted service, so developers looking to deploy their subgraphs will have to setup their own graph node. The
subgraph-example
doesn't list the graph node's env variables optimised for hedera. It would be helpful to anyone looking to set up a graph node to use that list of env variables instead of using their own guesses or the default values.For example
ETHEREUM_POLLING_INTERVAL
defaults to 500ms, however looking at hashscan's blocks the block time seems to be about 2000ms and looking at hedera metrics the time to finality is ~5.45s so perhaps a more suitableETHEREUM_POLLING_INTERVAL
is between 6_000 - 10_000 ms.Another example would be the
GRAPH_ETHEREUM_BLOCK_INGESTOR_MAX_CONCURRENT_JSON_RPC_CALLS_FOR_TXN_RECEIPTS
variable which defaults to 1_000, however, should probably be based on the relay service limits which in the case of Arkhia's Enterprise tier should be 200.Solution
subgraph-example
Alternatives
No response
The text was updated successfully, but these errors were encountered: