What's the recommended way to restart a hekad aggregator? In trying out a hekad instance that forwards messages to another hekad instance, I see writer side throw errors when I restart the upstream side and never recover.
Is there some way to trigger automatic reconnection? I'd settle for the writer exiting on a write failure so something like circusd could restart it. Basically this error on the writer side never resolves itself after the other instance fully restarts: 2014/01/05 22:39:00 Plugin 'aggregator_output' error: writing to svab35:5565: write tcp 10.0.1.35:5565: broken pipe
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
