[
https://issues.apache.org/jira/browse/STORM-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259933#comment-15259933
]
ASF GitHub Bot commented on STORM-1735:
---------------------------------------
GitHub user srdo opened a pull request:
https://github.com/apache/storm/pull/1369
STORM-1735: Nimbus should log that replication succeeded when min rep…
…licas was reached exactly
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/srdo/storm STORM-1735
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1369.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 #1369
----
commit 4fdb5e1c7e83ccb95feabffbbf05b52f584cfce2
Author: Stig Rohde Døssing <[email protected]>
Date: 2016-04-27T10:03:43Z
STORM-1735: Nimbus should log that replication succeeded when min replicas
was reached exactly
----
> 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)
