.
Thanks,
Nihit
On 11-Jul-2013, at 4:41 PM, Nihit Purwar wrote:
> Hi Jun,
>
> I did put in only one topic while starting the consumer and have used the
> same API "createMessageStreams".
> As for the trace level logs of kafka consumer, we will send that to you soon.
>
>
> On Wed, Jul 10, 2013 at 8:30 AM, Nihit Purwar wrote:
>
>> Hi Jun,
>>
>> Thanks for helping out so far.
>>
>> As per your explanation we are doing exactly as you have mentioned in your
>> workaround below.
>>> A workaround is to u
e queues is full, the fetcher
> will block and can't put the data into other queues.
>
> A workaround is to use different consumer connectors, each consuming a
> single topic.
>
> Thanks,
>
> Jun
>
>
> On Tue, Jul 9, 2013 at 11:12 PM, Nihit Purwar wrot
TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at kafka.consumer.FetcherRunnable.run(FetcherRunnable.scala:99)
>
> Thanks,
>
> Jun
>
>
> On Tue, Jul 9, 2013 at 8:37 AM, Nihit Purwar wrote:
>
>> Hello Jun,
>>
>> Ple
.lang.Thread.run(Thread.java:662)
>
> Thanks,
>
> Jun
>
>
> On Tue, Jul 9, 2013 at 4:18 AM, Nihit Purwar wrote:
>
>> Hi,
>>
>> We are using kafka-0.7.2 with zookeeper (3.4.5)
>>
>> Our cluster configuration:
>> 3 brokers on 3 differe
Hi,
We are using kafka-0.7.2 with zookeeper (3.4.5)
Our cluster configuration:
3 brokers on 3 different machines. Each broker machine has a zookeeper instance
running as well.
We have 15 topics defined. We are trying to use them as queue (JMS like) by
defining the same group across different ka
