topic.metadata.refresh.interval.ms for the
producer
to pick up the newly available partitions (see
http://kafka.apache.org/08/configuration.html for details).
Thanks,
Jun
On Wed, Jun 12, 2013 at 8:01 AM, Alexandre Rodrigues
alexan...@blismedia.com wrote:
Hi,
I have a Kafka 0.8
of consumer (which should be OK, no?)
Thanks,
Alex
On 13 June 2013 10:15, Alexandre Rodrigues alexan...@blismedia.com wrote:
Hi Jun,
I was using the 0.8 branch with 2 commits behind but now I am using the
latest with the same issue. 3 topics A,B,C, created automatically with
replication
related with the security group. I am going to run
the first setup with all open doors and see how it goes. If the ports are
really the problem, shouldn't this kind of problem be logged somewhere?
On 13 June 2013 12:13, Alexandre Rodrigues alexan...@blismedia.com wrote:
I've tried the console
at 6:41 AM, Alexandre Rodrigues
alexan...@blismedia.com wrote:
I think I know what's happening:
I tried to run both brokers and ZK on the same machine and it worked. I
also attempted to do the same but with a ZK node on other machine and it
also worked.
My guess is something related
/configuration.html for details).
Thanks,
Jun
On Wed, Jun 12, 2013 at 8:01 AM, Alexandre Rodrigues
alexan...@blismedia.com wrote:
Hi,
I have a Kafka 0.8 cluster with two nodes connected to three ZKs, with
the
same configuration but the brokerId (one is 0 and the other 1). I created
three topics
