Deployment Architecture

4.2 Search head with a 4.3 Search peer

johandk
Path Finder

We are looking to upgrade all our instances to 4.3 and will end up with 4.2 search heads distributing to 4.3 search peers.

Has anyone tested this? Are there any caveats we should be aware of?

Tags (1)
0 Karma
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

This will work and I believe is a supported configuration. However, you will of course be unable to use any new 4.3 search features (e.g., new search commands, per-result alerting, historical backfill in real-time searches), and of course the UI and workflow will be 4.2. About the only new 4.3 feature that you can use is Bloom filters.

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

This will work and I believe is a supported configuration. However, you will of course be unable to use any new 4.3 search features (e.g., new search commands, per-result alerting, historical backfill in real-time searches), and of course the UI and workflow will be 4.2. About the only new 4.3 feature that you can use is Bloom filters.

Get Updates on the Splunk Community!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

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