ipfs/kubo

Push CID to DHT when publishing a name

Open

#7,487 opened on Jun 17, 2020

View on GitHub
 (4 comments) (1 reaction) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
P2effort/hoursexp/intermediatehelp wantedkind/enhancementstatus/ready

Description

I investigated a bit a performance issue - where it takes quite a long time before data behind an IPNS record can be resolved via the DHT.

It seems that the newly added content is too large, so there's a large backlog of newly added pins and MFS data on the node, that it is able to push the CID for the name record in a reasonable amount of time.

A dedicated ipfs dht provide <CID> before running ipfs name publish --key=<keyID> <CID> solved this issue for me.

So there seems to be an improvement opportunity:

If the CID which should be published as a name record is still somewhere on the queue for sending it to the DHT as provider IPFS could give this CID priority, that it will be the next CID to be published. This way ipfs makes rue that the new name record will be resolvable via DHT.

Contributor guide

Tech stack
go
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingIPFS conceptsDHT knowledgeKubo codebase familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the DHT provider queue in Kubo's codebase, likely in the `core/commands/` and `namesys/` directories. Understand how CIDs are queued for providing and implement a mechanism to prioritize the CID being published via `name publish`. The issue suggests that the CID should jump ahead in the queue. Review existing comments and possibly linked issues for further context.