<?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: Splunk ES Datamodel Constantly Rebuilding in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Splunk-ES-Datamodel-Constantly-Rebuilding/m-p/239931#M4833</link>
    <description>&lt;P&gt;Even if someone could,tell me where data model operations log to I could look into that.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Sep 2015 21:05:48 GMT</pubDate>
    <dc:creator>domenico_perre</dc:creator>
    <dc:date>2015-09-25T21:05:48Z</dc:date>
    <item>
      <title>Splunk ES Datamodel Constantly Rebuilding</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-ES-Datamodel-Constantly-Rebuilding/m-p/239930#M4832</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;I have a problem that has been giving me a bit of grief with ES.  Essentially my larger datamodels (Authentication / Network) never seem to get over 10% before restarting at 0%.  I am running 2 clustered indexers and a dedicated SH for ES.&lt;/P&gt;

&lt;P&gt;I have confirmed that there are no lookup table errors, uninstalled all apps that are not being used, disabled correlation searches that I don't have data for and disabled data models that I don't have data for.&lt;/P&gt;

&lt;P&gt;I must admit that I am running VM's with 8 CPUs each idx and ES.  When ES is not running, the idxs run at around 3-10% cpu then spike up to 100% when it is started. I know I am technically not supported because the lack of cpu, but would like to know if there is anything else I can look for?&lt;/P&gt;

&lt;P&gt;Thx in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2015 11:38:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-ES-Datamodel-Constantly-Rebuilding/m-p/239930#M4832</guid>
      <dc:creator>domenico_perre</dc:creator>
      <dc:date>2015-09-25T11:38:56Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ES Datamodel Constantly Rebuilding</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-ES-Datamodel-Constantly-Rebuilding/m-p/239931#M4833</link>
      <description>&lt;P&gt;Even if someone could,tell me where data model operations log to I could look into that.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2015 21:05:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-ES-Datamodel-Constantly-Rebuilding/m-p/239931#M4833</guid>
      <dc:creator>domenico_perre</dc:creator>
      <dc:date>2015-09-25T21:05:48Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ES Datamodel Constantly Rebuilding</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-ES-Datamodel-Constantly-Rebuilding/m-p/239932#M4834</link>
      <description>&lt;P&gt;So I will answer my own question.&lt;/P&gt;

&lt;P&gt;The issue I had was related to the total time it took to build a Datamodel. As it was attempting to build for over an hour it would rerun and wipe the data model.  I edited the datamodels.conf relating to the DMs that were taking the longest with the following&lt;/P&gt;

&lt;P&gt;acceleration.max_time = 86400&lt;/P&gt;

&lt;P&gt;This is probably due to my underspecced indexers but was an adequate solution imo.&lt;/P&gt;

&lt;P&gt;Most DMs are 100% completed and CPU has dropped &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 27 Sep 2015 19:50:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-ES-Datamodel-Constantly-Rebuilding/m-p/239932#M4834</guid>
      <dc:creator>domenico_perre</dc:creator>
      <dc:date>2015-09-27T19:50:32Z</dc:date>
    </item>
  </channel>
</rss>

