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

Add synchronous UNS job amount to configuration #7747

Closed
4 of 14 tasks
jennijuju opened this issue Dec 9, 2021 · 2 comments · Fixed by #7884
Closed
4 of 14 tasks

Add synchronous UNS job amount to configuration #7747

jennijuju opened this issue Dec 9, 2021 · 2 comments · Fixed by #7884
Assignees
Labels
area/sealing kind/feature Kind: Feature P1 P1: Must be resolved
Milestone

Comments

@jennijuju
Copy link
Member

Checklist

  • This is not a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
  • This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
  • I have a specific, actionable, and well motivated feature request to propose.

Lotus component

  • lotus daemon - chain sync
  • lotus miner - mining and block production
  • lotus miner/worker - sealing
  • lotus miner - proving(WindowPoSt)
  • lotus miner/market - storage deal
  • lotus miner/market - retrieval deal
  • lotus miner/market - data transfer
  • lotus client
  • lotus JSON-RPC API
  • lotus message management (mpool)
  • Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

for better managing sealing resources. this will also help with SP that has many non-fast retrievals.

Describe the solution you'd like

have a configurable variable for how many unseal job a worker can have.

Describe alternatives you've considered

No response

Additional context

No response

@jennijuju jennijuju added kind/feature Kind: Feature need/triage area/sealing P1 P1: Must be resolved and removed need/triage labels Dec 9, 2021
@jennijuju jennijuju added this to the v1.13.3 milestone Dec 9, 2021
@jennijuju jennijuju changed the title Add UNS job amount to configuration Add synchronous UNS job amount to configuration Dec 9, 2021
@Angelo-gh3990
Copy link

It would be great if we can have our workers (PC1) do the unseal ... Right now when you enable unseal on the miner it works, but when you disbale it on the miner and enable it on the PC1 worker as an example it looks like it's wants to start but it time's out. Looks like it's not getting the data through the API from the miner to start the unsealing on the worker.
So the reason for this is so we can regulate it better on the miner for now to not overload it.

@benjaminh83
Copy link

Limiting the # of UNS jobs is a quick fix for making sure we do not overrun our lotus-miner with UNS jobs. This is a good start, but it does not solve the bug that it currently holding us from running UNS jobs seamlessly on our worker (Like the PC1 worker would be perfect for this task). Please see this perfect decription of the issue that is still present:

#7763

We need the UNS jobs not running on the miner itself, so worker bug should be fixed.

@ZenGround0 ZenGround0 self-assigned this Dec 17, 2021
@jennijuju jennijuju modified the milestones: v1.13.3, v1.15.0 Jan 2, 2022
laudiacay added a commit that referenced this issue Jan 13, 2022
…rrent unsealing jobs (#7884)

* adding the new variables- now time for logic

* putting parameters into right placeS

* adding unsealing throttle

* fixing linter issues

* removing one last thing...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sealing kind/feature Kind: Feature P1 P1: Must be resolved
Projects
None yet
6 participants