Github user harshach commented on the pull request:
https://github.com/apache/incubator-storm/pull/177#issuecomment-54386752
@anyatch I don't see the above mentioned issue anymore. But for some reason
complete_latency on topology ui goes up very high
window emitted transferred complete latency(ms) acked failed
10m 0s 747380 453520 24592.787 801800 8600
concerned with high complete latency and failed tuples and after a while
topology stops
I understand that WordCountTopologyNode is an example but I think it should
be working properly as users can refer to it as documentation towards writing a
topology in node.js.
I'll try to find more details (new to node.js) this evening. If you can
check why there are failed tuples and complete latency is high that will be
great.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
