[
https://issues.apache.org/jira/browse/STORM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546054#comment-14546054
]
ASF GitHub Bot commented on STORM-469:
--------------------------------------
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/388#issuecomment-102503828
> @d2r Thanks, and that is another thing - why do we have log link on port
number?
> That does not make any sense at all.The truncated text is where the user
expects a error log link on.
@rekhajoshm , sorry, somehow I did not get notified of this post.
The worker log link on the port number corresponds to the way the worker
log link is designed into the Executors table on the Component page. The two
are thus consistent. But that does not mean it makes more sense than having
the link to the worker log somewhere else. You have raised a good point.
It turns out that this change breaks the red-coloring of errors reported
less than 5 minutes in age (since it makes the entire text a blue link), so we
need to revert this change for now.
I am -1, since it breaks functionality.
> 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
> Fix For: 0.10.0
>
>
> 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)
