https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213852#M62717 <P>@sbattista09 - Were you able to find a solution to your question? If yes, was it somesoni2's link or GregMefford's answer? If no solution was found still, please feel free to leave a comment with more information.</P> Mon, 28 Nov 2016 23:30:14 GMT aaraneta_splunk 2016-11-28T23:30:14Z https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213849#M62714 <P>heyyyy everyone, anyone run into this annoying message before? </P> <P>we keep getting this after moving to a search head cluster</P> <BLOCKQUOTE> <P>"The system is approaching the<BR /> maximum number of historical searches<BR /> that can be run concurrently.<BR /> current=blahhh maximum=blahhahhh"</P> </BLOCKQUOTE> Mon, 07 Nov 2016 18:37:31 GMT https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213849#M62714 sbattista09 2016-11-07T18:37:31Z https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213850#M62715 <P>The <CODE>current</CODE> number should be pretty straightforward to determine whether it's reasonable or not. The <CODE>maximum</CODE> is normally determined roughly by the number of cores on the search head unless you have changed you parallelization settings ( <CODE>batch_search_max_pipeline</CODE> setting in <CODE>limits.conf</CODE>).</P> <P><A href="http://docs.splunk.com/Documentation/Splunk/6.5.0/Capacity/Parallelization">http://docs.splunk.com/Documentation/Splunk/6.5.0/Capacity/Parallelization</A></P> <P>Maybe your SHC has less cores per server than your previously stand-alone Search Head?<BR /> You can also look in the Distribute Management Center to see the number of concurrent historical searches over time.</P> <P>For example, if you open a dashboard with a dozen panels that are each running an independent search, that counts as 12.</P> Mon, 07 Nov 2016 20:55:55 GMT https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213850#M62715 GregMefford 2016-11-07T20:55:55Z https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213851#M62716 <P>See this</P> <P><A href="https://answers.splunk.com/answers/337598/search-head-cluster-pre-63-we-could-run-more-numbe-2.html">https://answers.splunk.com/answers/337598/search-head-cluster-pre-63-we-could-run-more-numbe-2.html</A></P> Mon, 07 Nov 2016 20:56:42 GMT https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213851#M62716 somesoni2 2016-11-07T20:56:42Z https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213852#M62717 <P>@sbattista09 - Were you able to find a solution to your question? If yes, was it somesoni2's link or GregMefford's answer? If no solution was found still, please feel free to leave a comment with more information.</P> Mon, 28 Nov 2016 23:30:14 GMT https://community.splunk.com/t5/Splunk-Search/How-to-resolve-quot-approaching-the-maximum-number-of-historical/m-p/213852#M62717 aaraneta_splunk 2016-11-28T23:30:14Z