Closed keep94 closed 8 years ago
@keep94 sadly, we never used NoACK option and looks like it was not fully implemented. Please check again, your code should work now. Remember that without ack you get no offset response and none of produced message attributes are updated.
I have written a very simple program to send two messages to a KAFKA cluster. The program queries the broker for the partition count and uses that count to create a Distributed Producer to distribute the load across the partitions.
The program works fine if I use conf.RequiredAcks = proto.RequiredAcksLocal. But I am willing to give up some durability guarantees to lower latency. Therefore, I don't want to wait for any acks.
When I change my program to use proto.RequiredAcksNone, it panics like this:
Here is my go program: