Monitoring Splunk

What is the difference between the two threads limits referenced in splunkd.log?

faol
Explorer

I set the maxThreads parameter in my server.conf file based upon the documentation http://docs.splunk.com/Documentation/Splunk/6.2.4/admin/Serverconf . After restarting Splunk, I see the number I set in the splunkd.log file in the following line.

08-03-2015 11:59:17.433 -0700 INFO loader - Limiting REST HTTP server to xxxx threads

I also noticed another setting which sets the maximum number of threads which has a different value.

08-03-2015 11:59:14.046 -0700 INFO loader - Maximum number of threads (approximate): yyyy

What is the difference between these, and how can I increase the latter?

0 Karma
1 Solution

bpaul_splunk
Splunk Employee
Splunk Employee

The maxThreads setting configures the number of threads the Splunk REST server can use. The maximum number of available threads referenced is acquired by Splunk from the host computer. It is derived from a number of different calculations based upon the memory of the system, and supersedes the maxThreads setting.

To increase the total maximum number of available threads Splunk can use, it is essential to increase the memory of the computer on which Splunk in running.

View solution in original post

bpaul_splunk
Splunk Employee
Splunk Employee

The maxThreads setting configures the number of threads the Splunk REST server can use. The maximum number of available threads referenced is acquired by Splunk from the host computer. It is derived from a number of different calculations based upon the memory of the system, and supersedes the maxThreads setting.

To increase the total maximum number of available threads Splunk can use, it is essential to increase the memory of the computer on which Splunk in running.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...