search

graphprotocol / support

Community support for the Hosted Service of The Graph
https://thegraph.com/
10 stars 3 forks source link

Trying again after eth_call RPC call for block #773384 - Arbitrum #100

Closed rafinskipg closed 1 year ago

rafinskipg commented 1 year ago

Do you want to request a feature or report a bug? bug

What is the current behavior? Hello , i have redeployed this graph several times, but it keeps getting stuck at 2.2%. Te graph getting stuck on arbitrum-one at specific block all the time.

https://thegraph.com/hosted-service/subgraph/rafinskipg/castles-arbitrum-v0?selected=logs

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

See the link above

What is the expected behavior?

The indexing should continue

azf20 commented 1 year ago

Hi @rafinskipg it looks like your subgraph is spending a lot of time on eth_calls, that is not recommended for indexing performance. It also seems to still be indexing right now, but it hasn't reached the block you mention. You can get more information about the failure if it fails by following this documentation. Please join our Discord (#hosted-service) for more help with debugging

rafinskipg commented 1 year ago

@azf20

The graph is still blocked, it never passes 2.2% of the indexation image

Could you reopen this issue? It seems like a timeout with the RPC.

I have also been posting under the hosted-service for a couple of days

azf20 commented 1 year ago

👍 Transferred as this isn't a Graph Node bug, it's an issue with the provider on the Hosted Service. The subgraph isn't failing, we are just seeing timeouts on the eth_call so indexing is very slow. @incrypto32 is looking into this

incrypto32 commented 1 year ago

@rafinskipg I'm working with our RPC provider to resolve this issue asap. Their arbitrum nodes seems to be timing out when fetching large onchain metadata

rafinskipg commented 1 year ago

provider to resolve this issue asap. Their arbitrum nodes seems to be timing out when fetching large onchain metadata

thank you for the response @azf20 and @incrypto32

I have been thinking if there's a way i can do the graph less dependant on eth_calls but i don't see much of a solution. There's another method in the contract called traitsOf that returns a JSON and i could probably use that but i have to figure out how to parse and access the data correctly using assemblyscript.

The source code for the graph: https://github.com/CastleDAO/subgraphs/tree/master/castledao-castles-arbitrum

incrypto32 commented 1 year ago

Closing as this issue is resolved now