[
https://issues.apache.org/jira/browse/STORM-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039147#comment-14039147
]
ASF GitHub Bot commented on STORM-360:
--------------------------------------
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/incubator-storm/pull/150#discussion_r14034430
--- Diff: storm-core/src/clj/backtype/storm/ui/core.clj ---
@@ -552,7 +587,11 @@
"processLatency" (float-str (get-in stats [:process-latencies
window]))
"acked" (get-in stats [:acked window])
"failed" (get-in stats [:failed window])
- "lastError" (most-recent-error (get errors id))}))
+ "errorHost" error-host
+ "errorPort" error-port
+ "errorWorkerLogLink" (worker-log-link error-host error-port)
+ "lastError" (get-error-data last-error)
+ }))
--- End diff --
Please put the closing '}))' on the line above.
> 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)
