Dashboards & Visualizations

Refresh props.conf delay

reed_kelly
Contributor

When I modify props.conf in an app on the Search Head, there is usually a delay (20 minutes?) before those changes become effective.
I also keep hitting the URL:

https://server:8000/en-US/debug/refresh

but it still takes a while before the changes are seen.

We have a fairly complex setup with Search heads and indexers, etc..., so I can imagine some delay. Does anyone know if this is normal, and if there is a way to speed this up? Alternatively, is there a way to see when the changes are effective without having to test it directly with a search?

Tags (1)
0 Karma
1 Solution

Drainy
Champion

hmm, it sounds like the replication bundles are taking a while to get sent out, usually the case if you have a large amount of search time objects. A solution might be to try and mount your knowledge objects and instead of the search head distributing them, the peers can mount them so all changes take effect straight away.
From 4.3 onwards the search time extractions in props will be reloaded each time you run a new search, this is done as splunk forks off another splunkd process to handle the search.

Have a look at http://docs.splunk.com/Documentation/Splunk/5.0/admin/Distsearchconf and the part about mounting replication bundles for config details on how to configure. Plus; http://docs.splunk.com/Documentation/Splunk/5.0/Deploy/Mounttheknowledgebundle

View solution in original post

Drainy
Champion

hmm, it sounds like the replication bundles are taking a while to get sent out, usually the case if you have a large amount of search time objects. A solution might be to try and mount your knowledge objects and instead of the search head distributing them, the peers can mount them so all changes take effect straight away.
From 4.3 onwards the search time extractions in props will be reloaded each time you run a new search, this is done as splunk forks off another splunkd process to handle the search.

Have a look at http://docs.splunk.com/Documentation/Splunk/5.0/admin/Distsearchconf and the part about mounting replication bundles for config details on how to configure. Plus; http://docs.splunk.com/Documentation/Splunk/5.0/Deploy/Mounttheknowledgebundle

reed_kelly
Contributor

Thanks Drainy. We are running 4.3.1 on the search heads, but we will have to look at mounted bundles.

0 Karma
Get Updates on the Splunk Community!

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

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 ...