[
https://issues.apache.org/jira/browse/RATIS-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214637#comment-17214637
]
runzhiwang edited comment on RATIS-1083 at 10/15/20, 11:57 AM:
---------------------------------------------------------------
[~szetszwo] Thanks for explanation, I have another question, sorry for that.
In ozone case, when write chunk, ozone client not only send the data, but also
send the metadata such as blockid. In RATIS-1085, before send data,
DataStreamOutputImpl send the header request in the constructor method, so the
header request does not contain the metadata (blockid), so do we send the
metadata (blockid) by DataStreamOutputImpl#writeAsync ?
was (Author: yjxxtd):
[~szetszwo] Thanks for explanation, I have another question, sorry for that.
In ozone case, when write chunk, ozone client not only send the data, but also
send the metadata such as blockid. In RATIS-1085, before send data,
DataStreamOutputImpl send the header request in the constructor method, so the
header request does not contain the metadata (blockid), so do we send the
metadata (blockid) by writeAsync ?
> Create a transaction once the stream data is replicated to all servers
> ----------------------------------------------------------------------
>
> Key: RATIS-1083
> URL: https://issues.apache.org/jira/browse/RATIS-1083
> Project: Ratis
> Issue Type: Sub-task
> Components: Streaming
> Reporter: Tsz-wo Sze
> Assignee: runzhiwang
> Priority: Major
>
> Once the stream data has been replicated to all server, the leader should
> create a Raft transaction. When the leader send the transaction to the other
> server by appendEntries, it only has to send the stream data ID instead of
> sending the stream data.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
