Deployment Architecture

After a Deployment Server outage, clients all reconnect at once. Any way to stop this?

Jason
Motivator

So our Deployment Server was down for some time, beyond that of the clients' checkin interval, and now that it is back up it is being overwhelmed by hundreds of clients checking in within a few thousanths of a second of each other.

Can anyone think of a way to stop this, without using another tool to sequentially restart splunk on every forwarder?

This is going in as a bug, there's no reason Splunk shouldn't continue to use the checkin interval if unable to connect, or at least backoff and not try every 10-15 seconds.

dstaulcu
Builder

handshakeRetryIntervalInSecs =
* Defaults to phoneHomeIntervalInSecs [does not seem to be true]
* This sets the handshake retry frequency.
* Could be used to tune the initial connection rate on a new server

http://docs.splunk.com/Documentation/Splunk/6.0.1/admin/Deploymentclientconf

0 Karma
Get Updates on the Splunk Community!

Get the T-shirt to Prove You Survived Splunk University Bootcamp

As if Splunk University, in Las Vegas, in-person, with three days of bootcamps and labs weren’t enough, now ...

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...