Investigate DHT put issue (go-libp2p-kad-dht)

[laser]

Split out from @whyrusleeping 's original catch-all issue.

Description

Address issues described here.

Acceptance criteria

TBD

Risks + pitfalls

TBD

Where to begin

TBD

[raulk]

@whyrusleeping @laser could you clarify how you use this feature? From what we understood, FC only uses peer routing at the moment.

cc/ @anacrolix

[whyrusleeping]

@raulk its not so much the DHT put, but the issues that were plaguing it. I think that the dial issue you fixed recently might have been the root cause actually.

[raulk]

@whyrusleeping that makes sense. Puts make lots of dials to lookup the K=20 closest peers to the key, then sends PutValue RPCs to them. If the dialer was stalling, it would somewhat explain the behaviour observed here.

Do we want to close this issue and reopen if we notice it again?

[whyrusleeping]

Yeah, let's close for now. Hopefully its fixed :)