Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There are no "seal task types" configuration options in $LOTUS_STORAGE_PATH/config.toml #2334

Closed
UltraVis opened this issue Jul 9, 2020 · 1 comment

Comments

@UltraVis
Copy link

UltraVis commented Jul 9, 2020

Describe the bug
There is no "seal task types" parameters for disabling in storage-miner's configuration (config.toml), as per:

### Running locally for manually managing process priority

You can also run the **Lotus Seal Worker** on the same machine as your **Lotus Storage Miner**, so you can manually manage the process priority.
To do so you have to first __disable all seal task types__ in the miner config. This is important to prevent conflicts between the two processes.

You can then run the storage miner on your local-loopback interface;

in ~/lotus/documentation/en/mining-lotus-seal-worker.md

To Reproduce

  1. look in the mining-lotus-seal-worker.md file for the instructions for "### Running locally for manually managing process priority"
  2. search for the "all seal task types" for disablement in storage-miner's config.toml file
  3. "seal tasks types" not found (or not obvious?)

Expected behavior
There are seal-task type parameters easily visible/identifiable for disablement for the purpose of running lotus-seal-worker in a separate process in the same miner server.

Screenshots
N/A

Version (run lotus version):
lotus version 0.4.1+git.24d8a84a

Additional context
N/A

@UltraVis
Copy link
Author

UltraVis commented Jul 15, 2020

From my testing, it appears the "all seal task types" are these entries in the "Storage" section in the config.toml:

[Storage]
#  AllowPreCommit1 = true
#  AllowPreCommit2 = true
#  AllowCommit = true
#  AllowUnseal = true

Uncomment these entries and set the values to "false" seem to make lotus-seal-worker get used when needed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant