You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently hosting my own graph-node on AWS EC2, and I've noticed that the IPFS block files are growing incredibly fast, taking up about 100 GB at the moment (while PostgreSQL is using only 28 GB). It seems like the graph-node is just seeding for the IPFS network, and I'd like to figure out how to stop that.
Bug report
I'm currently hosting my own graph-node on AWS EC2, and I've noticed that the IPFS block files are growing incredibly fast, taking up about 100 GB at the moment (while PostgreSQL is using only 28 GB). It seems like the graph-node is just seeding for the IPFS network, and I'd like to figure out how to stop that.
This is my
docker-compose.yml
.Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
OS information
Linux
The text was updated successfully, but these errors were encountered: