Skip to content

Commit

Permalink
rephrasing Tue Nov 21 19:52:44 CET 2023
Browse files Browse the repository at this point in the history
  • Loading branch information
Julien Noël committed Nov 21, 2023
1 parent 7d435f3 commit b96006f
Show file tree
Hide file tree
Showing 2 changed files with 24 additions and 14 deletions.
2 changes: 1 addition & 1 deletion content/en/storage-providers/manage/blacklist/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ toc: true

Access `Storage` > `Blacklist`.

When an address is blacklisting any deals form that address are automatically deleted without being evaluated. The client is informed by an unauthorized message.
When an address is blacklisted any deals form that address are automatically deleted without being evaluated. The client is informed by an unauthorized message.

## Blacklist new address

Expand Down
36 changes: 23 additions & 13 deletions content/en/storage-providers/manage/others/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,42 +13,52 @@ toc: true

## Maintenance mode

Maintenance mode provides an easy and fast to immediately stop accepting any types of deals both storage and retrieval deals (graphsync / bitswap / http).

Activation of maintenance mode results in the automatic rejection of all deals received by a miner.
This option is applicable to both storage and retrieval deals.

To toggle maintenance mode on or off, utilize the switch located on the top navigation bar.

{{< img src="maintenance-mode.png" alt="Enable and disable the maintenance mode" >}}

## Global limits
## Limits

Limits serve as a protective measure for the miner, preventing the sealing pipeline to be overloaded.

Global limits serve as a protective measure for the miner, preventing an influx of deals within a short timeframe.
These limits are applied without regard to the customer's status, whether registered or not.
Limits are implemented at 2 levels :
- Global limits apply accross all clients. Any accepted deals from any clients will be counted in the same bucket. If that bucket exceed the limit, nor more deals are accepted. - Client limits only apply to that specific client. All deals of that specific client are counted to evaluated if new deals should be accepted. When a limit is set on a client; both the client and the global rate limit are evaluated.

In the event these limits are exceeded, all deals processed by CIDgravity will be rejected.
{{< alert icon="warning" >}}
The global limits should be set to the maximum ingestion capacity of the miner.
{{< /alert >}}

These limits are applied to any clients registred and unknown.

Any new deals are rejected until the limit of accepted deals is exceeded.

For configuration of the global limits, navigate to the `Settings` section, specifically under `Global rate limits`.

{{< img src="global-rate-limits.png" alt="Configure the global rate limits" >}}

Various rate limits can be configured:

- **Number of storage deals per hour**: sets the maximum allowable number of storage deals
- **Cumulative storage deal size per hour**: defines the maximum cumulative size of all deals that can be received within an hour
- **Retrieval deals per hour**: establishes the maximum allowable number of retrieval deals
- **Number of storage deals per hour**: The maximum number of storage deals accepted over the last 60 minutes, across all clients.
- **Cumulative storage deal size per hour**: The maximum cumulative storage deal size (GiB) accepted over the last 60 minutes.
- **Retrieval deals per hour**: The maximum number of graphsync retrieval deals accepted over the last 60 minutes, across all clients.

{{< alert icon="warning" >}}
All limits are calculated over a rolling hour, ensuring a dynamic and continuous evaluation of the specified constraints within the preceding 60-minute timeframe.
Limits are calculated over the last 60 minutes and reevaluated in real time o each new proposal received.
{{< /alert >}}

{{< alert icon="tip" >}}
To signify no specified limits, you can enter 0, indicating an unrestricted or unlimited setting for the corresponding parameter.
Set a limit to 0 to disable it (unlimited).
{{< /alert >}}

## Start epoch sealing buffer

The start epoch sealing buffer setting allow to reject deals if a deal start epoch is under a specific requirement
This option will filter incomming storage deals to give time for sealing of sector with deal.
The start epoch sealing buffer setting allow to reject deals if a deal start epoch is under a specific requirement.

This feature will reject any deals that doesn't provide enough time to be processed.

To configure the start epoch sealing buffer, navigate to the `Settings` section, specifically under `Start epoch sealing buffer`.

Expand All @@ -61,5 +71,5 @@ The value must be expressed in hours
{{< /alert >}}

{{< alert icon="warning" >}}
It's possible to define start epoch sealing buffer for any registerd clients. To set client specific option, just edit a client
It's possible to define start epoch sealing buffer for any registerd clients. To set client specific option, just edit itt
{{< /alert >}}

0 comments on commit b96006f

Please sign in to comment.