Open Jorropo opened 2 years ago
What is actionable here? What is the expected behavior?
@guseggert the indexer protocol allows to mark which protocols peers support. We should ensure that peers supports bitswap and only return thoses. (as a parameter in reframe ? filter code done in hydras ? other ? idk).
@guseggert as @Jorropo pointed out - currently kubo and other IPFS implementations expect the DHT to exclusively contain bitswap-dialable peers. This is starting to become a problem in more and more places as the Filecoin SP community is pushing more and more data into the indexer. Effectively the hydra is now actively poisoning the DHT, filling it up with records that will not respond to requests.
We need to fix this ASAP, it's a structural network concern at this stage.
cc @biglep @aschmahmann @mikeal
2022-08-12 triage conversation: this isn't as bad as it seems because:
What needs to happen:
There's a potential parallel track where reframe findProviders will take hints of what provider records the client wants (e.g., bitswap only). That's a future optimization that we don't have a backlog item right now but also aren't planning to prioritize.