feat(matching): use ShardProcessors instead of TaskListManagers #7480
+217
−122
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Why?
The executor library is using the concept of shardProcessor to monitor a shard, in the case of matching a shardProcessor can be seen as a task executor manager.
The change in the executor library is necessary because moving the logic from the
How did you test it?
tested locally and with unit tests
Potential risks
matching service could be affected since we are changing the way we create new tasks.
Release notes
Documentation Changes