[
https://issues.apache.org/jira/browse/RATIS-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated RATIS-1373:
------------------------------
Description: We use StreamInfo#applyToRemotes to transfer data to to other
server, and eventually we call OrderedStreamAsync#sendRequest. So
StreamInfo#applyToRemotes finished after sending out request, but sometimes
OrderedStreamAsync#sendRequest costs hundred millseconds. So we need to make
StreamInfo#applyToRemotes async model, and also keep the order of request
belongs to the same stream. (was: We use StreamInfo#applyToRemotes to
transfer data to to other server, and eventually we call
OrderedStreamAsync#sendRequest. So StreamInfo#applyToRemotes finished after
sending out request, but sometimes OrderedStreamAsync#sendRequest costs hundred
millseconds. So we need to make StreamInfo#applyToRemotes async model, and also
keep the order of request belongs to the same stream. To achieve this, we can
do like StreamInfo#previos, but seems complicated.)
> Use async model for StreamInfo#applyToRemotes
> ---------------------------------------------
>
> Key: RATIS-1373
> URL: https://issues.apache.org/jira/browse/RATIS-1373
> Project: Ratis
> Issue Type: Sub-task
> Reporter: runzhiwang
> Priority: Major
>
> We use StreamInfo#applyToRemotes to transfer data to to other server, and
> eventually we call OrderedStreamAsync#sendRequest. So
> StreamInfo#applyToRemotes finished after sending out request, but sometimes
> OrderedStreamAsync#sendRequest costs hundred millseconds. So we need to make
> StreamInfo#applyToRemotes async model, and also keep the order of request
> belongs to the same stream.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
