Skip to content
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

JSON-RPC call reassign_subgraph in graph-node fails if a deployment has been copied #4394

Closed
lutter opened this issue Feb 23, 2023 · 0 comments · Fixed by #4395
Closed

JSON-RPC call reassign_subgraph in graph-node fails if a deployment has been copied #4394

lutter opened this issue Feb 23, 2023 · 0 comments · Fixed by #4395

Comments

@lutter
Copy link
Collaborator

lutter commented Feb 23, 2023

When a deployment has been copied, the IPFS hash does not identify the deployment uniquely any more, and there will be two (or more) deployments with the same hash. graph-node's JSON-RPC reassign_subgraph request fails because a lookup of that IPFS hash returns multiple deployments.

The call handler should be changed so that reassign_subgraph always changes the active copy if there are multiple copies of a deployment.

On the network, this issue causes the indexer-agent to get stuck since it tries to reassign subgraphs

lutter added a commit that referenced this issue Feb 23, 2023
The reassign_subgraph JSON-RPC call will fail if a deployment exists in
multiple shards. To disambiguate that, change the call so that it only
affects the active deployment.

Fixes #4394
lutter added a commit that referenced this issue Feb 24, 2023
The reassign_subgraph JSON-RPC call will fail if a deployment exists in
multiple shards. To disambiguate that, change the call so that it only
affects the active deployment.

Fixes #4394
lutter added a commit that referenced this issue Feb 24, 2023
The reassign_subgraph JSON-RPC call will fail if a deployment exists in
multiple shards. To disambiguate that, change the call so that it only
affects the active deployment.

Fixes #4394
@lutter lutter closed this as completed in cc0f2d3 Feb 24, 2023
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 a pull request may close this issue.

1 participant