Installation

Splunk 4.3 upgrade question - disable?

gnovak
Builder

In the instructions here:

http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Upgradeyourdistributedenvironment

In the area where you are upgrading a distributed environment with multiple indexers and non-pooled search heads, it states that in step #4 you should:

  1. Disable and upgrade one of the search heads. Do not allow it to restart.

What exactly do they mean by "disable"? Stop splunk?

The search head we are updating is our main search head. It's the main console everyone logs into to use splunk. It searches 3 other main indexers. It also indexes data itself. I'm assuming they mean to stop splunk?

Can anyone clarify what "disable" means?

If these instructions are for non-pooled search heads, I can't see how disable would mean disabling it from being searched on by the rest of the pool if it's a non-pooled search head.

Tags (1)
1 Solution

jgedeon120
Contributor

$SPLUNK_HOME/bin/splunk disable boot-start
$SPLUNK_HOME/bin/splunk stop

Then do your upgrade(s).

$SPLUNK_HOME/bin/splunk enable boot-start
$SPLUNK_HOME/bin/splunk start

View solution in original post

jgedeon120
Contributor

$SPLUNK_HOME/bin/splunk disable boot-start
$SPLUNK_HOME/bin/splunk stop

Then do your upgrade(s).

$SPLUNK_HOME/bin/splunk enable boot-start
$SPLUNK_HOME/bin/splunk start

jgedeon120
Contributor

You're welcome.

0 Karma

gnovak
Builder

Thank you very much

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...