Deployment Architecture

Distributed search and scripted lookups

bharaths
New Member

In a distributed search environment, do the python files for scripted lookups have to be placed manually on the indexers?
Or is it ok to just place the files in the search head, and allow it to replicate the scripts onto the indexers?

0 Karma
1 Solution

Ayn
Legend

The lookup scripts will be included in the bundles that are replicated to the search peers, so you won't have to copy those manually.

Just make sure you keep track of where the lookup is run - the search head will be ultimately responsible for bringing together the search results at some point in the search, so if you run a lookup after that point it'll be the search head running it, not the search peers.

View solution in original post

0 Karma

Ayn
Legend

The lookup scripts will be included in the bundles that are replicated to the search peers, so you won't have to copy those manually.

Just make sure you keep track of where the lookup is run - the search head will be ultimately responsible for bringing together the search results at some point in the search, so if you run a lookup after that point it'll be the search head running it, not the search peers.

0 Karma

Dbshah
Splunk Employee
Splunk Employee

I am getting "Read TimeoutError" for scripted lookup like below:

Problem replicating config (bundle) to search peer ' <indexerip>:8089 ', Upload bundle="/opt/splunk/var/run/7CAA9ED1-1C47-433B-83A2-5FBC5B25691E-1593006032.bundle" to peer name=c1idx3taf.cdsys.local uri=https://<indexerip>:8089 failed; error="Read Timeout".

Am I doing something wrong?

0 Karma

bharaths
New Member

Thanks, placing the script on the search head worked perfectly

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...