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

MaxSealingSectors setting seemingly ignored #3896

Closed
karalabe opened this issue Sep 17, 2020 · 2 comments
Closed

MaxSealingSectors setting seemingly ignored #3896

karalabe opened this issue Sep 17, 2020 · 2 comments
Assignees
Labels

Comments

@karalabe
Copy link
Contributor

I've set MaxSealingSectors = 4 (because I've queued up too many PCs and it OOMs my node). However, even like this, lotus starts all of the 7 PCs queued up. Is there a way to make it only do 3-4 concurrently without removing some of them and leaving the gap in the sector list?

@kenshyx
Copy link
Contributor

kenshyx commented Sep 17, 2020

This setting has effect only on pledge command at the moment from what I saw.

@TippyFlitsUK
Copy link
Contributor

Hi @karalabe

Thanks for the report. The issue is outdated.

If this is a issue in the current release - please open a new ticket.

Thank you !

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

No branches or pull requests

4 participants