[
https://issues.apache.org/jira/browse/NIFI-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228892#comment-15228892
]
ASF GitHub Bot commented on NIFI-1678:
--------------------------------------
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/323#issuecomment-206513196
I updated the PR with a new commit to address an issue that I ran into.
When we create 'container' nodes in ZooKeeper whose paths are not sensitive, we
will mark the node as wide-open, rather than applying ACLs. This allows us to
not have to worry about if we have state management and heartbeats using
different ACLs.
Also removed use of username/passwords from ZooKeeper configuration. This
was done because ZooKeeper indicates that these should be used only for local
testing and not for production. In production, security should be administered
via Kerberos. Username and password were always sent over the wire unencrypted.
Additionally, we are now using Apache Curator to handle Leader Election, and
Curator does not appear to support using digest auth via username/password.
> Nodes in cluster should use ZooKeeper to store heartbeat messages instead of
> sending to NCM
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-1678
> URL: https://issues.apache.org/jira/browse/NIFI-1678
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Currently, nodes send heartbeats to the NCM periodically in order to indicate
> that they are actively participating in the cluster. As we move away from
> using an NCM, we need these heartbeats to go somewhere else. ZooKeeper is a
> reasonable location to push the heartbeats to, as it provides the HA that we
> need
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
