Hi all,
I profile my code and I see that the thread <BoldName>MetricConsumer is
locked and never unlocked. It is why my metrics are never published.
More over, the problem is related to buffer size:
* topology.executor.receive.buffer.size=16 and
topology.executor.send.buffer.size=16 implies a blocking after 4 minutes.
* with a size=512, I am able to run my test for more than 1 hour.
Thanks for your help.
Denis
Le 18/03/2016 22:38, Abhishek Agarwal a écrit :
Do you get this problem if you use only the LoggingMetricsConsumer?
Excuse typos
On Mar 18, 2016 9:38 PM, "Denis DEBARBIEUX" <ddebarbi...@norsys.fr
<mailto:ddebarbi...@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
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel
antivirus Avast.
https://www.avast.com/antivirus
