Re: RE : Problem when consuming storm metrics

[Abhishek Agarwal <ab...@gmail.com>]

It would be a good idea to take thread dump when logging stops. That could
give some clues

Excuse typos
On Mar 19, 2016 9:33 PM, "Denis DEBARBIEUX" <dd...@norsys.fr> wrote:

> Yes, I do.
>
> Denis
> ------------------------------
> *De :* Abhishek Agarwal [abhishcool@gmail.com]
> *Date d'envoi :* vendredi 18 mars 2016 22:38
> *À :* user@storm.apache.org
> *Objet :* Re: Problem when consuming storm metrics
>
> Do you get this problem if you use only the LoggingMetricsConsumer?
>
> Excuse typos
> On Mar 18, 2016 9:38 PM, "Denis DEBARBIEUX" <dd...@norsys.fr> wrote:
>
>> Dear all,
>>
>> I have a question about metrics and how they are consumed:
>> I launch my topology. During 3 or 4 minutes, I receive my metrics. Then
>> no more logs.
>> It's look like the process that is consuming the metrics has a dead lock
>> or is blocked by a time out.
>>
>> Here comes some information about the context:
>>  - I am using storm 0.9.4.
>>  - Some metrics are defined by defaut (eg emit-count.default) some other
>> are customed.
>>  - I am sure that my topology is still running.
>>  - According to Storm UI, the number of messages emiting by my bolts is
>> increasing. In other words, metrics are still computing and send somewhere.
>>  - I try two instances of LoggingMetricsConsumer: in file
>> (backtype.storm.metric.LoggingMetricsConsumer) and in graphite
>> (com.verisign.storm.metrics.GraphiteMetricsConsumer).
>>  - I can reproduce it on 2 different machines.
>>  - No error are logged (worker, metric, supervisor).
>>  - I am using storm since 1 year and I never seen this problem.
>>
>> Thanks for your help.
>>
>> Denis
>>
>> ---
>> L'absence de virus dans ce courrier électronique a été vérifiée par le
>> logiciel antivirus Avast.
>> https://www.avast.com/antivirus
>>
>>