Add description for sealFailedRetryCount and sealFailedRetryInterval …

…config in smanager
crustio · Dec 3, 2024 · c851f38 · c851f38
1 parent 5d43dea
commit c851f38
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git 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
@@ -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.