You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/06/22 06:22:00 UTC

[jira] [Commented] (STORM-809) topology.message.timeout.secs should not allow for null or <= 0 values

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

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

Github user harshach commented on the pull request:

    https://github.com/apache/storm/pull/544#issuecomment-113997109
  
    +1


> topology.message.timeout.secs should not allow for null or <= 0 values
> ----------------------------------------------------------------------
>
>                 Key: STORM-809
>                 URL: https://issues.apache.org/jira/browse/STORM-809
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>
> topology.message.timeout.secs has bad things happen if it is set to null or <= 0.  If it is null killing or rebalancing a topology without providing a timeout results in an NPE.  <= 0 causes other periodic things to run too frequently.



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