Hello Ismael,
yes, I went through that PR and this is what I was actually looking for.
Thanks!
2016-10-12 14:37 GMT+02:00 Ismael Juma :
> Hi Alexandru,
>
> I think your issue will be fixed by KAFKA-4254. There's a PR available and
> should be merged shortly. Can you please verify?
>
> Thanks,
>
Hi Alexandru,
I think your issue will be fixed by KAFKA-4254. There's a PR available and
should be merged shortly. Can you please verify?
Thanks,
Ismael
On Wed, Oct 12, 2016 at 11:00 AM, Alexandru Ionita <
alexandru.ion...@gmail.com> wrote:
> OK. then my question is: why is not the producer try
OK. then my question is: why is not the producer trying to recover from
this error by updating its topic metadata right away instead of waiting for
the "metadata.max.age.ms" to expire?
2016-10-12 11:43 GMT+02:00 Manikumar :
> we have similar setting "metadata.max.age.ms" in new producer api.
> It
we have similar setting "metadata.max.age.ms" in new producer api.
Its default value is 300sec.
On Wed, Oct 12, 2016 at 3:04 PM, Alexandru Ionita <
alexandru.ion...@gmail.com> wrote:
> Hello kafka users!!
>
> I'm trying implement/use a mechanism to make a Kafka producer imperatively
> update its
