<?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 auto-cancelled in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742194#M240795</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/308648"&gt;@hema_5757&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There could be a number of reasons your search is auto-cancelling:&lt;/P&gt;&lt;P&gt;1) The SH does not have enough RAM. Can you confirm how much RAM the SH has, and how much is free during the search?&lt;/P&gt;&lt;P&gt;2) Certain savedsearches.conf properties can affect the amount of time and/or number of results that might return (&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Savedsearchesconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/Savedsearchesconf&lt;/A&gt;) such as:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dispatch.max_count = &amp;lt;integer&amp;gt;
* The maximum number of results before finalizing the search.
* Defaults to 500000.

dispatch.max_time = &amp;lt;integer&amp;gt;
* Indicates the maximum amount of time (in seconds) before finalizing the
  search.
* Defaults to 0.

dispatch.auto_cancel = &amp;lt;integer&amp;gt;
* Specifies the amount of inactive time, in seconds, after which the job
  is automatically canceled.
* 0 means to never auto-cancel the job.
* Default: 0  &lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please review these in your environment to see if this could be impacting.&lt;/P&gt;&lt;P&gt;3) Workload management (WLM) - Are your searches subject to WLM policies?&lt;/P&gt;&lt;P&gt;4) Check the job inspector, if you look at the search.log from within the job inspector for things like cancel/fail/error etc and see if there is more information that you can share with us it might help investigate further.&lt;/P&gt;&lt;P&gt;Please let me know how you get on and consider adding karma to this or any other answer if it has helped.&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Will&lt;/P&gt;</description>
    <pubDate>Wed, 19 Mar 2025 13:26:18 GMT</pubDate>
    <dc:creator>livehybrid</dc:creator>
    <dc:date>2025-03-19T13:26:18Z</dc:date>
    <item>
      <title>Search auto-cancelled</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742188#M240794</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have following Query&amp;nbsp;&lt;/P&gt;&lt;P&gt;index=wineventlog&lt;BR /&gt;|eval _time = strftime(_time,"%Y-%m-%d %H:%M:%S") |eval device_name = lower(Workstation_Name)|dedup device_name | table _time user device_name src_nt_host action ComputerName host SourceName Account_Name Security_ID Logon_Type TaskCategory Type app eventtype product vendor vendor_product Account_Domain dest dest_nt_domain dest_nt_host Error_Code EventCode EventType name source SourceName sourcetype src src_domain src_ip src_nt_domain src_port Virtual_Account LogName Logon_GUID Impersonation_Level&lt;/P&gt;&lt;P&gt;on Yesterday time filter&lt;/P&gt;&lt;P&gt;This search takes more than one hour and when I use this query to output search It process till 60% and then it is giving error like search auto-cancelled. Is there any way that we can handle time for processing this query. or how can I get data in other ways.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I give shorted timeframe like last 60 min time takes almost 5 min and I can get data. Please suggest.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 12:45:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742188#M240794</guid>
      <dc:creator>hema_5757</dc:creator>
      <dc:date>2025-03-19T12:45:21Z</dc:date>
    </item>
    <item>
      <title>Re: Search auto-cancelled</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742194#M240795</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/308648"&gt;@hema_5757&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There could be a number of reasons your search is auto-cancelling:&lt;/P&gt;&lt;P&gt;1) The SH does not have enough RAM. Can you confirm how much RAM the SH has, and how much is free during the search?&lt;/P&gt;&lt;P&gt;2) Certain savedsearches.conf properties can affect the amount of time and/or number of results that might return (&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Savedsearchesconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/Savedsearchesconf&lt;/A&gt;) such as:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dispatch.max_count = &amp;lt;integer&amp;gt;
* The maximum number of results before finalizing the search.
* Defaults to 500000.

dispatch.max_time = &amp;lt;integer&amp;gt;
* Indicates the maximum amount of time (in seconds) before finalizing the
  search.
* Defaults to 0.

dispatch.auto_cancel = &amp;lt;integer&amp;gt;
* Specifies the amount of inactive time, in seconds, after which the job
  is automatically canceled.
* 0 means to never auto-cancel the job.
* Default: 0  &lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please review these in your environment to see if this could be impacting.&lt;/P&gt;&lt;P&gt;3) Workload management (WLM) - Are your searches subject to WLM policies?&lt;/P&gt;&lt;P&gt;4) Check the job inspector, if you look at the search.log from within the job inspector for things like cancel/fail/error etc and see if there is more information that you can share with us it might help investigate further.&lt;/P&gt;&lt;P&gt;Please let me know how you get on and consider adding karma to this or any other answer if it has helped.&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Will&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 13:26:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742194#M240795</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2025-03-19T13:26:18Z</dc:date>
    </item>
    <item>
      <title>Re: Search auto-cancelled</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742196#M240797</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/308648"&gt;@hema_5757&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;your search is very long, so the only way to avoid timeouts like your is to send the job in background [Job &amp;gt; Send Job to background].&lt;BR /&gt;eventually adding an email to receive the completion of the job.&lt;/P&gt;&lt;P&gt;Then remember that you have the limit of 10,000 results, so maybe it's better to use more filters if you have too many results.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 13:28:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742196#M240797</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2025-03-19T13:28:42Z</dc:date>
    </item>
    <item>
      <title>Re: Search auto-cancelled</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742200#M240799</link>
      <description>&lt;P&gt;The Search process around 8K results in 400M events&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 13:41:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742200#M240799</guid>
      <dc:creator>hema_5757</dc:creator>
      <dc:date>2025-03-19T13:41:41Z</dc:date>
    </item>
    <item>
      <title>Re: Search auto-cancelled</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742202#M240800</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/308648"&gt;@hema_5757&lt;/a&gt;&amp;nbsp; did you see my response with other options under the other reply?&lt;/P&gt;&lt;P&gt;Please let me know how you get on and consider adding karma to this or any other answer if it has helped.&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Will&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 13:44:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-auto-cancelled/m-p/742202#M240800</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2025-03-19T13:44:51Z</dc:date>
    </item>
  </channel>
</rss>

