<?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>topic Re: Slow/Unresponsive Deployment Server. Deployment Clients timing out. in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Slow-Unresponsive-Deployment-Server-Deployment-Clients-timing/m-p/546745#M18723</link>
    <description>&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;That is because with default DS configuration, DS has reached a saturation point of handling too many phone home checks. Here are the recommendations&amp;nbsp;to increase DS scalability.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;STRONG&gt;&lt;SPAN class="s1"&gt;On the DS server.conf&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;[sslConfig]&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;sslServerSessionTimeout = 7200&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;[httpServer]&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;dedicatedIoThreads = 10&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p2"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Set following config to 512.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;In $SPLUNK_HOME/etc/splunk-launch.conf on DS.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;SPLUNK_LISTEN_BACKLOG = 512&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Note:&amp;nbsp;Make sure linux net.core.somaxconn setting is more than SPLUNK_LISTEN_BACKLOG.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p2"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;STRONG&gt;&lt;SPAN class="s1"&gt;On DC side&amp;nbsp; server.conf&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;[sslConfig]&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;useSslClientSessionCache=true&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Upgrade all DC to 7.1.3 and above to have configurable and higher default DC timeouts. Before 7.1.3 these are hardcoded 5 sec.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;connect_timeout = &amp;lt;positive integer&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;* Default: 60&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;send_timeout = &amp;lt;positive integer&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;* Default: 60&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;recv_timeout = &amp;lt;positive integer&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;* Default: 60&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Apr 2021 19:10:06 GMT</pubDate>
    <dc:creator>hrawat</dc:creator>
    <dc:date>2021-04-05T19:10:06Z</dc:date>
    <item>
      <title>Slow/Unresponsive Deployment Server. Deployment Clients timing out.</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Slow-Unresponsive-Deployment-Server-Deployment-Clients-timing/m-p/546741#M18722</link>
      <description>&lt;P&gt;&lt;SPAN&gt;There are&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;503 errors and DC can't connect messages in splunkd.log on deployment client.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Apr 2021 18:51:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Slow-Unresponsive-Deployment-Server-Deployment-Clients-timing/m-p/546741#M18722</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2021-04-05T18:51:24Z</dc:date>
    </item>
    <item>
      <title>Re: Slow/Unresponsive Deployment Server. Deployment Clients timing out.</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Slow-Unresponsive-Deployment-Server-Deployment-Clients-timing/m-p/546745#M18723</link>
      <description>&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;That is because with default DS configuration, DS has reached a saturation point of handling too many phone home checks. Here are the recommendations&amp;nbsp;to increase DS scalability.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;STRONG&gt;&lt;SPAN class="s1"&gt;On the DS server.conf&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;[sslConfig]&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;sslServerSessionTimeout = 7200&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;[httpServer]&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;dedicatedIoThreads = 10&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p2"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Set following config to 512.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;In $SPLUNK_HOME/etc/splunk-launch.conf on DS.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;SPLUNK_LISTEN_BACKLOG = 512&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Note:&amp;nbsp;Make sure linux net.core.somaxconn setting is more than SPLUNK_LISTEN_BACKLOG.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p2"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;STRONG&gt;&lt;SPAN class="s1"&gt;On DC side&amp;nbsp; server.conf&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;[sslConfig]&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;useSslClientSessionCache=true&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Upgrade all DC to 7.1.3 and above to have configurable and higher default DC timeouts. Before 7.1.3 these are hardcoded 5 sec.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;connect_timeout = &amp;lt;positive integer&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;* Default: 60&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;send_timeout = &amp;lt;positive integer&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;* Default: 60&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;recv_timeout = &amp;lt;positive integer&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;* Default: 60&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Apr 2021 19:10:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Slow-Unresponsive-Deployment-Server-Deployment-Clients-timing/m-p/546745#M18723</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2021-04-05T19:10:06Z</dc:date>
    </item>
  </channel>
</rss>

