this is not the case with Splunk 6.x
when my remote splunk server is down, my local splunk spits out tcperror (expected) but eventually fill up the queues and blocks all indexing.
The preferred behavior is to drop new tcpout events until the connection is resumed. This allows all other events to be indexed.
Again, I don't see this problem on Splunk 6.x.
