ipfs / ipfs/kubo

Garbage Collection minimum data lifetime

Open
#8,412 1 comment 0 reactions 0 assignees View on GitHub
kind/enhancement P3
Dominant language
Go
Stars
17.1k
Forks
3.2k
Avg merge
3d 18h
Merged PRs (30d)
11

Description

### Checklist

- [X] My issue is specific & actionable.
- [X] I am not suggesting a protocol enhancement.
- [X] I have searched on the [issue tracker](https://github.com/ipfs/go-ipfs/issues?q=is%3Aissue) for my issue.

### Description

In #8103 we saw users attempting to pin "large" data sets (in this case, 90GiB) reach a hangup during the pinning process.

If the size of the dataset you're attempting to pin is larger then GCThreshold, the chunks will be *immediately* garbage collected when ctl+c'ing or terminating the pin. This defeats the purpose of IPFS as users should be able to "resume" downloading chunks from where they left off if pinning is interrupted.

A simple solution to this may be to preserve pinned chunks for a minimum amount of time? 24 hours since being received, 48 hours since being received, etc. This would give users the opportunity to "resume" a failed pin.

#8413 is another alternative strategy to fix this (warning users on ipfs pin)
#3121 seems to be another alternative strategy for this (best effort pins)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.