> > Yes, it will keep trying until the link comes back, or until the buffer >> hits a configurable max buffer size, at which point it will either start >> dropping messages, apply back pressure to the entire pipeline by blocking >> the router, or cause Heka to shut down, depending on your configuration. >> > That explanation was very helpful. Thanks.
> No, neither of these are supported at this time. Currently you'd need to > either do this at the network level, or use an alternate transport. That's ok. This can be handled at the dns level. Regards, WU
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
