In our system, Splunk REST API does a login call to Splunk in one of the search heads and gets a token from that search head.
Later on, the load balancer changes the search head that Splunk REST API is connected to.
The service is still logged into the previous search head with the token from that search head, but it's sending this token to a different search head which still hasn't been logged into.
How can I solve this issue now that we are running with search head cluster?
that means it will be sticky what happens if the instances its tied to crashes and the load balancer switches instances?
also it will always be the same session on the same splunk instance ?