https://community.splunk.com/t5/Deployment-Architecture/REST-API-and-search-head-cluster/m-p/493342#M17042 <P>You need to turn on <CODE>sticky sessions</CODE> feature on your load balancer based on <CODE>session_id_PORTNUMBER</CODE> cookie.</P> Thu, 19 Mar 2020 12:56:33 GMT woodcock 2020-03-19T12:56:33Z https://community.splunk.com/t5/Deployment-Architecture/REST-API-and-search-head-cluster/m-p/493341#M17041 <P>Hello,</P> <P>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.<BR /><BR />Later on, the load balancer changes the search head that Splunk REST API is connected to.<BR />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.</P> <P>How can I solve this issue now that we are running with search head cluster?</P> <P>Thanks</P> Thu, 11 Jun 2020 21:00:00 GMT https://community.splunk.com/t5/Deployment-Architecture/REST-API-and-search-head-cluster/m-p/493341#M17041 sarit_s 2020-06-11T21:00:00Z https://community.splunk.com/t5/Deployment-Architecture/REST-API-and-search-head-cluster/m-p/493342#M17042 <P>You need to turn on <CODE>sticky sessions</CODE> feature on your load balancer based on <CODE>session_id_PORTNUMBER</CODE> cookie.</P> Thu, 19 Mar 2020 12:56:33 GMT https://community.splunk.com/t5/Deployment-Architecture/REST-API-and-search-head-cluster/m-p/493342#M17042 woodcock 2020-03-19T12:56:33Z https://community.splunk.com/t5/Deployment-Architecture/REST-API-and-search-head-cluster/m-p/493343#M17043 <P>that means it will be sticky what happens if the instances its tied to crashes and the load balancer switches instances?<BR /> also it will always be the same session on the same splunk instance ?</P> Thu, 19 Mar 2020 15:05:49 GMT https://community.splunk.com/t5/Deployment-Architecture/REST-API-and-search-head-cluster/m-p/493343#M17043 sarit_s 2020-03-19T15:05:49Z