Are there any thoughts on running Zookeeper on the same physical nodes that run
the Kafka broker? So the loss of a node affects quorum and possibly requires
electing new leaders at both the ZK and the broker level. Are there race
conditions or other failure cases that could come about from eithe
Ah, thanks. The intent of my question though was to better understand how a
large number of partitions affects Kafka itself.
- Original Message -
From: balaji.sesha...@dish.com
To: Sudarshan Kadambi (BLOOMBERG/ 731 LEXIN), users@kafka.apache.org
At: Apr 8 2014 15:26:49
We have 131
ition count is because it simplifies application
semantics.
- Original Message -
From: balaji.sesha...@dish.com
To: Sudarshan Kadambi (BLOOMBERG/ 731 LEXIN), users@kafka.apache.org
At: Apr 8 2014 14:08:41
I think you are looking for accessing messages from set of partitions by your
Let's say I've a single consumer thread reading off multiple partitions (I'll
have around 10K partitions). As per the documentation on
https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Group+Example, there
are no guarantees on the order in which messages are read off the set of
partiti
Hi:
If someone's intention is to implement a producer such that:
1. The call to send() blocks until the write is successful on the configured
number or replicas or max num of retries.
2. The call to send() takes in a configurable batch of messages that is
committed all or nothing.
what combinat