lotus/storage
Łukasz Magiera 60d576241c fix: sched: Address GET_32G_MAX_CONCURRENT regression (#10850)
* Fix 1.21 regression: GET_32G_MAX_CONCURRENT + mixed prepared/executing leads to stuck scheduler

If you have 12 GET tasks and GET_32G_MAX_CONCURRENT=1, sealing jobs will only show assigned tasks for GET of the miner
and is stuck.
I believe this to be a regression of 1.21 unifying the counters, in the case of GETs where PrepType and TaskType
both being seal/v0/fetch leading to a state where tasks are blocked since already counted towards the limit.

* itests: Repro issue from PR #10633

* make counters int (non-working)

* fix: worker sched: Send taskDone notifs after tasks are done

* itests: Make TestPledgeMaxConcurrentGet actually reproduce the issue

* make the linter happy

---------

Co-authored-by: Steffen Butzer <steffen.butzer@outlook.com>
2023-05-10 15:45:50 -04:00
..
ctladdr sealing pipeline: Cleanup AddresSelector plumbing 2022-08-09 12:57:36 +02:00
paths fix: storage: Remove temp fetching files after failed fetch 2023-04-12 17:00:10 -07:00
pipeline Merge pull request #10696 from filecoin-project/fix/nil-terminate-wait 2023-04-25 19:28:52 +02:00
sealer fix: sched: Address GET_32G_MAX_CONCURRENT regression (#10850) 2023-05-10 15:45:50 -04:00
sectorblocks storage: Don't depend on specs-storage, move to storiface 2022-06-17 13:36:33 +02:00
wdpost chore: build: Merge/v22 into 21 for 23 (#10702) 2023-04-19 18:40:18 -04:00
winning_prover.go sealing pipeline: Remove useless storage adapter code 2022-08-09 13:40:06 +02:00