Deployment Architecture

In 5.0.2, Is the distsearch.conf attribute: removedTimedOutServers valid?

Ellen
Splunk Employee
Splunk Employee

I just upgraded from 4.2.4 to 5.0.2 and see this message whenever I start up Splunk
It no longer appears in the default distsearch.conf or distsearch.conf.spec in 5.0.2.

Is that an error or something else replaced it?

Possible typo in stanza [distributedSearch] in /opt/splunk/etc/system/local/distsearch.conf, line 5: removedTimedOutServers = 1 
Tags (1)
0 Karma

Ellen
Splunk Employee
Splunk Employee

This is not an error and there is no replacement.

In 5.0.2 the distsearch.conf attribute,
"removedTimedOutServers = false" was removed since it is not a valid setting.

While this was listed in previous 4.x distsearch.conf as a default setting that could be configurable, it was not an attribute that was in use.
Its reference was finally removed starting in 5.0.2 under SPL-56966

[distributedSearch]
removedTimedOutServers = false

If you do have "removedTimedOutServers" configured in your local distsearch.conf, this can be safely removed.

krugger
Communicator

I upgraded from 4.x to 5.0.2 and when I create a new search peer this invalid setting is added.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...