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!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...