[
https://issues.apache.org/jira/browse/NIFI-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723489#comment-15723489
]
ASF GitHub Bot commented on NIFI-3150:
--------------------------------------
GitHub user jtstorck opened a pull request:
https://github.com/apache/nifi/pull/1301
NIFI-3150 Added logic to wait for the zk client to connect to the con…
…figured server
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jtstorck/nifi NIFI-3150
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1301.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 #1301
----
commit f439f5a42f5d5962ec6e4ccf3beaf6b2189b8374
Author: Jeff Storck <[email protected]>
Date: 2016-12-05T18:19:31Z
NIFI-3150 Added logic to wait for the zk client to connect to the
configured server
----
> ZooKeeper Migrator does not wait for connection before attempting to
> read/write to ZooKeeper
> --------------------------------------------------------------------------------------------
>
> Key: NIFI-3150
> URL: https://issues.apache.org/jira/browse/NIFI-3150
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 1.1.0
> Reporter: Jeff Storck
> Assignee: Jeff Storck
>
> While running NiFi in a 3-node cluster, attempting to read or write ZK data
> to the ZK ensemble results in intermittent connection loss exceptions because
> the migrator is not waiting for the asynchronous connection method in ZK to
> report that the client has completely connected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
