Skip to content

limit the number of tokens a transaction retrieves and locks#1707

Open
HayimShaul wants to merge 4 commits into
mainfrom
1641_bound_work_by_request
Open

limit the number of tokens a transaction retrieves and locks#1707
HayimShaul wants to merge 4 commits into
mainfrom
1641_bound_work_by_request

Conversation

@HayimShaul

Copy link
Copy Markdown
Contributor

solve issue #1641

@HayimShaul HayimShaul added this to the Q2/26 milestone May 14, 2026
@HayimShaul HayimShaul self-assigned this May 14, 2026
@HayimShaul HayimShaul force-pushed the 1641_bound_work_by_request branch 4 times, most recently from dda132d to 142170c Compare May 21, 2026 10:00
@HayimShaul HayimShaul marked this pull request as ready for review May 24, 2026 07:42
@HayimShaul HayimShaul requested a review from adecaro May 24, 2026 07:42
@adecaro

adecaro commented May 26, 2026

Copy link
Copy Markdown
Contributor

Hi @HayimShaul , should these changes apply also to sherdlock?

@HayimShaul HayimShaul force-pushed the 1641_bound_work_by_request branch 2 times, most recently from 0a0b6ca to 2662935 Compare May 31, 2026 11:07
Comment thread token/services/selector/sherdlock/manager.go Outdated
Comment thread token/services/selector/simple/manager.go
Comment thread token/services/selector/sherdlock/selector.go
Comment thread token/services/selector/sherdlock/selector_shutdown_test.go
@adecaro

adecaro commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

@HayimShaul , don't we need to enforce limit also at the fetcher level token/services/selector/sherdlock/fetcher.go when the token db is queried?

A more general question, if we say that we can only load 100 tokens at the time from the storage, what if for these 100 tokens the selection request cannot be satisfied, but if had picked the tokens differently we would have. We might reject requests that can be satisfied.

@HayimShaul

Copy link
Copy Markdown
Contributor Author

Hi @HayimShaul , should these changes apply also to sherdlock?

done

@adecaro adecaro modified the milestones: Q2/26, Q3/26 Jun 2, 2026
@HayimShaul HayimShaul force-pushed the 1641_bound_work_by_request branch 3 times, most recently from 4ac2576 to 079ec93 Compare June 7, 2026 08:23
@HayimShaul HayimShaul force-pushed the 1641_bound_work_by_request branch from cb59a41 to 3778cd1 Compare June 14, 2026 09:43
@AkramBitar AkramBitar force-pushed the 1641_bound_work_by_request branch 3 times, most recently from 39378e4 to 1bdbe20 Compare June 23, 2026 12:13
@HayimShaul HayimShaul force-pushed the 1641_bound_work_by_request branch from 95ef2b6 to 319c6fb Compare June 30, 2026 07:42
Signed-off-by: Hayim.Shaul@ibm.com <hayimsha@fhe03.vpc.cloud9.ibm.com>
Hayim.Shaul@ibm.com added 3 commits July 1, 2026 14:50
fix
Signed-off-by: Hayim.Shaul@ibm.com <hayimsha@fhe03.vpc.cloud9.ibm.com>
Signed-off-by: Hayim.Shaul@ibm.com <hayimsha@fhe03.vpc.cloud9.ibm.com>
fix
Signed-off-by: Hayim.Shaul@ibm.com <hayimsha@fhe03.vpc.cloud9.ibm.com>
@HayimShaul HayimShaul force-pushed the 1641_bound_work_by_request branch from 2b91b1f to 8f6abe6 Compare July 1, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bound All Work Triggered by a Single Token Selection Request [HIGH]

3 participants