With version 6.0 these parameters, it restricted the amount of file open. when i changed server.conf to
[httpServer]
maxThreads = -1
maxSockets = -1
Splunk unable to parse the negative number, what is correct syntax to "no limit will be enforced"
maxThreads =
* Number of threads that can be used by active HTTP transactions.
This can be limited to constrain resource usage.
* If set to 0 (the default) a limit will be automatically picked
based on estimated server capacity.
* If set to a negative number, no limit will be enforced.
maxSockets =
* Number of simultaneous HTTP connections that we'll accept simultaneously.
This can be limited to constrain resource usage.
* If set to 0 (the default) a limit will be automatically picked
based on estimated server capacity.
* If set to a negative number, no limit will be enforced.
Clarified the stanza in the question.
For clarity, dumbo me, what stanza are these in?
"-1" is the correct setting for an unbounded maxThreads
or maxSockets
, but it was broken for a bit due to bug SPL-82389.
This has been resolved in Splunk Enterprise 6.0.4, which was released today.
The known issues for 6.0.4 is still showing this issue, SPL-82389, as active and not fixed in 6.0.4.
I question the use of unbounded values here, though.
If your system can't operate inside a thousand or so simultaneous sockets/requests then it's just going to run out of system memory, most likely, and fall over.
Any reasonably large number such as 1000000 should work around this, effectively imposing no limit.