From c851f389b879a3bdcec4da01a251694bb9626677 Mon Sep 17 00:00:00 2001 From: BrianWu Date: Tue, 3 Dec 2024 13:24:21 +0800 Subject: [PATCH] Add description for sealFailedRetryCount and sealFailedRetryInterval config in smanager --- docs/build-smanager.md | 6 ++++++ website/translated_docs/zh-CN/build-smanager.md | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/docs/build-smanager.md b/docs/build-smanager.md index 9cb0a8d8..ff80e29f 100644 --- a/docs/build-smanager.md +++ b/docs/build-smanager.md @@ -78,6 +78,8 @@ You could check [smanager-config.example.json](https://github.com/crustio/crust- "dataDir": "data", "scheduler": { "minSrdRatio": 30, + "sealFailedRetryCount": 3, + "sealFailedRetryInterval": 3, "strategy": { "dbFilesWeight": 0, "newFilesWeight": 100 @@ -102,6 +104,10 @@ Those config items will be loaded in the sManager configuration setup process. T > For example, if the ratio is 30, your node will start to accept storage order once the ratio of SRD capacity is higher than 30% +- `scheduler.sealFailedRetryCount`: retry count of failed seal tasks + +- `scheduler.sealFailedRetryInterval`: retry interval of failed seal tasks, unit in hours + - `scheduler.strategy.dbFilesWeight`: how much bandwidth of this node will be used to fetch and store the history storage orders (Storage orders in the past four months). - `scheduler.strategy.newFilesWeight`: how much bandwidth of this node will be used to fetch and store the newest storage orders. diff --git a/website/translated_docs/zh-CN/build-smanager.md b/website/translated_docs/zh-CN/build-smanager.md index 0465de3a..3e761d3b 100644 --- a/website/translated_docs/zh-CN/build-smanager.md +++ b/website/translated_docs/zh-CN/build-smanager.md @@ -78,6 +78,8 @@ You could check [smanager-config.example.json](https://github.com/crustio/crust- "dataDir": "data", "scheduler": { "minSrdRatio": 30, + "sealFailedRetryCount": 3, + "sealFailedRetryInterval": 3, "strategy": { "dbFilesWeight": 0, "newFilesWeight": 100 @@ -102,6 +104,10 @@ Those config items will be loaded in the sManager configuration setup process. T > For example, if the ratio is 30, your node will start to accept storage order once the ratio of SRD capacity is higher than 30% +- `scheduler.sealFailedRetryCount`: retry count of failed seal tasks + +- `scheduler.sealFailedRetryInterval`: retry interval of failed seal tasks, unit in hours + - `scheduler.strategy.dbFilesWeight`: how much bandwidth of this node will be used to fetch and store the history storage orders (Storage orders in the past four months). - `scheduler.strategy.newFilesWeight`: how much bandwidth of this node will be used to fetch and store the newest storage orders.