[
https://issues.apache.org/jira/browse/RATIS-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214678#comment-17214678
]
Tsz-wo Sze commented on RATIS-1083:
-----------------------------------
Ozone uses Ratis as a transportation layer. When we say header and data in
Ratis, we mean Ratis header and user data. Of course, user applications such
as Ozone could have its own header and body divisions. So, the user data in
Ozone is actually Ozone header + Ozone body, i.e. Ozone should send Ozone
header as part of the user data.
Consider the AsyncApi, Ozone encodes Ozone header and Ozone body together as a
single Message (ByteString). In the DataStreamApi, Ozone encodes Ozone header
and Ozone body together as a list of ByteBuffers.
> 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)
