[
https://issues.apache.org/jira/browse/STORM-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039227#comment-14039227
]
ASF GitHub Bot commented on STORM-360:
--------------------------------------
Github user d2r commented on a diff in the pull request:
https://github.com/apache/incubator-storm/pull/150#discussion_r14037320
--- Diff: storm-core/src/ui/public/component.html ---
@@ -92,10 +96,6 @@
$("#bolt-executor-table").tablesorter({ sortList:
[[0,0]], headers: {}});
}
}
-
componentErrors.append(Mustache.render($(template).filter("#component-errors-template").html(),response));
- if(response["componentErrors"].length > 0) {
- $("#component-errors-table").tablesorter({ sortList:
[[0,0]], headers: {1: { sorter: "stormtimestr"}}});
- }
--- End diff --
Curious, why was this needed?
> Add woker-id/host info/port info to the error for easy tracking on UI
> ---------------------------------------------------------------------
>
> Key: STORM-360
> URL: https://issues.apache.org/jira/browse/STORM-360
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Reporter: Kishor Patil
> Labels: master
>
> As the ErrorInfo get from nimbus has no detailed information of where did
> this error happen. Can task id host/port for can be added to the error
> information? It can easy storm debug. Currently we also can only see the
> error information in UI but cannot which component throws this exception and
> track it to logs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
