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

config: Fix doc on PreferNewSectorsForDeals; gofmt

Browse Source
This commit is contained in:
Łukasz Magiera 2022-03-17 21:27:10 +01:00
parent 49a6d7ebcc
commit 433e9c351d
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -337,6 +337,7 @@
# env var: LOTUS_SEALING_MAXSEALINGSECTORSFORDEALS # env var: LOTUS_SEALING_MAXSEALINGSECTORSFORDEALS
#MaxSealingSectorsForDeals = 0 #MaxSealingSectorsForDeals = 0
# Prefer creating new sectors even if there are sectors Available for upgrading.
# This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it # This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it
# possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing # possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing
# flow when the volume of storage deals is lower. # flow when the volume of storage deals is lower.

2
itests/sector_make_cc_avail_test.go
View File

@ -74,4 +74,4 @@ func TestMakeAvailable(t *testing.T) {
miner.WaitSectorsProving(ctx, map[abi.SectorNumber]struct{}{ miner.WaitSectorsProving(ctx, map[abi.SectorNumber]struct{}{
CCUpgrade: {}, CCUpgrade: {},
}) })
} }

1
itests/sector_prefer_no_upgrade_test.go
View File

@ -87,4 +87,3 @@ func TestPreferNoUpgrade(t *testing.T) {
}) })
} }
} }

3
node/config/doc_gen.go
View File

@ -726,7 +726,8 @@ Note that setting this number too high in relation to deal ingestion rate may re
Name: "PreferNewSectorsForDeals", Name: "PreferNewSectorsForDeals",
Type: "bool", Type: "bool",
Comment: `This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it Comment: `Prefer creating new sectors even if there are sectors Available for upgrading.
This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it
possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing
flow when the volume of storage deals is lower.`, flow when the volume of storage deals is lower.`,
}, },

3
node/config/types.go
View File

@ -234,8 +234,7 @@ type SealingConfig struct {
// Upper bound on how many sectors can be sealing+upgrading at the same time when creating new sectors with deals (0 = unlimited) // Upper bound on how many sectors can be sealing+upgrading at the same time when creating new sectors with deals (0 = unlimited)
MaxSealingSectorsForDeals uint64 MaxSealingSectorsForDeals uint64
// Prefer creating new sectors even if there are sectors Available for upgrading // Prefer creating new sectors even if there are sectors Available for upgrading.
//
// This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it // This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it
// possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing // possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing
// flow when the volume of storage deals is lower. // flow when the volume of storage deals is lower.