>For this one case, though, an easier fix would be to have the ES output retry, >and/or if it fails to have the data that *would* have been sent to ES to >instead be written out to disk.
I agree with Rob, that it's easier to patch ES output and add a retry. I've patched heka to add buffered output (like in TCPOutput plugin). It perfectly works and we have simple monitoring of buffering and sending performance. But... we completely lost ability to send bulk POSTs to ES because BufferedOutput works only with single messages. Yes, we might use flush_* parameters, but it's meaningless to keep messages in previous buffer and to lost the whole bulk of them in ES output because of network errors. BTW, Rob did you consider in your feature plans how to handle this situation (single processing in BufferedOutput vs bulk sending outputs)? _______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
