<?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: Search Peer down, distsearch.conf in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687913#M28202</link>
    <description>&lt;P&gt;So:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;if our search peers and indexers are synced across properly&lt;/LI&gt;&lt;LI&gt;Distconf has 6 IPs but only 3 of those hosts are up&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Will our master search head cluster be able to still search against the peers? Or if it happens to hit a dead host it will return nothing for that query?&lt;/P&gt;</description>
    <pubDate>Fri, 17 May 2024 17:39:00 GMT</pubDate>
    <dc:creator>SecurityFeller</dc:creator>
    <dc:date>2024-05-17T17:39:00Z</dc:date>
    <item>
      <title>Search Peer down, distsearch.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687901#M28198</link>
      <description>&lt;P&gt;If I have 6 search peers configured in the distsearch.conf file but 3 of them go down, can Splunk recognize that a host is down and continue skipping down the list until it gets a live host?&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 15:23:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687901#M28198</guid>
      <dc:creator>SecurityFeller</dc:creator>
      <dc:date>2024-05-17T15:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: Search Peer down, distsearch.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687912#M28201</link>
      <description>&lt;P&gt;Unlike a forwarder sending data to a peer, search heads do not round-robin among the indexers.&amp;nbsp; Search queries are sent to all (most of the time) indexers and the responses are collated by the SH.&amp;nbsp; If the data on the 3 down peers is not replicated on the remaining 3 then you will get incomplete search results.&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 17:13:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687912#M28201</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-05-17T17:13:01Z</dc:date>
    </item>
    <item>
      <title>Re: Search Peer down, distsearch.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687913#M28202</link>
      <description>&lt;P&gt;So:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;if our search peers and indexers are synced across properly&lt;/LI&gt;&lt;LI&gt;Distconf has 6 IPs but only 3 of those hosts are up&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Will our master search head cluster be able to still search against the peers? Or if it happens to hit a dead host it will return nothing for that query?&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 17:39:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687913#M28202</guid>
      <dc:creator>SecurityFeller</dc:creator>
      <dc:date>2024-05-17T17:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: Search Peer down, distsearch.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687916#M28203</link>
      <description>&lt;P&gt;The Cluster Manager will keep track of where the searchable buckets are in the cluster.&amp;nbsp; If all goes well, you should be able to search with half the cluster still up.&amp;nbsp; It will depend on the search factor and the timing of the indexer failures as to whether the cluster will remain searchable.&amp;nbsp; The Indexer Clustering page on the Cluster Manager will tell you the state of the cluster.&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 17:53:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687916#M28203</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-05-17T17:53:59Z</dc:date>
    </item>
    <item>
      <title>Re: Search Peer down, distsearch.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687917#M28204</link>
      <description>&lt;P&gt;I apologize, I don't believe my question was clear.&lt;/P&gt;&lt;P&gt;I have 2 full fledged splunk deployments, 1 on-prem and 1 in AWS.&lt;/P&gt;&lt;P&gt;The AWS SearchHeads are acting as remote search peers reside to the on-prem deployment. These search peers are hardcoded in the on-prem conf file as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;10.0.0.1&lt;/LI&gt;&lt;LI&gt;10.0.0.2&lt;/LI&gt;&lt;LI&gt;10.0.0.3&lt;/LI&gt;&lt;LI&gt;10.0.0.4&lt;/LI&gt;&lt;LI&gt;10.0.0.5&lt;/LI&gt;&lt;LI&gt;10.0.0.6&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Now if the remote search peers 4-6 go down, will our on-prem splunk solution still be able to query our remote search peers as normal given that the config file has 3 non-live searchpeers&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 18:01:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687917#M28204</guid>
      <dc:creator>SecurityFeller</dc:creator>
      <dc:date>2024-05-17T18:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: Search Peer down, distsearch.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687937#M28207</link>
      <description>&lt;P&gt;Yes, the on-prem search heads will be able to send queries to the AWS indexers.&amp;nbsp; Whether those queries are successful or not is another question the answer to which depends on how the indexers are configured.&amp;nbsp; Are they in a cluster?&amp;nbsp; What are the replication factor and search factor settings?&lt;/P&gt;&lt;P&gt;An indexer cluster with fully replicated and searchable data will be able to respond to search requests even if some peers are down.&amp;nbsp; The likelihood of the cluster being fully searchable goes down with each lost indexers.&amp;nbsp; If the indexers go down in rapid succession then it's possible (depending on the configuration) for some data to be unreachable.&amp;nbsp; In that case, the search requests will return incomplete results.&lt;/P&gt;</description>
      <pubDate>Sat, 18 May 2024 00:04:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Peer-down-distsearch-conf/m-p/687937#M28207</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-05-18T00:04:46Z</dc:date>
    </item>
  </channel>
</rss>

