Getting Data In

Search Peers(Indexers) & what they get from their Mounted Knowledge Bundle

Damien_Dallimor
Ultra Champion

I'm setting up several Search Peers(Indexers) and a pool of Search Heads using the combined mount approach from the Splunk docs :

"For multiple search heads, you can
combine mounted bundles with search
head pooling. The pooled search heads
maintain one bundle on the shared
storage, and all search peers access
that bundle".

Will the Search Peers obtain their entire configuration from the mounted knowledge bundle, or just the knowledge pertaining to distributed search requests ?

ie: on each Search Peer do I also have to locally(or using Deploy Manager, Puppet etc..) setup the index definitions, index time transforms & receiving ?

Tags (2)
0 Karma
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

They will only get information about distributed search requests from a mounted bundle. The other items must be configured locally as usual. Note that a mounted bundle will have the configuration from a search head, which will usually lack index definitions, listen ports, index-time transforms, etc.

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

They will only get information about distributed search requests from a mounted bundle. The other items must be configured locally as usual. Note that a mounted bundle will have the configuration from a search head, which will usually lack index definitions, listen ports, index-time transforms, etc.

Damien_Dallimor
Ultra Champion

Thanks GK.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...