introduce MaxStagingDealsGiB - reject new deals if our staging deals area is "full"
This commit is contained in:
@@ -251,6 +251,13 @@ message`,
|
||||
|
||||
Comment: `The maximum collateral that the provider will put up against a deal,
|
||||
as a multiplier of the minimum collateral bound`,
|
||||
},
|
||||
{
|
||||
Name: "MaxStagingDealsGiB",
|
||||
Type: "int64",
|
||||
|
||||
Comment: `The maximum size of staging deals not yet passed to the sealing node,
|
||||
that the markets service can accept`,
|
||||
},
|
||||
{
|
||||
Name: "SimultaneousTransfers",
|
||||
|
||||
@@ -126,7 +126,9 @@ type DealmakingConfig struct {
|
||||
// The maximum collateral that the provider will put up against a deal,
|
||||
// as a multiplier of the minimum collateral bound
|
||||
MaxProviderCollateralMultiplier uint64
|
||||
|
||||
// The maximum size of staging deals not yet passed to the sealing node,
|
||||
// that the markets service can accept
|
||||
MaxStagingDealsGiB int64
|
||||
// The maximum number of parallel online data transfers (storage+retrieval)
|
||||
SimultaneousTransfers uint64
|
||||
|
||||
|
||||
Reference in New Issue
Block a user