Deployment Architecture

Deployer is throwing out error

adoumbia
Engager

Hello

I am building a new search head cluster, the cluster work fine, however the deployer is throwing error whenever I run "/bin/splunk show shcluster-status" on the deployer

Here is error I am getting

"Encountered some errors while trying to obtain shcluster status.
Search Head Clustering is not enabled on this node. REST endpoint is not available"

my server.conf look like the following

[shclustering]
pass4SymmKey = xxxxxxxxx

 

Your input  be appreciated

Labels (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @adoumbia ,

for my knowedge, you can run this command only on Search Heads, not on Deployer, because it isn't a component of the Cluster, it's only the system that deployes apps to the Cluster, but after deployment, the Cluster runs by itself.

Ciao.

Giuseppe

PickleRick
SplunkTrust
SplunkTrust

Yes. @gcusello is 100% spot-on. I admit it is a bit counterintuitive (especially compared to indexer cluster and manager node) but the deployer is not a part of a search head cluster. It is an auxiliary component meant to be used for... well, deploying the configuration to the SHC but apart from that it doesn't take part in any other SHC activity.

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...