We have been using Subquery indexing service for xdc subgraph. They had some problems with it, we are following up with them.
Initially we were running graph node in our own servers. https://github.com/XinFinOrg/XDC-Graph-Node
We had some issues:
When deploying changes to the codebase or adding new contracts, it syncs from starting and all data is only available when it syncs till latest block. As our protocol have been for a long time in XDC network, for a very long period we experienced data outage. Switching to Subquery solved this as indexer services serves from previous release until latest release is synced to latest block.
Computing and Storage resources:
We need some suggestion on what should be the server configuration for an ec2 instance in Amazon AWS. In t2.medium instance, the indexing process was slow.
In general we don't run indexer on our own, we use thegraph, goldsky etc.
Any suggestions to fix this ?
Discussion (2)
For the first issue, it's the design of graph-node, but you can use
startBlockin subgraph to save time according to the document of the graph.For the hardware requirements, please query with index software provider, or refer to their document.
Hello @pranjal_prashar_be5b9585f
We hope that the above issue is resolved, if the issue still persists then please let us know about it so that the team can resolve it on priority. It will be grateful to get an update within 72 hours or else it will be considered resolved.
Thank You.