Deployment Architecture

adding search-heads to search-head pooling...

a212830
Champion

I am building out a new Splunk 6 with some new, shiny, heavy-duty servers (yay!). We are setting up search-head pooling across two servers and it got me thinking - is there any reason that, in the future (or even now) I can't add vm's to that search-head pool? They are going to be using the same NAS disk. Pro's? Con's? Seems like a nice, inexpensive way to expand search-head pooling...

Tags (1)
0 Karma

twinspop
Influencer

In my experience, VMs are poor search heads. The I/O requirements of Splunk are just too high. Additionally, SHP requires the use of an NFS share, which also slows down SH performance. Doing both is a double-whammy. Sure it works, but the performance is pretty poor. We recently got physical servers to replace our SHP'd VMs and the difference is night and day. (Even more so when I was testing them out before putting them in the SHP.)

a212830
Champion

Thanks for the info.

0 Karma
Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...