Getting Data In

Indexer Configuration

OldManEd
Builder

We have 3 new HP Red Hat Servers we need to install with 13 already running. All of them have 8 drives and the new ones are 950G I believe. Any suggestions on the best configurations based on experience? I’m thinking for the overall hardware RAID, 4 drives backed up by the other 4. Now, for partitioning we have the following configuration on the other indexers;

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_splunkindexnn-lv_root
                       50G  2.0G   45G   5% /
tmpfs                  16G     0   16G   0% /dev/shm
/dev/sda1             485M   62M  398M  14% /boot
/dev/mapper/vg_splunkindexnn-lv_home
                      468G  145G  300G  33% /home
/dev/mapper/vg_splunk_opt-splunk_opt
                      1.1T  758G  288G  73% /opt
/dev/mapper/vg_splunk_storage-splunk_storage
                      551G  218G  305G  42% /opt/storage

Comments?

Tags (2)
0 Karma

OldManEd
Builder

I got with our Linux team and figured this one out.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...