Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/317#issuecomment-204434802
Ran into an issue with the PR as is. Specifically, I deployed the
contributions to an existing cluster. The existing cluster had already stored
state in ZK using the configuration from the state-management.xml. During start
up the nodes were unable to heartbeat into ZK because the configuration in
state-management.xml had used a username/password. In order for the heartbeats
to be stored the ZK connection from nifi.properties would also need to be
configured with the same credentials.
As I mentioned in the PR for #301 we should address having duplicate
connect string in nifi.properties and state-management.xml for ZK. A short term
fix for addressing this issue would be to additionally duplicate the remaining
ZK configuration from state-management to nifi.properties. We could take this
temporary approach while we discuss a more appropriate long term strategy for
ZK configuration prior the first 1.x release. Or alternatively, we could
address that issue prior to re-submitting this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
