<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question DNS Error when trying to insert data in Kudu table in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58169#M14259</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;We have a Kudu installation with 3 tablet servers and when we try to insert data using the C++ Kudu API we get the following errors:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;W0728 10:10:49.129612&amp;nbsp; 8707 meta_cache.cc:207] Tablet ee4f630ffb8b440faa029c106df6c058: Replica 4c09e6d53a8248a3bc6e1f6408c0d0a6 (bigdata07dev:7050) has failed: Network error: Failed to resolve address for TS 4c09e6d53a8248a3bc6e1f6408c0d0a6: Unable to resolve address 'bigdata07dev': Name or service not known
W0728 10:10:50.142993&amp;nbsp; 8707 meta_cache.cc:207] Tablet 04f38c93f4c14fa29a581cb2b70aa982: Replica 0cf3c1866a094ee0b2305bca770f5e70 (bigdata09dev:7050) has failed: Network error: Failed to resolve address for TS 0cf3c1866a094ee0b2305bca770f5e70: Unable to resolve address 'bigdata09dev': Name or service not known
W0728 10:10:51.165246&amp;nbsp; 8707 meta_cache.cc:207] Tablet 4e8f82788d0d4442bd91f39b3a09f5ca: Replica 5a6eb71e57554893b09acbd0a052aa9e (bigdata08dev:7050) has failed: Network error: Failed to resolve address for TS 5a6eb71e57554893b09acbd0a052aa9e: Unable to resolve address 'bigdata08dev': Name or service not known
W0728 10:10:52.165480&amp;nbsp; 8707 meta_cache.cc:207] Tablet a992ebf9cc3c40bda5c458cabeb2cabf: Replica 0cf3c1866a094ee0b2305bca770f5e70 (bigdata09dev:7050) has failed: Network error: Failed to resolve address for TS 0cf3c1866a094ee0b2305bca770f5e70: Unable to resolve address 'bigdata09dev': Name or service not known
W0728 10:10:53.185971&amp;nbsp; 8707 meta_cache.cc:207] Tablet a56b25d77bd7406099533cbcff6b59a5: Replica 5a6eb71e57554893b09acbd0a052aa9e (bigdata08dev:7050) has failed: Network error: Failed to resolve address for TS 5a6eb71e57554893b09acbd0a052aa9e: Unable to resolve address 'bigdata08dev': Name or service not known
W0728 10:10:54.191416&amp;nbsp; 8707 meta_cache.cc:207] Tablet 57129396125e4db2ba9374acfe013682: Replica 5a6eb71e57554893b09acbd0a052aa9e (bigdata08dev:7050) has failed: Network error: Failed to resolve address for TS 5a6eb71e57554893b09acbd0a052aa9e: Unable to resolve address 'bigdata08dev': Name or service not known
W0728 10:10:55.212915&amp;nbsp; 8707 meta_cache.cc:207] Tablet 3cc7d0b868834cdd883768b5d5afed68: Replica 0cf3c1866a094ee0b2305bca770f5e70 (bigdata09dev:7050) has failed: Network error: Failed to resolve address for TS 0cf3c1866a094ee0b2305bca770f5e70: Unable to resolve address 'bigdata09dev': Name or service not known
W0728 10:10:56.219542&amp;nbsp; 8707 meta_cache.cc:207] Tablet 91f1452cbb0942d3a3ef1bf60b1d97ab: Replica 0cf3c1866a094ee0b2305bca770f5e70 (bigdata09dev:7050) has failed: Network error: Failed to resolve address for TS 0cf3c1866a094ee0b2305bca770f5e70: Unable to resolve address 'bigdata09dev': Name or service not known
W0728 10:10:57.220916&amp;nbsp; 8707 meta_cache.cc:207] Tablet 2ff810ab35724222a01e5db584c87c35: Replica 4c09e6d53a8248a3bc6e1f6408c0d0a6 (bigdata07dev:7050) has failed: Network error: Failed to resolve address for TS 4c09e6d53a8248a3bc6e1f6408c0d0a6: Unable to resolve address 'bigdata07dev': Name or service not known
W0728 10:11:02.837929&amp;nbsp; 8707 net_util.cc:129] Time spent resolving address for bigdata07dev: real 5.012s user 0.000s sys 0.000s
W0728 10:11:02.838008&amp;nbsp; 8707 meta_cache.cc:207] Tablet a56b25d77bd7406099533cbcff6b59a5: Replica 4c09e6d53a8248a3bc6e1f6408c0d0a6 (bigdata07dev:7050) has failed: Network error: Failed to resolve address for TS 4c09e6d53a8248a3bc6e1f6408c0d0a6: Unable to resolve address 'bigdata07dev': Name or service not known
W0728 10:11:02.857394&amp;nbsp; 8703 batcher.cc:329] Timed out: Failed to write batch of 805 ops to tablet a56b25d77bd7406099533cbcff6b59a5 after 15 attempt(s): Failed to write to server: (no server available): Write(tablet: a56b25d77bd7406099533cbcff6b59a5, num_ops: 805, num_attempts: 15) passed its deadline: Network error: Failed to resolve address for TS 5a6eb71e57554893b09acbd0a052aa9e: Unable to resolve address 'bigdata08dev': Name or service not known
Check failed: _s.ok() Bad status: IO error: Some errors occurred&lt;/PRE&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;nbsp; &amp;nbsp;We don't have DNS to resolve the names, instead we use the hosts file of the OS. Is there a way to configure Kudu to use the hosts file?&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;nbsp; &amp;nbsp;Thank you very much and best regards&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 11:59:53 GMT</pubDate>
    <dc:creator>albers2n</dc:creator>
    <dc:date>2022-09-16T11:59:53Z</dc:date>
    <item>
      <title>DNS Error when trying to insert data in Kudu table</title>
      <link>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58169#M14259</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;We have a Kudu installation with 3 tablet servers and when we try to insert data using the C++ Kudu API we get the following errors:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;W0728 10:10:49.129612&amp;nbsp; 8707 meta_cache.cc:207] Tablet ee4f630ffb8b440faa029c106df6c058: Replica 4c09e6d53a8248a3bc6e1f6408c0d0a6 (bigdata07dev:7050) has failed: Network error: Failed to resolve address for TS 4c09e6d53a8248a3bc6e1f6408c0d0a6: Unable to resolve address 'bigdata07dev': Name or service not known
W0728 10:10:50.142993&amp;nbsp; 8707 meta_cache.cc:207] Tablet 04f38c93f4c14fa29a581cb2b70aa982: Replica 0cf3c1866a094ee0b2305bca770f5e70 (bigdata09dev:7050) has failed: Network error: Failed to resolve address for TS 0cf3c1866a094ee0b2305bca770f5e70: Unable to resolve address 'bigdata09dev': Name or service not known
W0728 10:10:51.165246&amp;nbsp; 8707 meta_cache.cc:207] Tablet 4e8f82788d0d4442bd91f39b3a09f5ca: Replica 5a6eb71e57554893b09acbd0a052aa9e (bigdata08dev:7050) has failed: Network error: Failed to resolve address for TS 5a6eb71e57554893b09acbd0a052aa9e: Unable to resolve address 'bigdata08dev': Name or service not known
W0728 10:10:52.165480&amp;nbsp; 8707 meta_cache.cc:207] Tablet a992ebf9cc3c40bda5c458cabeb2cabf: Replica 0cf3c1866a094ee0b2305bca770f5e70 (bigdata09dev:7050) has failed: Network error: Failed to resolve address for TS 0cf3c1866a094ee0b2305bca770f5e70: Unable to resolve address 'bigdata09dev': Name or service not known
W0728 10:10:53.185971&amp;nbsp; 8707 meta_cache.cc:207] Tablet a56b25d77bd7406099533cbcff6b59a5: Replica 5a6eb71e57554893b09acbd0a052aa9e (bigdata08dev:7050) has failed: Network error: Failed to resolve address for TS 5a6eb71e57554893b09acbd0a052aa9e: Unable to resolve address 'bigdata08dev': Name or service not known
W0728 10:10:54.191416&amp;nbsp; 8707 meta_cache.cc:207] Tablet 57129396125e4db2ba9374acfe013682: Replica 5a6eb71e57554893b09acbd0a052aa9e (bigdata08dev:7050) has failed: Network error: Failed to resolve address for TS 5a6eb71e57554893b09acbd0a052aa9e: Unable to resolve address 'bigdata08dev': Name or service not known
W0728 10:10:55.212915&amp;nbsp; 8707 meta_cache.cc:207] Tablet 3cc7d0b868834cdd883768b5d5afed68: Replica 0cf3c1866a094ee0b2305bca770f5e70 (bigdata09dev:7050) has failed: Network error: Failed to resolve address for TS 0cf3c1866a094ee0b2305bca770f5e70: Unable to resolve address 'bigdata09dev': Name or service not known
W0728 10:10:56.219542&amp;nbsp; 8707 meta_cache.cc:207] Tablet 91f1452cbb0942d3a3ef1bf60b1d97ab: Replica 0cf3c1866a094ee0b2305bca770f5e70 (bigdata09dev:7050) has failed: Network error: Failed to resolve address for TS 0cf3c1866a094ee0b2305bca770f5e70: Unable to resolve address 'bigdata09dev': Name or service not known
W0728 10:10:57.220916&amp;nbsp; 8707 meta_cache.cc:207] Tablet 2ff810ab35724222a01e5db584c87c35: Replica 4c09e6d53a8248a3bc6e1f6408c0d0a6 (bigdata07dev:7050) has failed: Network error: Failed to resolve address for TS 4c09e6d53a8248a3bc6e1f6408c0d0a6: Unable to resolve address 'bigdata07dev': Name or service not known
W0728 10:11:02.837929&amp;nbsp; 8707 net_util.cc:129] Time spent resolving address for bigdata07dev: real 5.012s user 0.000s sys 0.000s
W0728 10:11:02.838008&amp;nbsp; 8707 meta_cache.cc:207] Tablet a56b25d77bd7406099533cbcff6b59a5: Replica 4c09e6d53a8248a3bc6e1f6408c0d0a6 (bigdata07dev:7050) has failed: Network error: Failed to resolve address for TS 4c09e6d53a8248a3bc6e1f6408c0d0a6: Unable to resolve address 'bigdata07dev': Name or service not known
W0728 10:11:02.857394&amp;nbsp; 8703 batcher.cc:329] Timed out: Failed to write batch of 805 ops to tablet a56b25d77bd7406099533cbcff6b59a5 after 15 attempt(s): Failed to write to server: (no server available): Write(tablet: a56b25d77bd7406099533cbcff6b59a5, num_ops: 805, num_attempts: 15) passed its deadline: Network error: Failed to resolve address for TS 5a6eb71e57554893b09acbd0a052aa9e: Unable to resolve address 'bigdata08dev': Name or service not known
Check failed: _s.ok() Bad status: IO error: Some errors occurred&lt;/PRE&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;nbsp; &amp;nbsp;We don't have DNS to resolve the names, instead we use the hosts file of the OS. Is there a way to configure Kudu to use the hosts file?&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;nbsp; &amp;nbsp;Thank you very much and best regards&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 11:59:53 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58169#M14259</guid>
      <dc:creator>albers2n</dc:creator>
      <dc:date>2022-09-16T11:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Error when trying to insert data in Kudu table</title>
      <link>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58244#M14260</link>
      <description>&lt;P&gt;UP!!&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2017 11:50:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58244#M14260</guid>
      <dc:creator>albers2n</dc:creator>
      <dc:date>2017-07-31T11:50:00Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Error when trying to insert data in Kudu table</title>
      <link>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58252#M14261</link>
      <description>&lt;P&gt;Kudu doesn't do anything special to resolve hostnames, so it should use the hosts file by&amp;nbsp;way of doing the resolving. You can also see a 5s delay when trying to resolve the address, I would recommend googling "dns 5 seconds delay" and debug your network situation from there.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2017 16:21:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58252#M14261</guid>
      <dc:creator>J-D</dc:creator>
      <dc:date>2017-07-31T16:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Error when trying to insert data in Kudu table</title>
      <link>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58479#M14262</link>
      <description>&lt;P&gt;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).&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2017 11:21:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/DNS-Error-when-trying-to-insert-data-in-Kudu-table/m-p/58479#M14262</guid>
      <dc:creator>albers2n</dc:creator>
      <dc:date>2017-08-07T11:21:32Z</dc:date>
    </item>
  </channel>
</rss>

