<?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: The splunk-system-user is hitting a quota limit.  How do I increase the quota for this user? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/The-splunk-system-user-is-hitting-a-quota-limit-How-do-I/m-p/11306#M145107</link>
    <description>&lt;P&gt;Note that when scheduled search does not have an owner, it is run by splunk-system-user.&lt;/P&gt;

&lt;P&gt;The splunk-system-user seems to have a hardcoded quota.  &lt;/P&gt;

&lt;P&gt;Therefore, you'll need to assign an owner/user to the scheduled search and specify a role for the user.  This is because there isn't a way to set a per-user disk quota so you'll have to edit the role to increase this limit.  Here are the defaults from $SPLUNK_HOME/etc/system/default/authorize.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[role_admin]
srchDiskQuota = 10000

[role_power]
srchDiskQuota = 500

[role_user]
srchDiskQuota = 100
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;(System-wide default is 100 MB which will be applied to all roles where a srchDiskQuota is not specified)&lt;/P&gt;

&lt;P&gt;Best way is probably to create a custom role and assign it to this user rather than edit the defaults for the canned roles.  Create your custom role in $SPLUNK_HOME/etc/system/local/authorize.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[role_quota]
srchDiskQuota = 5000
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 13 Apr 2010 18:48:17 GMT</pubDate>
    <dc:creator>the_wolverine</dc:creator>
    <dc:date>2010-04-13T18:48:17Z</dc:date>
    <item>
      <title>The splunk-system-user is hitting a quota limit.  How do I increase the quota for this user?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/The-splunk-system-user-is-hitting-a-quota-limit-How-do-I/m-p/11305#M145106</link>
      <description>&lt;P&gt;I'm running summary searches and the splunk-system-user keeps hitting a quota limit.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  04-12-2010 16:50:28.436 ERROR SavedSplunker - 
  Maximum disk usage=10422MB quota=10000MB, reached. Search not executed. 
  SearchId=scheduler_nobody_myapp_custom_summary_searchname
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I'm only running summary searches on this host so I want to give the splunk-system-user free reign.  How can I increase the quota for just the splunk-system-user?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2010 18:29:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/The-splunk-system-user-is-hitting-a-quota-limit-How-do-I/m-p/11305#M145106</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2010-04-13T18:29:37Z</dc:date>
    </item>
    <item>
      <title>Re: The splunk-system-user is hitting a quota limit.  How do I increase the quota for this user?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/The-splunk-system-user-is-hitting-a-quota-limit-How-do-I/m-p/11306#M145107</link>
      <description>&lt;P&gt;Note that when scheduled search does not have an owner, it is run by splunk-system-user.&lt;/P&gt;

&lt;P&gt;The splunk-system-user seems to have a hardcoded quota.  &lt;/P&gt;

&lt;P&gt;Therefore, you'll need to assign an owner/user to the scheduled search and specify a role for the user.  This is because there isn't a way to set a per-user disk quota so you'll have to edit the role to increase this limit.  Here are the defaults from $SPLUNK_HOME/etc/system/default/authorize.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[role_admin]
srchDiskQuota = 10000

[role_power]
srchDiskQuota = 500

[role_user]
srchDiskQuota = 100
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;(System-wide default is 100 MB which will be applied to all roles where a srchDiskQuota is not specified)&lt;/P&gt;

&lt;P&gt;Best way is probably to create a custom role and assign it to this user rather than edit the defaults for the canned roles.  Create your custom role in $SPLUNK_HOME/etc/system/local/authorize.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[role_quota]
srchDiskQuota = 5000
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 13 Apr 2010 18:48:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/The-splunk-system-user-is-hitting-a-quota-limit-How-do-I/m-p/11306#M145107</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2010-04-13T18:48:17Z</dc:date>
    </item>
  </channel>
</rss>

