cerc-io/lotus
16
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 27 Wiki Activity

Clarify the purpose of MaxSimultaneousTransfers config

Browse Source 
Clarify the documentation of `MaxSimultaneousTransfers` to state that
the "transfer" refers to multihash syncing only and not the data itself.
This commit is contained in:
Masih H. Derkani 2022-02-03 11:51:01 +00:00
parent ad348c8e2f
commit 235377585d
No known key found for this signature in database
GPG Key ID: B320AFAA5B736DB6
3 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/en/default-lotus-miner-config.toml
View File

@ -285,8 +285,8 @@
# env var: LOTUS_INDEXERPROVIDER_ANNOUNCEADDRESSES
#AnnounceAddresses = []
# The maximum number of simultaneous data transfers between the indexers
# and the indexer provider
# The maximum number of simultaneous requests syncing the list of advertised multihashes between
# the indexers and the index provider.
#
# type: uint64
# env var: LOTUS_INDEXERPROVIDER_MAXSIMULTANEOUSTRANSFERS

3
node/config/doc_gen.go
View File

@ -378,8 +378,7 @@ Format: multiaddress`,
Name: "MaxSimultaneousTransfers",
Type: "uint64",
Comment: `The maximum number of simultaneous data transfers between the indexers
and the indexer provider`,
Comment: `The maximum number of simultaneous requests syncing the list of advertised multihashes between the indexers and the index provider.`,
},
},
"Libp2p": []DocField{

4
node/config/types.go
View File

@ -173,8 +173,8 @@ type IndexerProviderConfig struct {
// Format: multiaddress
AnnounceAddresses []string
// The maximum number of simultaneous data transfers between the indexers
// and the indexer provider
// The maximum number of simultaneous requests syncing the list of advertised multihashes
// between the indexers and the index provider.
MaxSimultaneousTransfers uint64
}