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

Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2016/05/16 10:16:12 UTC

[jira] [Resolved] (STORM-1735) Nimbus logs that replication was not reached when min-replication-count was reached exactly

     [ https://issues.apache.org/jira/browse/STORM-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim resolved STORM-1735.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.2
                   2.0.0

Thanks [~Srdo], I merged into master, 1.x, 1.0.x branches.

> 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
>             Fix For: 2.0.0, 1.0.2
>
>
> 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)