<?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: Why aren't lookups replicating on search head (SH) cluster? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Why-aren-t-lookups-replicating-on-search-head-SH-cluster/m-p/408579#M14689</link>
    <description>&lt;P&gt;Are you pushing files onto the search head and then expecting the replication to just work?&lt;/P&gt;

&lt;P&gt;If so you might want to send the lookup files through via a REST API call rather than just scp'ing files to the search head server&lt;/P&gt;</description>
    <pubDate>Thu, 11 Oct 2018 22:07:19 GMT</pubDate>
    <dc:creator>gjanders</dc:creator>
    <dc:date>2018-10-11T22:07:19Z</dc:date>
    <item>
      <title>Why aren't lookups replicating on search head (SH) cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-aren-t-lookups-replicating-on-search-head-SH-cluster/m-p/408577#M14687</link>
      <description>&lt;P&gt;I have a 3 node SH cluster. I pushed a custom app from the deployer that had a local folder (just a transforms.conf for 2 lookup tables) and I had a folder with 2 lookup tables. &lt;/P&gt;

&lt;P&gt;The lookup tables are being pushed to SH's via a crontab running on our Enterprise Security. Since this would get overlaid by a bundle push, I removed the lookup folder from the deployer and re-pushed the bundle.&lt;/P&gt;

&lt;P&gt;What I noticed is the lookup tables are not being replicated when they change. I had also noticed that when I removed the folder from the deployer and pushed the bundle, it didn't remove the lookup folder from the 3 SH nodes, which I had expected. My guess is there is something stuck?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2018 16:28:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-aren-t-lookups-replicating-on-search-head-SH-cluster/m-p/408577#M14687</guid>
      <dc:creator>pfabrizi</dc:creator>
      <dc:date>2018-10-04T16:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: Why aren't lookups replicating on search head (SH) cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-aren-t-lookups-replicating-on-search-head-SH-cluster/m-p/408578#M14688</link>
      <description>&lt;P&gt;There might be too much size w.r.t. the lookup table, this might be the reason causing not being replicated.&lt;BR /&gt;
Also, it won't simply remove from the search heads even if you remove from your lookup folder on deployer. There would be a command where it will remove these kind of things from peers, please check with the splunk doc. docs.splunk.com&lt;/P&gt;</description>
      <pubDate>Thu, 11 Oct 2018 17:49:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-aren-t-lookups-replicating-on-search-head-SH-cluster/m-p/408578#M14688</guid>
      <dc:creator>chskm</dc:creator>
      <dc:date>2018-10-11T17:49:04Z</dc:date>
    </item>
    <item>
      <title>Re: Why aren't lookups replicating on search head (SH) cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-aren-t-lookups-replicating-on-search-head-SH-cluster/m-p/408579#M14689</link>
      <description>&lt;P&gt;Are you pushing files onto the search head and then expecting the replication to just work?&lt;/P&gt;

&lt;P&gt;If so you might want to send the lookup files through via a REST API call rather than just scp'ing files to the search head server&lt;/P&gt;</description>
      <pubDate>Thu, 11 Oct 2018 22:07:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-aren-t-lookups-replicating-on-search-head-SH-cluster/m-p/408579#M14689</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2018-10-11T22:07:19Z</dc:date>
    </item>
  </channel>
</rss>

