Hi,
Have notice an issue. We retrieve the
"kafka.log":type="Log",name="--LogEndOffset" 's Attribute:
Value and used it to calculate the lag from consumer's offset.
After we did a partition re-assignment, where partition leaders were changed,
some of the new leader's LogEndOffset were not updat
Hi,
We are doing load testing. Ran into some exception - need some help
clarifying what the problem is and how to bring the broker back on-line (hoping
w/o the need to shutdown other brokers). Each broker was handling about 100k
msgs/sec.
Payload is small - less than 500 bytes
About 2 hours
#x27;s not very intuitive. Currently, it is true that we don't have gap
in the partition ids. Since we already build the new producer, we probably
don't have to patch the old producer.
Thanks,
Jun
On Thu, Apr 3, 2014 at 9:06 AM, joe smith wrote:
> Hi,
>
> My apologies - a
Hi,
My apologies - a newbie here.
In looking at the getPartition() method, I notice the returned value for keyed
message is the "index" of a partition. But when there is no key, then the
value returned is the "id" of a partition.
case None =>
val availablePartitions =
t
