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

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

Github user pershyn commented on the pull request:

    https://github.com/apache/storm/pull/527#issuecomment-97111490
  
    I have tested these changes on pure 0.9.3. 
    With them [STORM-770](https://issues.apache.org/jira/browse/STORM-770) 
doesn't break the affected bolts, rather prints warning messages:
    
    ```
    2015-04-27T16:39:02.503+0200 b.s.d.worker [WARN] Can't transfer tuple - 
task value is nil. tuple type: nil and information: nil
    ```
    
    I have also 
[commented](https://issues.apache.org/jira/browse/STORM-770?focusedCommentId=14517213&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14517213)
 STORM-770
    



> Log "task id is null" instead of let worker died (NPE in consumeBatchToCursor)
> ------------------------------------------------------------------------------
>
>                 Key: STORM-790
>                 URL: https://issues.apache.org/jira/browse/STORM-790
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 0.9.2-incubating, 0.9.3, 0.10.0, 0.9.4, 0.11.0
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>
> In STORM-770, some users have observed that worker suddenly died with NPE in 
> consumeBatchToCursor().
> Looks like it can occur when "task" in "mk-transfer-fn" is null.
> It may not be an issue before 0.9.2-incubating, since worker just ignores 
> that tuple. 
> Please see 
> https://issues.apache.org/jira/browse/STORM-770?focusedCommentId=14496199&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14496199.
> Before finding root cause of this issue, it would be better to let worker not 
> killed by this issue but just log with WARN or ERROR level.
> It really makes sense cause before 0.9.2 Storm silently ignores tuple, and 
> with Guaranteeing Message Processing, after timed-out tuple will be replayed. 
> (It isn't applied to non-ack)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to