[ISSUE-184] Support async submit events. #185
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 changes were proposed in this pull request?
使用独立的rpc不能保证有序，在rpc server端可能接收到乱序，如果在一组rpc请求内，允许乱序，而不同组直接通过同步等待，保证严格有序即可。
在scheduler每一轮发送的一组event，对于发给单个worker的event，已经合并到ComposeEvent中，不同event是发给不同的worker的，也即这些event可以允许乱序，在运行时表现为不同worker收到event时间先后顺序不同而已。
当一组event发送完成后，同步等待所有event的响应，直到确认所有event的回应后，才继续执行。
How was this PR tested?