graphprotocol / graphprotocol/graph-node
[Feature] Add a `graphman database check`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Description
We should add a graphman command that checks that all shards can talk to each other in the way that we need. For each shard, it should access the primary_public (e.g., by running select count(*) from primary_public.chains) and the shard_.._subgraphs.subgraph tables for all the other shards and print any error it encounters.
This would be very useful to ensure that everything is in place for sharding to work as there are many ways in which this can go wrong (firewalls, pg_hba.conf, ..)
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out
- Tick this box if you plan on implementing this feature yourself.
- I have searched the issue tracker to make sure this issue is not a duplicate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing graphman database commands and the code that manages shard connections. Determine how to access primary_public and each shard's subgraph table, then verify the command reports every connection error and succeeds when all checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, rust
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100