Deployment Architecture

Will the deployer being on the master node and already been upgraded prior to reaching the search head tier, cause any problems when upgrading a clustered environment?

Path Finder

I'm working on upgrading a clustered environment from 6.5 to the current version. I have search head clusters, indexer clusters, and indexer clusters.

I'm planning to follow the instructions here. It lists the steps for upgrading the master node, upgrading the search head tier, upgrading the peer tier. This all seems fine but when I look at the instructions for the search head tier if it uses a search head cluster (link here) it shows the order of the upgrade to be all the members, then the deployer.

The problem and question I have is that the deployer is on the master node so it will have already been upgraded prior to reaching the search head tier. Since this seems to be a common configuration I don't expect it would be a problem, but I wanted to see if anyone had encountered this situation before or if anyone knew if this will likely cause problems.

Thanks.

0 Karma
1 Solution

Influencer

It's not a supported configuration, but I don't think it will cause any problems since there will only be a version mismatch while you're doing upgrades. If you can, after the upgrades, you should consider running the master node and deployer roles on separate hosts.

View solution in original post

0 Karma

Influencer

It's not a supported configuration, but I don't think it will cause any problems since there will only be a version mismatch while you're doing upgrades. If you can, after the upgrades, you should consider running the master node and deployer roles on separate hosts.

View solution in original post

0 Karma

Path Finder

Ok, that is good to know, thank you.

0 Karma