<?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: Best recommendation for serach head cluster load balancer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668332#M112022</link>
    <description>&lt;P&gt;Load balancers help the SHC perform better by evenly distributing users among all nodes.&lt;/P&gt;</description>
    <pubDate>Sat, 11 Nov 2023 21:32:32 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-11-11T21:32:32Z</dc:date>
    <item>
      <title>Best recommendation for serach head cluster load balancer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668314#M112018</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have deployed a search head cluster with 3 members and one deployer. based on splunk document, is recommends that run a third-party hardware or software load balancer in front of the clustered search heads.&lt;/P&gt;&lt;P&gt;does splunk recommend any special load balancer that is most compatible&lt;/P&gt;</description>
      <pubDate>Sat, 11 Nov 2023 11:51:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668314#M112018</guid>
      <dc:creator>maede_yavari</dc:creator>
      <dc:date>2023-11-11T11:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: Best recommendation for serach head cluster load balancer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668316#M112019</link>
      <description>&lt;P&gt;Splunk does not recommend any specific load balancer.&amp;nbsp; They specify only that the LB employ layer-7 (application-level) processing and user sessions are "sticky" or "persistent."&lt;/P&gt;</description>
      <pubDate>Sat, 11 Nov 2023 13:03:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668316#M112019</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-11-11T13:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: Best recommendation for serach head cluster load balancer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668317#M112020</link>
      <description>&lt;P data-unlink="true"&gt;Hi Richgalloway,&lt;/P&gt;&lt;P data-unlink="true"&gt;Thanks for your reply.&lt;/P&gt;&lt;P data-unlink="true"&gt;I consider HAProxy for that because I've had some experience about it. But I want to add LB several month later. does it maybe have some bad effect on the cluster performance? or create some fault on the search process?&lt;/P&gt;&lt;P data-unlink="true"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 11 Nov 2023 13:50:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668317#M112020</guid>
      <dc:creator>maede_yavari</dc:creator>
      <dc:date>2023-11-11T13:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: Best recommendation for serach head cluster load balancer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668332#M112022</link>
      <description>&lt;P&gt;Load balancers help the SHC perform better by evenly distributing users among all nodes.&lt;/P&gt;</description>
      <pubDate>Sat, 11 Nov 2023 21:32:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-recommendation-for-serach-head-cluster-load-balancer/m-p/668332#M112022</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-11-11T21:32:32Z</dc:date>
    </item>
  </channel>
</rss>

