Re: Error message: 'Tried to update clock beyond the max. error.'

Which version of Kudu do you use? I also encountered this error a few days ago using Kudu1.3.0: "Tried to update clock beyond the max. error.", after restarting the cluster, everything goes normal. I checked the dmesg and asked SRE to check the ntp service, everything looks normal. Still have no

Error message: 'Tried to update clock beyond the max. error.'

A few days ago at work our Kudu servers started having fatal errors and shutting down with the following error message: Couldn't get the current time: Clock unsynchronized. Status: Service unavailable: Error: Clock synchronized but error wastoo high (1016 us). After some research

Re: Low ingestion rate from Kafka

In addition to what Zhen suggests, I'm also curious how you are sizing your batches in manual-flush mode? With 128 hash partitions, each batch is generating 128 RPCs, so if for example you are only batching 1000 rows at a time, you'll end up with a lot of fixed overhead in each RPC to insert just

Re: Low ingestion rate from Kafka

If you want to manage batching yourself you can use the manual flush mode. Easiest would be the auto flush background mode. Todd On Oct 30, 2017 11:10 PM, "Chao Sun" wrote: > Hi Todd, > > Thanks for the reply! I used a single Kafka consumer to pull the data. > For Kudu, I was