<?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: Poor indexing rate in indexer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Poor-indexing-rate-in-indexer/m-p/191282#M38070</link>
    <description>&lt;P&gt;Sometimes a forwarder app is accidentally deployed to an indexer. It is normally limited by the throughput of network bandwidth. &lt;/P&gt;

&lt;P&gt;[thruput]&lt;BR /&gt;
maxKBps = 256&lt;/P&gt;

&lt;P&gt;Please try to use the command ./splunk cmd btool limits list thruput to check if the maxKBps is set to 0. Otherwise indexing rate of an indexer will be limited and not fully utilized the IO rate of the disk system. &lt;/P&gt;

&lt;P&gt;You may also refer the link below showing that index_thruput is controlled by thruput value. &lt;BR /&gt;
&lt;A href="http://wiki.splunk.com/Community:HowIndexingWorks"&gt;http://wiki.splunk.com/Community:HowIndexingWorks&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 12 Jan 2015 07:12:21 GMT</pubDate>
    <dc:creator>mwong</dc:creator>
    <dc:date>2015-01-12T07:12:21Z</dc:date>
    <item>
      <title>Poor indexing rate in indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Poor-indexing-rate-in-indexer/m-p/191281#M38069</link>
      <description>&lt;P&gt;In SoS app, it is found that the indexing rate is limited to about 200Kb/s. &lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2015 07:00:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Poor-indexing-rate-in-indexer/m-p/191281#M38069</guid>
      <dc:creator>mwong</dc:creator>
      <dc:date>2015-01-12T07:00:03Z</dc:date>
    </item>
    <item>
      <title>Re: Poor indexing rate in indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Poor-indexing-rate-in-indexer/m-p/191282#M38070</link>
      <description>&lt;P&gt;Sometimes a forwarder app is accidentally deployed to an indexer. It is normally limited by the throughput of network bandwidth. &lt;/P&gt;

&lt;P&gt;[thruput]&lt;BR /&gt;
maxKBps = 256&lt;/P&gt;

&lt;P&gt;Please try to use the command ./splunk cmd btool limits list thruput to check if the maxKBps is set to 0. Otherwise indexing rate of an indexer will be limited and not fully utilized the IO rate of the disk system. &lt;/P&gt;

&lt;P&gt;You may also refer the link below showing that index_thruput is controlled by thruput value. &lt;BR /&gt;
&lt;A href="http://wiki.splunk.com/Community:HowIndexingWorks"&gt;http://wiki.splunk.com/Community:HowIndexingWorks&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2015 07:12:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Poor-indexing-rate-in-indexer/m-p/191282#M38070</guid>
      <dc:creator>mwong</dc:creator>
      <dc:date>2015-01-12T07:12:21Z</dc:date>
    </item>
  </channel>
</rss>

