<?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: Data lost - splunk reload deploy-server in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Data-lost-splunk-reload-deploy-server/m-p/546721#M18720</link>
    <description>&lt;P&gt;Thank you for the suggestion, I will have to do some reading into these components and how to configure them, I currently do not have clustered search heads or indexers replicating the data so i did not think they were required.&amp;nbsp; It provides me with a direction to investigate, thank you!&lt;/P&gt;</description>
    <pubDate>Mon, 05 Apr 2021 15:19:25 GMT</pubDate>
    <dc:creator>rlaan</dc:creator>
    <dc:date>2021-04-05T15:19:25Z</dc:date>
    <item>
      <title>Data lost - splunk reload deploy-server</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Data-lost-splunk-reload-deploy-server/m-p/546420#M18716</link>
      <description>&lt;P&gt;I noticed that when pushing configuration changed from the deployment-servers to addition compoents (U-forwarders, H-forwarders, indexers, search heads) via the "splunk reload deploy-server" command that there were small 20-25 sec periods of missing data ingest.&lt;BR /&gt;&lt;BR /&gt;I was under the impression that after these configuration pushes that splunk would catch-up or re-index&amp;nbsp; the data during the change. It appears that this is not the case after having to explain some missing data gaps.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;How can i push configuration changes without causing a loss of data ingest (working with busy access_combined/apache access logs so a few hundred events are missed during a 20 second window)&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Additionally, i have the full log files, is there a way to only re-index non-repeat events, i feel trying to delete the existing logs via splunk search and re-indexing with a "oneshot" method would be very time consuming over many servers.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 19:05:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Data-lost-splunk-reload-deploy-server/m-p/546420#M18716</guid>
      <dc:creator>rlaan</dc:creator>
      <dc:date>2021-04-01T19:05:50Z</dc:date>
    </item>
    <item>
      <title>Re: Data lost - splunk reload deploy-server</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Data-lost-splunk-reload-deploy-server/m-p/546533#M18719</link>
      <description>&lt;P&gt;It sounds like your Splunk architecture could use some improvements.&amp;nbsp; While it can be done, it's not typical (or recommended) to use the DS to manage all instance types.&amp;nbsp; The DS is designed to manage forwarders.&lt;/P&gt;&lt;P&gt;The search heads probably should be in a cluster and managed by a SHC Deployer.&lt;/P&gt;&lt;P&gt;More importantly, however, the indexers should be clustered and managed by a Manager Node (MN).&amp;nbsp; The MN will push apps to the indexers and contol when they restart to ensure at least one is available to receive data at all times.&lt;/P&gt;&lt;P&gt;Make sure all forwarders have the names (or IP addresses) of all indexers.&amp;nbsp; That way the forwarder can send data to another indexer if one is unavailable.&amp;nbsp; Consider using the Indexer Discovery feature where the forwarders get the list of indexers from the MN.&amp;nbsp; That will avoid having to update the forwarders when an indexer is added or removed.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Apr 2021 13:01:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Data-lost-splunk-reload-deploy-server/m-p/546533#M18719</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-04-02T13:01:24Z</dc:date>
    </item>
    <item>
      <title>Re: Data lost - splunk reload deploy-server</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Data-lost-splunk-reload-deploy-server/m-p/546721#M18720</link>
      <description>&lt;P&gt;Thank you for the suggestion, I will have to do some reading into these components and how to configure them, I currently do not have clustered search heads or indexers replicating the data so i did not think they were required.&amp;nbsp; It provides me with a direction to investigate, thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 05 Apr 2021 15:19:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Data-lost-splunk-reload-deploy-server/m-p/546721#M18720</guid>
      <dc:creator>rlaan</dc:creator>
      <dc:date>2021-04-05T15:19:25Z</dc:date>
    </item>
  </channel>
</rss>

