Deployment Architecture

best use of "spare" servers

a212830
Champion

Hi,

We upgraded to Splunk 6.1 this spring, and with that purchased new physical servers. The SH's (two) are 64 cores and 128gb of memory and the indexers are all 48 cores and 128gb of memory. I have two additional servers - one of the original servers (16 cores and 48gb of memory) and another new one that is 32 cores and 128gb of memory. I want to put these to use before I'm told to return them. However, since they don't match the specs of either of the existing SH's or indexers, I've been told (unofficially) that it's not a great idea - the servers should all be the same specs within function. Do people agree with this? Is there any reason that I couldn't make both of these either indexers or SH's? (I do plan on upgrading to 6.2 early next year).

0 Karma

ekost
Splunk Employee
Splunk Employee

Sweet. Run D.M.C. after upgrading to 6.2. And I'm sure you'll want a deployer node for the search head cluster.

martin_mueller
SplunkTrust
SplunkTrust

More uses would be as a master in an indexer cluster, as a heavy forwarder for "special needs" sources such as DBConnect, a testbed for crazy new ideas, ...

I doubt you'll need a deployer though, because running a search head cluster with just two SHs shouldn't really work... however, you could use one of the spare boxes as a dedicated captain captain_is_adhoc_searchhead = true and turn your two SHs into a working search head cluster 😄

a212830
Champion

Ideally, I'd like to add it to the SHC. Sounds like I could use it as the captain, and still have it perform searches? I'd like to take advantage of the number of cores and memory available on the 32 core server especially. For the other uses, I'm able to spin up smaller servers quickly.

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 ...