I didn't know there's a method in the producer to get the metadata from the
broker.
I will fix my producer container.
On Wed, Sep 17, 2014 at 6:52 PM, Neha Narkhede neha.narkh...@gmail.com
wrote:
Could you make them same logic? Otherwise, I have to change implementation
of kafka producer
Hey Jae,
The rationale for switching was to use a hash code that is cross
language and not dependent on the particular object. There are all
kinds of gotchas with Java's hashCode() as a partition assignment
strategy (e.g. two byte arrays with the same bytes will have different
hash codes).
-Jay
The major motivation of adopting new producer before it's released, old
producer is showing terrible throughput of cross-regional kafka mirroring
in EC2.
Let me share numbers.
Using iperf, network bandwidth between us-west-2 AWS EC2 and us-east-1 AWS
EC2 is more than 40 MB/sec. But old
Could you make them same logic? Otherwise, I have to change implementation
of kafka producer container.
The new producer is much more flexible and allows the user to use custom
partitioning logic and provide the partition number in the ProducerRecord.
That way it is broadly applicable to a
