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
Copy file name to clipboardExpand all lines: docs/changelogs/v0.35.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ This release was brought to you by the [Shipyard](http://ipshipyard.com/) team.
10
10
11
11
-[Overview](#overview)
12
12
-[🔦 Highlights](#-highlights)
13
+
-[Dedicated `Reprovider.Strategy` for MFS](#dedicated-reproviderstrategy-for-mfs)
13
14
-[📦️ Important dependency updates](#-important-dependency-updates)
14
15
-[📝 Changelog](#-changelog)
15
16
-[👨👩👧👦 Contributors](#-contributors)
@@ -18,6 +19,16 @@ This release was brought to you by the [Shipyard](http://ipshipyard.com/) team.
18
19
19
20
### 🔦 Highlights
20
21
22
+
#### Dedicated `Reprovider.Strategy` for MFS
23
+
24
+
The [Mutable File System (MFS)](https://docs.ipfs.tech/concepts/glossary/#mfs) in Kubo is a UnixFS filesystem managed with [`ipfs files`](https://docs.ipfs.tech/reference/kubo/cli/#ipfs-files) commands. It supports familiar file operations like cp and mv within a folder-tree structure, automatically updating a MerkleDAG and a "root CID" that reflects the current MFS state. Files in MFS are protected from garbage collection, offering a simpler alternative to `ipfs pin`. This makes it a popular choice for tools like [IPFS Desktop](https://docs.ipfs.tech/install/ipfs-desktop/) and the [WebUI](https://github.com/ipfs/ipfs-webui/#readme).
25
+
26
+
Previously, the `pinned` reprovider strategy required manual pin management: each dataset update meant pinning the new version and unpinning the old one. Now, new strategies—`mfs` and `pinned+mfs`—let users limit announcements to data explicitly placed in MFS. This simplifies updating datasets and announcing only the latest version to the Amino DHT.
27
+
28
+
Users relying on the `pinned` strategy can switch to `pinned+mfs` and use MFS alone to manage updates and announcements, eliminating the need for manual pinning and unpinning. We hope this makes it easier to publish just the data that matters to you.
29
+
30
+
See [`Reprovider.Strategy`](https://github.com/ipfs/kubo/blob/master/docs/config.md#reproviderstrategy) for more details.
31
+
21
32
##### `Routing.IgnoreProviders`
22
33
23
34
This new option allows ignoring specific peer IDs when returned by the content
Copy file name to clipboardExpand all lines: docs/config.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1587,21 +1587,26 @@ Type: `optionalDuration` (unset for the default)
1587
1587
Tells reprovider what should be announced. Valid strategies are:
1588
1588
1589
1589
-`"all"` - announce all CIDs of stored blocks
1590
-
- Order: root blocks of direct and recursive pins are announced first, then the rest of blockstore
1591
-
-`"pinned"` - only announce pinned CIDs recursively (both roots and child blocks)
1590
+
- Order: root blocks of direct and recursive pins and MFS root are announced first, then the rest of blockstore
1591
+
-`"pinned"` - only announce recursively pinned CIDs (`ipfs pin add -r`, both roots and child blocks)
1592
1592
- Order: root blocks of direct and recursive pins are announced first, then the child blocks of recursive pins
1593
-
-`"roots"` - only announce the root block of explicitly pinned CIDs
1593
+
-`"roots"` - only announce the root block of explicitly pinned CIDs (`ipfs pin add`)
1594
1594
-**⚠️ BE CAREFUL:** node with `roots` strategy will not announce child blocks.
1595
1595
It makes sense only for use cases where the entire DAG is fetched in full,
1596
1596
and a graceful resume does not have to be guaranteed: the lack of child
1597
1597
announcements means an interrupted retrieval won't be able to find
1598
1598
providers for the missing block in the middle of a file, unless the peer
1599
1599
happens to already be connected to a provider and ask for child CID over
1600
1600
bitswap.
1601
+
-`"mfs"` - announce only the local CIDs that are part of the MFS (`ipfs files`)
1602
+
- Note: MFS is lazy-loaded. Only the MFS blocks present in local datastore are announced.
1603
+
-`"pinned+mfs"` - a combination of the `pinned` and `mfs` strategies.
1604
+
-**ℹ️ NOTE:** This is the suggested strategy for users who run without GC and don't want to provide everything in cache.
1605
+
- Order: first `pinned` and then the locally available part of `mfs`.
1601
1606
-`"flat"` - same as `all`, announce all CIDs of stored blocks, but without prioritizing anything.
1602
1607
1603
1608
> [!IMPORTANT]
1604
-
> Reproviding larger pinsets using the `all`, `pinned`, or `roots` strategies requires additional memory, with an estimated ~1 GiB of RAM per 20 million items for reproviding to the Amino DHT.
1609
+
> Reproviding larger pinsets using the `all`, `mfs`, `pinned`,`pinned+mfs` or `roots` strategies requires additional memory, with an estimated ~1 GiB of RAM per 20 million items for reproviding to the Amino DHT.
1605
1610
> This is due to the use of a buffered provider, which avoids holding a lock on the entire pinset during the reprovide cycle.
1606
1611
> The `flat` strategy can be used to lower memory requirements, but only recommended if memory utilization is too high, prioritization of pins is not necessary, and it is acceptable to announce every block cached in the local repository.
0 commit comments