This is from commit: 7fcbd42b32ac7d75e709e73a60eae386a8ad181a
I'll add that I got the same results from similar code that I was testing yesterday for a few hours. The results are always the same: heka gets totally wedged, Queue report shows the kafka output as fully blocked up, and all the the sarama goroutines are all executing the same line of code.
Notably the plugin runner for KafkaOutput is always in:
This is from commit: 7fcbd42b32ac7d75e709e73a60eae386a8ad181a
I'll add that I got the same results from similar code that I was testing yesterday for a few hours. The results are always the same: heka gets totally wedged, Queue report shows the kafka output as fully blocked up, and all the the sarama goroutines are all executing the same line of code.
Notably the plugin runner for KafkaOutput is always in:
While what appear to be the 2 sarama flusher goroutines are both blocked on sending errors on the error channel to our plugin runner:
Here's the full stack dump from sending SIGQUIT. http://f.cl.ly/items/3o2t402E352S262O0L3e/heka-kafa-wedge.txt
Queue report:
My KafkaOutput plugin settings are pretty simple, went with many defaults: