Member since
06-14-2017
8
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4437 | 08-07-2017 04:21 AM |
08-08-2017
08:52 AM
1 Kudo
It looks like you're using the C++ client. Given that, you can use the KuduSession::SetTimeout() API: https://kudu.apache.org/cpp-client-api/classkudu_1_1client_1_1KuduSession.html#a25b22362650d7120f59cc1025e40bd79 -Todd
... View more
08-07-2017
04:21 AM
1 Kudo
If it happens to anyone else, we fixed this by deactivating IPv6 (seems that when resolving an address goes to the /etc/hosts for it, and if it only finds the IPv4 address then tries to get the IPv6 through DNS. Deactivating IPv6 in the servers avoids the DNS search).
... View more
06-16-2017
11:19 AM
1 Kudo
Yes, what you're observing is Kudu preallocating one 64 MB write-ahead log segment for each partition. The space will be filled once you start writing to the partition. In Kudu 1.4 we dropped the segment size from 64 MB to 8 MB. If you'd like to make that change now, you can do so via the --log_segment_size_mb command line option. An alternative would be to disable preallocation via --log_async_preallocate_segments=false and/or --log_preallocate_segments=false, but that's not something we generally test so I would advise against it.
... View more