Hi team,
According to the document, the default partitioner hashes the key string and
assign the message
to a broker. Could you give a brief introduction to the hash algorithm? If a
long timestamp (in hex format)
is used as key, will the messages be distributed evenly to all partitions?
Assume
It hashes the key and mods it by the number of partitions, not brokers.
Thanks,
Neha
On Oct 19, 2013 7:44 AM, "Yu, Libo" wrote:
> Hi team,
>
> According to the document, the default partitioner hashes the key string
> and assign the message
> to a broker. Could you give a brief introduction to
Hi team,
For the message type in KeyedMessage, I can use String or byte[].
Is there any difference in terms of the actual data transferred?
Regards,
Libo
The latest HEAD does seem to solve one issue, where a new topic being
created after the consumer is started, would not be consumed.
But the bigger issue is that we have a couple different consumers both
consuming the same set of topics (under different groupids), and hanging
after a while (both ha
Can you send around a thread dump of the halted consumer process?
On Sat, Oct 19, 2013 at 12:16 PM, Jason Rosenberg wrote:
> The latest HEAD does seem to solve one issue, where a new topic being
> created after the consumer is started, would not be consumed.
>
> But the bigger issue is that we
Not really. If you use a String key, you will have to use a StringEncoder
for the key serializer. The key serializer turns any key into a byte array.
Thanks,
Neha
On Sat, Oct 19, 2013 at 11:02 AM, Yu, Libo wrote:
> Hi team,
>
> For the message type in KeyedMessage, I can use String or byte[].
I'll try to, next time it hangs!
On Sat, Oct 19, 2013 at 4:04 PM, Neha Narkhede wrote:
> Can you send around a thread dump of the halted consumer process?
>
>
>
> On Sat, Oct 19, 2013 at 12:16 PM, Jason Rosenberg
> wrote:
>
> > The latest HEAD does seem to solve one issue, where a new topic bei
