[improve][pcip] PCIP-4 Improve delayed RPC message handling in pulsar-rpc #12
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.
Motivation
Currently, Pulsar RPC encounters some issues with delayed messages (delayed RPC). The current behavior involves storing RPC requests and the responses returned by the server in the pendingRequestsMap. When the server responds, it checks the pendingRequestsMap for the corresponding RPC request. If no request is found, the response is “discarded” and not returned for user handling. We aim to perform RPC requests on a scheduled basis, especially when there are long delays, meaning the message will persist in the pendingRequestsMap for an extended period. Therefore, we need to improve the handling behavior for such delayed RPC scenarios.
Modifications
In the case of delaying the sending of RPC requests:
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)