Hi Eno,
Here is the code for the application ExclusiveStatsConnectionDevice which is
composed of 4 nodes.
For example when i put print("....") you would sess the problem of the
infinite loop.
I preferred to send the whole code sto make it easier to you even though you
don't need all of it
________________________________
De : Eno Thereska <eno.there...@gmail.com>
Envoyé : lundi 28 novembre 2016 01:12:14
À : users@kafka.apache.org
Objet : Re: Abnormal working in the method punctuate and error linked to
seesion.timeout.ms
Hi Hamza,
Would you be willing to share some of your code so we can have a look?
Thanks
Eno
> On 28 Nov 2016, at 12:58, Hamza HACHANI <hamza.hach...@supcom.tn> wrote:
>
> Hi Eno.
>
> The problem is that there is no infinite while loop that i write.
>
> So I can't understand why the application is doing so.
>
>
> Hamza
>
> ________________________________
> De : Eno Thereska <eno.there...@gmail.com>
> Envoyé : dimanche 27 novembre 2016 23:21:24
> À : users@kafka.apache.org
> Objet : Re: Abnormal working in the method punctuate and error linked to
> seesion.timeout.ms
>
> Hi Hamza,
>
> If you have an infinite while loop, that would mean the app would spend all
> the time in that loop and poll() would never be called.
>
> Eno
>
>> On 28 Nov 2016, at 10:49, Hamza HACHANI <hamza.hach...@supcom.tn> wrote:
>>
>> Hi,
>>
>> I've some troubles with the method puctuate.In fact when i would like to
>> print a string in the method punctuate.
>>
>> this string would be printed in an indefinitly way as if I printed (while
>> (true){print(string)}.
>>
>> I can't understand what happened.Does any body has an explenation ?.
>>
>>
>> Besides In the other hand,for another application it print the following
>> error :
>>
>> WARN Failed to commit StreamTask #0_0 in thread [StreamThread-1]:
>> (org.apache.kafka.streams.processor.internals.StreamThread)
>> org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be
>> completed since the group has already rebalanced and assigned the partitions
>> to another member. This means that the time between subsequent calls to
>> poll() was longer than the configured session.timeout.ms, which typically
>> implies that the poll loop is spending too much time message processing. You
>> can address this either by increasing the session timeout or by reducing the
>> maximum size of batches returned in poll() with max.poll.records.
>>
>> When i tried to modify the configuration of the consumer nothing happened.
>>
>> Any Ideas for this too ?
>>
>> Thanks in Advance.
>>
>>
>> Hamza
>>
>
