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

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

Github user HeartSaVioR commented on the pull request:

    https://github.com/apache/storm/pull/1369#issuecomment-216472728
  
    +1 Nice finding.
    @srdo I could cherry-pick into 1.x-branch since changeset is really small 
but then merging should wait to release 1.0.1. Could you craft pull request 
against 1.x-branch if you really don't mind?


> Nimbus logs that replication was not reached when min-replication-count was 
> reached exactly
> -------------------------------------------------------------------------------------------
>
>                 Key: STORM-1735
>                 URL: https://issues.apache.org/jira/browse/STORM-1735
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Minor
>
> When waiting for replication during topology submission, Nimbus logs whether 
> replication succeeded within the timeout or not. The check for whether to log 
> that it timed out or succeeded is off by one.



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

Reply via email to