You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@storm.apache.org by Kostya Golikov <jo...@gmail.com> on 2015/03/12 15:49:53 UTC

What is the way to find Trident transaction replays reason?

Hey everybody!

I know I can consult Storm UI, but apparently, UI contains only subset
of errors (the one that extend ReportedFailedException). Currently, we
observe a lot of transaction replays in our Storm installation and there is
no obvious reason for that (no reported exceptions, no worker deaths, no
stacktraces in logs) and it would be nice to know why exactly replay was
triggered. So far it looks as simple as adding single logging statement
<https://github.com/lazyval/storm/commit/7dd4d76a1602f79d24745e2ceebc9f1aca0a76f0>
.

Is there simpler way to nail down transaction replays reason? If not,
should I raise a ticket for inclusion of such logging?