<?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 8.0.2 report acceleration broken for reports using inputlookup command in subsearches in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/525858#M8545</link>
    <description>&lt;P&gt;Issue not fixed in Splunk Enterprise 8.1.0&lt;/P&gt;</description>
    <pubDate>Wed, 21 Oct 2020 16:26:21 GMT</pubDate>
    <dc:creator>orion44</dc:creator>
    <dc:date>2020-10-21T16:26:21Z</dc:date>
    <item>
      <title>Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472290#M7577</link>
      <description>&lt;P&gt;Prior to updating to Splunk Enterprise 8.0.2 scheduled accelerated reports ran extremely fast:&lt;BR /&gt;Report A&lt;BR /&gt;Duration: 37.166&lt;BR /&gt;Record count: 314&lt;/P&gt;
&lt;P&gt;After updating to Splunk Enterprise 8.0.2 the report ran extremely slow:&lt;BR /&gt;Report A&lt;BR /&gt;Duration: 418.621&lt;BR /&gt;Record count: 300&lt;/P&gt;
&lt;P&gt;Given the &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.2/ReleaseNotes/MeetSplunk" target="_blank" rel="noopener"&gt;patch notes&lt;/A&gt; for 8.0.2 – I'm not seeing any changes to acceleration or summary indexing, so is it safe to assume this is a fluke?&lt;/P&gt;
&lt;P&gt;The massive increase in report generation (job) time of the scheduled accelerated reports appears to be caused by them no longer accessing the corresponding report acceleration summary. The "Access Count" never goes up when the scheduled reports are run.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/8398iE10F4D93D0C9ABA2/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Guess we'll wait for 8.0.3 to fix this.&lt;/P&gt;
&lt;P&gt;Troubleshooting steps attempted:&lt;BR /&gt;Manually rebuild Report Acceleration Summaries&lt;BR /&gt;Delete all affected Report Acceleration Summaries&lt;BR /&gt;Delete and recreate affected production reports – recreated schedule and checked box for acceleration&lt;BR /&gt;Check filesystem permissions of inputlookup csv - confirmed &lt;CODE&gt;-rw-rw-r--  splunk splunk&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2020 23:34:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472290#M7577</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-06-08T23:34:49Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472291#M7578</link>
      <description>&lt;P&gt;Did you migrate the scheduled report or recreate it?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2020 20:47:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472291#M7578</guid>
      <dc:creator>codebuilder</dc:creator>
      <dc:date>2020-02-14T20:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472292#M7579</link>
      <description>&lt;P&gt;Total delete and recreate the report, schedule, acceleration, and the corresponding report acceleration summary.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2020 21:21:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472292#M7579</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-02-14T21:21:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472293#M7580</link>
      <description>&lt;P&gt;After further testing, it appears that reports that use  &lt;CODE&gt;inputlookup&lt;/CODE&gt; commands no longer accelerate correctly after the Splunk Enterprise 8.0.2 update. I reached this conclusion by removing the  &lt;CODE&gt;inputlookup&lt;/CODE&gt; command from the two reports mentioned above in my question – then hardcoded a few example values into my Splunk search query to test.&lt;/P&gt;

&lt;P&gt;After doing so, the report acceleration performed as expected. Sadly this isn't a solution and only a workaround until the issue is (hopefully) fixed in future Splunk Enterprise releases.&lt;/P&gt;

&lt;P&gt;CONFIRMED&lt;BR /&gt;
Splunk 8.0.2 caused report acceleration to break. I was able to correct the issue by rolling back to version 8.0.1 via the steps below:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;wget -O splunk-8.0.1-6db836e2fb9e-linux-2.6-x86_64.rpm 'https://www.splunk.com/bin/splunk/DownloadActivityServlet?architecture=x86_64&amp;amp;platform=linux&amp;amp;version=8.0.1&amp;amp;product=splunk&amp;amp;filename=splunk-8.0.1-6db836e2fb9e-linux-2.6-x86_64.rpm&amp;amp;wget=true'

sudo rpm -Uvh --oldpackage splunk-8.0.1-6db836e2fb9e-linux-2.6-x86_64.rpm

sudo service splunk start
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 15 Feb 2020 20:36:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472293#M7580</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-02-15T20:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472294#M7581</link>
      <description>&lt;P&gt;Did you log a support case? As that way the support team will actually confirm that its a bug/fix the issue in a future release...&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2020 06:11:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472294#M7581</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2020-02-17T06:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472295#M7582</link>
      <description>&lt;P&gt;"It appears you do not have an active Support Contract or entitlement and as a result, cannot open a Support case. If you believe this is an error, please contact 1-855-SPLUNK S, or consult &lt;A href="https://www.splunk.com/en_us/about-us/contact.html#customer-support"&gt;https://www.splunk.com/en_us/about-us/contact.html#customer-support&lt;/A&gt; for a country specific Support phone number and we can resolve any contractual data integrity issues."&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2020 17:55:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472295#M7582</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-02-17T17:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472296#M7583</link>
      <description>&lt;P&gt;Oh ok, if your not on a customer site you cannot raise an issue, if i get spare time I'll try it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2020 22:26:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472296#M7583</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2020-02-17T22:26:13Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472297#M7584</link>
      <description>&lt;P&gt;It could, that would be greatly appreciated. Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 18 Feb 2020 03:12:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472297#M7584</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-02-18T03:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472298#M7585</link>
      <description>&lt;P&gt;What's the search? &lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2020 10:14:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472298#M7585</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2020-02-19T10:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472299#M7586</link>
      <description>&lt;P&gt;Outside of the &lt;CODE&gt;inputlookup&lt;/CODE&gt; command the search itself is irrelevant. Once I remove the reference to &lt;CODE&gt;inputlookup&lt;/CODE&gt; command from the search and hardcode a few examples from the csv – the search accelerates as expected.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2020 20:22:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472299#M7586</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-02-19T20:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472300#M7587</link>
      <description>&lt;P&gt;It would be useful to know which version you were on before when it was working, and whether the inputlookup is done as a subsearch.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2020 00:18:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472300#M7587</guid>
      <dc:creator>nvanderwalt_spl</dc:creator>
      <dc:date>2020-02-20T00:18:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472301#M7588</link>
      <description>&lt;P&gt;Version 8.0.1 was used prior to the issue starting after upgrading to 8.0.2. The &lt;CODE&gt;inputlookup&lt;/CODE&gt; function used is &lt;CODE&gt;[| inputlookup filename.csv | fields name1 | rename name1 as my_search_value | format]&lt;/CODE&gt; and comes after &lt;CODE&gt;index=index_name&lt;/CODE&gt; in the search query.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2020 08:22:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472301#M7588</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-02-20T08:22:37Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472302#M7589</link>
      <description>&lt;P&gt;Downgrading to 8.0.1 resulted in acceleration working correctly again. Do you know if there's a full list of changes in 8.0.2 that we can review for a possible cause?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 23:17:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472302#M7589</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-02-21T23:17:41Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472303#M7590</link>
      <description>&lt;P&gt;Were you able to report a support case? Has anyone else reported this issue?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2020 18:56:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472303#M7590</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-02-26T18:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472304#M7591</link>
      <description>&lt;P&gt;Will try and replicate it today...where does the summarisation load screen come from?&lt;/P&gt;</description>
      <pubDate>Mon, 02 Mar 2020 22:33:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472304#M7591</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2020-03-02T22:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472305#M7592</link>
      <description>&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;It can be found at &lt;A href="https://:8000/en-US/manager/system/summarization" target="test_blank"&gt;https://:8000/en-US/manager/system/summarization&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 00:05:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472305#M7592</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-03-03T00:05:14Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472306#M7593</link>
      <description>&lt;P&gt;So I did this, search 1:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal | stats count by _time
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Search 2:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal | stats count by _time | inputlookup append=true rest_api_test.csv
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Report acceleration confirms they will both use the same acceleration job.&lt;BR /&gt;
When I run the reports they advise they both used the same acceleration job.&lt;/P&gt;

&lt;P&gt;So did not replicate it, is that similar to what you are doing?&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 01:19:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472306#M7593</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2020-03-03T01:19:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472307#M7594</link>
      <description>&lt;P&gt;Schedule the second search you created to run at some interval and see if the "Access Count" number increases after each scheduled report runs. In my case, the count doesn't go up and the report generates slowly – despite showing that it is using the acceleration (summary) index on the Report Acceleration Summaries page.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 01:28:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472307#M7594</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-03-03T01:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472308#M7595</link>
      <description>&lt;P&gt;And is the summary showing as complete? Perhaps the summary is not in a usable state yet?&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 02:32:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472308#M7595</guid>
      <dc:creator>nvanderwalt_spl</dc:creator>
      <dc:date>2020-03-03T02:32:07Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 8.0.2 report acceleration broken for reports using inputlookup command in subsearches</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472309#M7596</link>
      <description>&lt;P&gt;Yes, the summary was 100% complete as shown in OP screenshot. Prior to the 8.0.2 upgrade the report acceleration was working as intended.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 02:47:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-8-0-2-report-acceleration-broken-for-reports-using/m-p/472309#M7596</guid>
      <dc:creator>orion44</dc:creator>
      <dc:date>2020-03-03T02:47:42Z</dc:date>
    </item>
  </channel>
</rss>

