cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Ask a Question
damonmiller
New Member
Member since: ‎03-02-2011
‎06-05-2020
Community Statistics
Posts 4
Solutions 0
Karma Given 0
Karma Received 0
Member Since ‎03-02-2011
Activity Feed
View All

Re: Sticky Sessions with Splunk Search Heads behin...

by in Security
‎03-07-2011 06:28 PM
‎03-07-2011 06:28 PM
Finally got this working using Apache's internal balancer cookies (ROUTEID) as described in http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html#example ... View more

Re: Sticky Sessions with Splunk Search Heads behin...

by in Security
‎03-07-2011 04:55 PM
‎03-07-2011 04:55 PM
ProxyPass / balancer://mycluster/ stickysession=session_id_8000 nofailover=On timeout=15 ProxyPassReverse / balancer://mycluster/ stickysession=session_id_8000 BalancerMember http://10.x.x.10:8000 BalancerMember http://10.x.x.11:8000 ... View more

Re: Sticky Sessions with Splunk Search Heads behin...

by in Security
‎03-07-2011 04:54 PM
‎03-07-2011 04:54 PM
Hmmm. I tried adding that session cookie to the apache config, but can't seem to make that work- I am continually redirected back to the Splunk login screen when more than one backend proxies are configured. I'm assuming this is a session issue, because proxying a single backend server works fine, its when I add two or more that the behavior starts... I suppose this is more an Apache issue than Splunk, but I thought someone must have tried this. Here is my Apache config snippet (more or less straight out of the Apache docs): ... View more

Sticky Sessions with Splunk Search Heads behind Ap...

by in Security
‎03-02-2011 05:27 PM
‎03-02-2011 05:27 PM
Hello. I have a set of 3 or so search-heads that have matching configurations. I am trying to configure an Apache Reverse-Proxy to load-balance between these servers to maximize search capacity and to handle HTTPS encoding, etc. I have sucessfully setup the proxy to point to a single search head, but when I configure more than one, I find the sessions continuing to round-robin between servers, intead of "sticking" to on search head after a session is established. I have followed a few recommendations as documented on the Apache mod_proxy and mod_proxy_balancer docs, but so far can't make this work. Does splunk have any standardized session variables, like "JSESSIONID" or the like I could leverage? Any other suggestions? Has anyone gotten this to work? Thanks! Damon ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎06-05-2020 02:02 AM