Explanation of 0 replication factor
This commit is contained in:
parent
ef8483e30e
commit
7155fa87c3
|
@ -275,6 +275,10 @@ ipfs add, but the result is a fully replicated CID on completion.
|
|||
If you prefer faster adding, add directly to the local IPFS and trigger a
|
||||
cluster "pin add".
|
||||
|
||||
Optional replication-min and replication-max factors can be provided: -1 means
|
||||
"pin everywhere" and 0 means use cluster's default setting (i.e., replication
|
||||
factor set in config). Positive values indicate how many peers should pin this
|
||||
content.
|
||||
`,
|
||||
/*
|
||||
Cluster Add supports handling huge files and sharding the resulting DAG among
|
||||
|
@ -483,8 +487,8 @@ When the request has succeeded, the command returns the status of the CID
|
|||
in the cluster and should be part of the list offered by "pin ls".
|
||||
|
||||
An optional replication factor can be provided: -1 means "pin everywhere"
|
||||
and 0 means use cluster's default setting. Positive values indicate how many
|
||||
peers should pin this content.
|
||||
and 0 means use cluster's default setting (i.e., replication factor set in
|
||||
config). Positive values indicate how many peers should pin this content.
|
||||
|
||||
An optional allocations argument can be provided, allocations should be a
|
||||
comma-separated list of peer IDs on which we want to pin. Peers in allocations
|
||||
|
|
2
go.mod
2
go.mod
|
@ -69,6 +69,8 @@ require (
|
|||
github.com/libp2p/go-ws-transport v0.1.0
|
||||
github.com/mattn/go-isatty v0.0.9 // indirect
|
||||
github.com/miekg/dns v1.1.16 // indirect
|
||||
github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd // indirect
|
||||
github.com/modern-go/reflect2 v1.0.1 // indirect
|
||||
github.com/multiformats/go-multiaddr v0.0.4
|
||||
github.com/multiformats/go-multiaddr-dns v0.0.3
|
||||
github.com/multiformats/go-multiaddr-net v0.0.1
|
||||
|
|
Loading…
Reference in New Issue
Block a user