Hmm, anything special with that topic (e.g., did you run any admin
operation on it)? Also, does bouncing the brokers fix the issue?
Thanks,
Jun
On Tue, Feb 10, 2015 at 1:31 PM, Sumit Rangwala
wrote:
> On Thu, Feb 5, 2015 at 12:37 PM, Sumit Rangwala
> wrote:
>
> >
> >
> > On Wed, Feb 4, 2015 a
On Thu, Feb 5, 2015 at 12:37 PM, Sumit Rangwala
wrote:
>
>
> On Wed, Feb 4, 2015 at 9:23 PM, Jun Rao wrote:
>
>> Could you try the 0.8.2.0 release? It fixed one issue related to topic
>> creation.
>>
>
Jun,
If you need more info let me know. Seems like TopicMetadataResponse is
expecting more fi
On Wed, Feb 4, 2015 at 9:23 PM, Jun Rao wrote:
> Could you try the 0.8.2.0 release? It fixed one issue related to topic
> creation.
>
Jun,
Tried with 0.8.2.0 and I still see the same error.
I see the error given below almost incessantly on the client side for topic
LAX1-GRIFFIN-r47-14231658976
Could you try the 0.8.2.0 release? It fixed one issue related to topic
creation.
Thanks,
Jun
On Wed, Feb 4, 2015 at 12:58 AM, Sumit Rangwala
wrote:
> I am observing the following exception with kafka client:
>
> 2015-02-04 00:17:27,345
>
> (LAX1-GRIFFIN-r8-1423037468055-pf13797-lax1-GriffinDow
I am observing the following exception with kafka client:
2015-02-04 00:17:27,345
(LAX1-GRIFFIN-r8-1423037468055-pf13797-lax1-GriffinDownloader-1423037818264_c7b1e843ff51-1423037822122-eb7afca7-leader-finder-thread)
ClientUtils$ WARN: Fetching topic metadata with correlation id 112 for
topics [Set
