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!

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...

Explore the Latest Educational Offerings from Splunk [January 2025 Updates]

At Splunk Education, we are committed to providing a robust learning experience for all users, regardless of ...

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...