Sorry for my mistake.
The copy replica could be read by clients with below API in client.h:

        Status SetSelection(KuduClient::ReplicaSelection selection)
        WARN_UNUSED_RESULT;

        enum ReplicaSelection {
        LEADER_ONLY,      ///< Select the LEADER replica.

            CLOSEST_REPLICA,  ///< Select the closest replica to the client,
                          ///< or a random one if all replicas are equidistant.

            FIRST_REPLICA     ///< Select the first replica in the list.
        };


何李夫
2017-04-10 16:06:24

-----邮件原件-----
发件人: [email protected] 
[mailto:[email protected]] 代表 ??
发送时间: 2017年10月26日 13:50
收件人: [email protected]
主题: Re: 答复: How kudu synchronize real-time records?

Thanks for replying me.

It helps a lot.

2017-10-26 12:29 GMT+09:00 helifu <[email protected]>:
> Hi,
>
> Now the read/write operations are limited to the master replica(record1 on 
> node1), and the copy replica(record1 on node2/node3) can't be read/write by 
> clients directly.
>
>
> 何李夫
> 2017-04-10 11:24:24
>
> -----邮件原件-----
> 发件人: [email protected] 
> [mailto:[email protected]] 代表 ??
> 发送时间: 2017年10月26日 10:43
> 收件人: [email protected]
> 主题: How kudu synchronize real-time records?
>
> Hi!
>
> I read from documents saying 'once kudu receives records from client it write 
> those records into WAL (also does replica)'
>
> And i wonder it can be different time when load those records from WAL in 
> each node.
> So let's say node1 load record1 from WAL at t1, node2 t2, node3 t3 (t1 < t2 < 
> t3) then reading client attached node1 can see record but other reading 
> clients attached not node1(node2, node3) have possibilities missing record1.
>
> I think that does not happens in kudu, and i wonder how kudu synchronize real 
> time data.
>
> Thanks!
>

Reply via email to