[
https://issues.apache.org/jira/browse/STORM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283995#comment-14283995
]
Derek Dagit commented on STORM-469:
-----------------------------------
That could be tricky. The storm worker code would need to know the byte-offset
into the log at which the error occurred and report that as part of the error,
and I'm not sure we would want the worker to know such details of the logging
system.
Recently we started testing a change to storm that allows us to search the most
recent, active worker logs for a fixed string. Once we find the opportunity to
submit it to apache/storm, we could then add a link to perform a search on the
corresponding worker log for that sub-string that we see now. This way the
storm worker code does not have to know where its log messages are going or
know anything about file offsets.
We could click this new link next to the cut-off error text and we would be
able to see any instances in the real worker log file with that error snippet.
> Storm UI Last Error Detail Insufficient for debugging
> -----------------------------------------------------
>
> Key: STORM-469
> URL: https://issues.apache.org/jira/browse/STORM-469
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.9.2-incubating
> Environment: java 1.7 update 67, debian wheezy and squeeze
> Reporter: Jason Kania
> Assignee: Rekha Joshi
>
> The error text that is captured in the Storm UI is insufficient to debug the
> issue as it gets cut off and does not link to the actual error to allow a
> person to get more detail. This means that the debugging is unnecessarily
> blind. This prevents diagnosis of the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
