[
https://issues.apache.org/jira/browse/RATIS-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229846#comment-17229846
]
runzhiwang edited comment on RATIS-979 at 11/11/20, 11:05 AM:
--------------------------------------------------------------
[~szetszwo] Currently, when START_TRANSACTION, primary try to submit client
request, if failed, then primary asks 2 peers to submit client request by
[forwardStartTransaction|https://github.com/apache/incubator-ratis/blob/master/ratis-netty/src/main/java/org/apache/ratis/netty/server/NettyServerStreamRpc.java#L393].
Do you think it needs to be improved ? For example, record leader in primary,
and primary ask leader to submit client request. Not sure whether it's
necessary.
was (Author: yjxxtd):
[~szetszwo] Currently, when START_TRANSACTION, primary try to submit client
request, if failed, then primary asks 2 peers to submit client request by
[forwardStartTransaction|https://github.com/apache/incubator-ratis/blob/master/ratis-netty/src/main/java/org/apache/ratis/netty/server/NettyServerStreamRpc.java#L393].
Do you think it needs to be improved ? For example, record leader in
NettyServerStreamRpc, and primary ask leader to submit client request. Not sure
whether it's necessary.
> Ratis streaming
> ---------------
>
> Key: RATIS-979
> URL: https://issues.apache.org/jira/browse/RATIS-979
> Project: Ratis
> Issue Type: New Feature
> Components: Streaming
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Attachments: RatisStreaming20200929.pdf
>
>
> In this JIRA, we design and implement Ratis Streaming with zero buffer
> copying and asynchronous event driven.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
