[ 
https://issues.apache.org/jira/browse/STORM-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036467#comment-14036467
 ] 

ASF GitHub Bot commented on STORM-360:
--------------------------------------

GitHub user kishorvpatil opened a pull request:

    https://github.com/apache/incubator-storm/pull/150

    [STORM-360]  Add node details for Error Topology and Component pages

    Please note that this would be not a rolling upgrade due to change in 
TaskError struct used to store in znode.
    * Add host, port to ErrorInfo, TaskError, znode
    * Added host, port to trident class ErrorInfo
    * Added host, port to error znodes
    * Displaying host, port and link to log file for errors on 
      * Topology page ( per component in spouts/bolts)
      * Component page
    * Fixed component template to ensure Errors section is displayed on errors.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kishorvpatil/incubator-storm 
node-details-on-error

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-storm/pull/150.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #150
    
----
commit 550a2596f11aff07b893c24b3737c0521ffcd206
Author: Kishor Patil <[email protected]>
Date:   2014-06-18T21:43:10Z

        Show node details on error

----


> 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)

Reply via email to