I have got another idea. if I change the param --follower_unavailable_considered_failed_sec=3600 or more, that disable data migration almost, We can balance data by kudu command line tools kudu table change_config add_replica <https://kudu.apache.org/docs/command_line_tools_reference.html#change_config-add_replica> /remove_replica <https://kudu.apache.org/docs/command_line_tools_reference.html#change_config-add_replica> to balance data. small-scale data migration will not take so much network traffic. maybe this is we need.๐
2017-09-05 7:12 GMT+08:00 Li Jin <[email protected]>: > Hi Andrew, > > Thanks for replay. I seeing at zabbix, I would like reduce the use of network > traffic and make sure the business online is not affect. I try to change > the configure num_tablets_to_copy_simultaneously from 10 to 1, Can it be > meet my needs? > > King Lee > > 2017-09-05 3:35 GMT+08:00 Andrew Wong <[email protected]>: > >> Hi Li, >> >> What errors are you seeing when the network traffic is full? Kudu needs >> to replicate all the data that was lost to maintain the specified >> replication factor. As far as I know there isn't a way to throttle this >> without giving up some guarantees. >> >> If the concern is around Kudu scans completing, there is an >> `isFaultTolerant` mode for the scanner that will retry at other servers, >> although I'm not sure this is what you want. >> >> >> Andrew >> >> >> On Mon, Sep 4, 2017 at 5:34 AM, Li Jin <[email protected]> wrote: >> >>> Hi,I got a question. >>> Our kudu service is production now. when ts crash, data will migration >>> between ts. Network traffic will full and can not write or write >>> normally. itโs unacceptable. Is there any good way to control network >>> traffic when ts crash, and write or read service is not affect. Thanks! >>> >> >> >> >> -- >> Andrew Wong >> > >
