You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "runzhiwang (Jira)" <ji...@apache.org> on 2020/12/17 12:43:00 UTC

[jira] [Comment Edited] (RATIS-1249) Add route table in RaftConfiguration

    [ https://issues.apache.org/jira/browse/RATIS-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251058#comment-17251058 ] 

runzhiwang edited comment on RATIS-1249 at 12/17/20, 12:42 PM:
---------------------------------------------------------------

bq. Yes, we should start changing Streaming to use network topology. It actually should not be very hard. We may pass a routing table in the RaftConfiguration.
bq. 
bq.   interface RoutingTable {
bq.     List<RaftPeerId> getForwardPeers(RaftPeerId primary, RaftPeerId current);
bq.   }
bq. Then, each peer can use it to forward the requests.

[~szetszwo] Hi, I'm thinking wheter we need to pass a routing table in the RaftConfiguration.

In ozone case, in my thinking.
1. when client wants to write data, scm can answer to client with 3 datanodes in order such as dn1-> dn2 -> dn3 to client
2. when create stream, client send this order to dn1, dn1 send this order to dn2, dn2 send this order to dn3.
3. then client send data to dn1, dn1 send data to dn2, dn2 send data to dn3.


was (Author: yjxxtd):
bq. Yes, we should start changing Streaming to use network topology. It actually should not be very hard. We may pass a routing table in the RaftConfiguration.
bq. 
bq.   interface RoutingTable {
bq.     List<RaftPeerId> getForwardPeers(RaftPeerId primary, RaftPeerId current);
bq.   }
bq. Then, each peer can use it to forward the requests.

[~szetszwo] Hi, I'm thinking wheter we need to pass a routing table in the RaftConfiguration.

In my thinking.
1. when client wants to write data, scm can answer to client with 3 datanodes in order such as dn1-> dn2 -> dn3 to client
2. when create stream, client send this order to dn1, dn1 send this order to dn2, dn2 send this order to dn3.
3. then client send data to dn1, dn1 send data to dn2, dn2 send data to dn3.

> Add route table in RaftConfiguration
> ------------------------------------
>
>                 Key: RATIS-1249
>                 URL: https://issues.apache.org/jira/browse/RATIS-1249
>             Project: Ratis
>          Issue Type: Sub-task
>            Reporter: runzhiwang
>            Assignee: runzhiwang
>            Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)