Deployment Architecture

procedure to perform non-rolling upgrade a (Windows) Search Head Cluster - problem with service auto-restart

sylbaea
Communicator

Hello,

I have a 3-node (Windows 2012 R2 based) Search Head Cluster currently connected to a standalone indexer.

I wanted to follow the non-rolling upgrade procedure (anticipating it will be soon connected to a clustered indexer) described here:
http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/UpgradeaSHC

It is specified as step 1 to stop all cluster members, and to only restart them after the upgrade of all nodes.

However:
1. If I simply stop Splunkd Service, the MSI setup does restart the service automatically at the end of the upgrade.
2. If I stop Splunkd Service and temporary change startup type to Disabled, upgrade fails and rollback because setup is not able to start the service.

By the end, the upgrade has worked (I manually stopped again each node after its upgrade) but I have not been able to comply with the "official" non-rolling upgrade procedure.
Is anybody proceeding differently and able to follow the official procedure ?

Regards.

0 Karma
1 Solution

somesoni2
Revered Legend

You can use Command line to upgrade Splunk and specify following flag so that Splunk will not try to start the service after upgarde.

msiexec.exe /i splunk-<...>-x64-release.msi LAUNCHSPLUNK=0 /quiet

LAUNCHSPLUNK=0/1

Description: Use this flag to specify whether or not Splunk should start up automatically on system boot.
Note: If you enable the Splunk Forwarder by using the SPLUNK_APP flag, the installer configures Splunk to start automatically, and ignores this flag.
Default Value: 1 (on)

View solution in original post

somesoni2
Revered Legend

You can use Command line to upgrade Splunk and specify following flag so that Splunk will not try to start the service after upgarde.

msiexec.exe /i splunk-<...>-x64-release.msi LAUNCHSPLUNK=0 /quiet

LAUNCHSPLUNK=0/1

Description: Use this flag to specify whether or not Splunk should start up automatically on system boot.
Note: If you enable the Splunk Forwarder by using the SPLUNK_APP flag, the installer configures Splunk to start automatically, and ignores this flag.
Default Value: 1 (on)

sylbaea
Communicator

You are right. I forgot about this option.
Thanks a lot for the reminder 🙂

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...