<?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 Re: Datanode IPC port TIME_WAIT in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Datanode-IPC-port-TIME-WAIT/m-p/352295#M236485</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/41138"&gt;@isoardi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Seeing sockets in TIME_WAIT state is normal and is by design when the socket is getting closed. Unless we see tens of thousands of sockets in TIME_WAIT state which would consume the ephemeral ports on the host , these are fine. It would be the CLOSE_WAIT sockets we need check which indicates the application has not called the close() call on the socket.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can refer the below RedHat documentation for more info on this and ways to close the TW sockets by reusing them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://access.redhat.com/solutions/24154" target="_blank"&gt;https://access.redhat.com/solutions/24154&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 15 Sep 2022 07:22:32 GMT</pubDate>
    <dc:creator>rki_</dc:creator>
    <dc:date>2022-09-15T07:22:32Z</dc:date>
    <item>
      <title>Datanode IPC port TIME_WAIT</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Datanode-IPC-port-TIME-WAIT/m-p/352116#M236441</link>
      <description>&lt;P&gt;hello to all,&lt;BR /&gt;I have many connections in time_wait on the ipc port 1019 of the datanode:&lt;BR /&gt;More than 600 time_wait and about 250 established.&lt;BR /&gt;Is that normal?&lt;/P&gt;&lt;P&gt;I’m afraid that’s why index write closed on solr errors (the index is on hdfs).&lt;BR /&gt;The servers are downloaded and the datanode does not saturate the jvm heap.&lt;/P&gt;&lt;P&gt;I couldn’t find any max connection configuration for port 1019&lt;BR /&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Environment:&lt;/P&gt;&lt;P&gt;HDP 3.1.5.0-152 with HDFS 3.1.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 07:42:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Datanode-IPC-port-TIME-WAIT/m-p/352116#M236441</guid>
      <dc:creator>isoardi</dc:creator>
      <dc:date>2022-09-13T07:42:37Z</dc:date>
    </item>
    <item>
      <title>Re: Datanode IPC port TIME_WAIT</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Datanode-IPC-port-TIME-WAIT/m-p/352295#M236485</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/41138"&gt;@isoardi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Seeing sockets in TIME_WAIT state is normal and is by design when the socket is getting closed. Unless we see tens of thousands of sockets in TIME_WAIT state which would consume the ephemeral ports on the host , these are fine. It would be the CLOSE_WAIT sockets we need check which indicates the application has not called the close() call on the socket.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can refer the below RedHat documentation for more info on this and ways to close the TW sockets by reusing them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://access.redhat.com/solutions/24154" target="_blank"&gt;https://access.redhat.com/solutions/24154&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 07:22:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Datanode-IPC-port-TIME-WAIT/m-p/352295#M236485</guid>
      <dc:creator>rki_</dc:creator>
      <dc:date>2022-09-15T07:22:32Z</dc:date>
    </item>
    <item>
      <title>Re: Datanode IPC port TIME_WAIT</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Datanode-IPC-port-TIME-WAIT/m-p/352304#M236487</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/80393"&gt;@rki_&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;Thanks for the explanation.&lt;/P&gt;&lt;P&gt;I had hoped to have found a reason for the index writer closed error of SolR.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks you anyway&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 07:57:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Datanode-IPC-port-TIME-WAIT/m-p/352304#M236487</guid>
      <dc:creator>isoardi</dc:creator>
      <dc:date>2022-09-15T07:57:39Z</dc:date>
    </item>
  </channel>
</rss>

