Splunk Enterprise

migrating to new hardware

KulvinderSingh
Path Finder

Splunk offline --enforce-count or data rebalance which one is better in case of migrating to new hardware and do i have to add peer to manual detention in indexer cluster before running a data rebalance or splunkoffline?

 

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Use splunk offline --enforce-count to migrate to new hardware.  A rebalance will shuffle buckets around, but won't remove the old indexer.  If you're only replacing a single indexer then manual detention is not necessary.  However, if this is one of many migrations than consider setting manual detention on each old indexer so they don't receive buckets from the others that are taken down.  It will spare the system from potentially moving the same bucket multiple times.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Use splunk offline --enforce-count to migrate to new hardware.  A rebalance will shuffle buckets around, but won't remove the old indexer.  If you're only replacing a single indexer then manual detention is not necessary.  However, if this is one of many migrations than consider setting manual detention on each old indexer so they don't receive buckets from the others that are taken down.  It will spare the system from potentially moving the same bucket multiple times.

---
If this reply helps you, Karma would be appreciated.
Get Updates on the Splunk Community!

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...

Adoption of Infrastructure Monitoring at Splunk

  Splunk's Growth Engineering team showcases one of their first Splunk product adoption-Splunk Infrastructure ...

Modern way of developing distributed application using OTel

Recently, I had the opportunity to work on a complex microservice using Spring boot and Quarkus to develop a ...