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

Fix config doc

Browse Source
This commit is contained in:
Łukasz Magiera 2022-05-24 01:33:56 +02:00
parent 8c081e271a
commit 70f3b98574
3 changed files with 21 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -542,6 +542,15 @@
# env var: LOTUS_STORAGE_ASSIGNER # env var: LOTUS_STORAGE_ASSIGNER
#Assigner = "utilization" #Assigner = "utilization"
# DisallowRemoteFinalize when set to true will force all Finalize tasks to
# run on workers with local access to both long-term storage and the sealing
# path containing the sector.
# --
# WARNING: Only set this if all workers have access to long-term storage
# paths. If this flag is enabled, and there are workers without long-term
# storage access, sectors will not be moved from them, and Finalize tasks
# will appear to be stuck.
# --
# If you see stuck Finalize tasks after enabling this setting, check # If you see stuck Finalize tasks after enabling this setting, check
# 'lotus-miner sealing sched-diag' and 'lotus-miner storage find [sector num]' # 'lotus-miner sealing sched-diag' and 'lotus-miner storage find [sector num]'
# #

11
node/config/doc_gen.go
View File

@ -768,7 +768,16 @@ This parameter is ONLY applicable if the retrieval pricing policy strategy has b
Name: "DisallowRemoteFinalize", Name: "DisallowRemoteFinalize",
Type: "bool", Type: "bool",
Comment: `If you see stuck Finalize tasks after enabling this setting, check Comment: `DisallowRemoteFinalize when set to true will force all Finalize tasks to
run on workers with local access to both long-term storage and the sealing
path containing the sector.
--
WARNING: Only set this if all workers have access to long-term storage
paths. If this flag is enabled, and there are workers without long-term
storage access, sectors will not be moved from them, and Finalize tasks
will appear to be stuck.
--
If you see stuck Finalize tasks after enabling this setting, check
'lotus-miner sealing sched-diag' and 'lotus-miner storage find [sector num]'`, 'lotus-miner sealing sched-diag' and 'lotus-miner storage find [sector num]'`,
}, },
{ {

4
node/config/types.go
View File

@ -338,12 +338,12 @@ type SealerConfig struct {
// DisallowRemoteFinalize when set to true will force all Finalize tasks to // DisallowRemoteFinalize when set to true will force all Finalize tasks to
// run on workers with local access to both long-term storage and the sealing // run on workers with local access to both long-term storage and the sealing
// path containing the sector. // path containing the sector.
// // --
// WARNING: Only set this if all workers have access to long-term storage // WARNING: Only set this if all workers have access to long-term storage
// paths. If this flag is enabled, and there are workers without long-term // paths. If this flag is enabled, and there are workers without long-term
// storage access, sectors will not be moved from them, and Finalize tasks // storage access, sectors will not be moved from them, and Finalize tasks
// will appear to be stuck. // will appear to be stuck.
// // --
// If you see stuck Finalize tasks after enabling this setting, check // If you see stuck Finalize tasks after enabling this setting, check
// 'lotus-miner sealing sched-diag' and 'lotus-miner storage find [sector num]' // 'lotus-miner sealing sched-diag' and 'lotus-miner storage find [sector num]'
DisallowRemoteFinalize bool DisallowRemoteFinalize bool