[
https://issues.apache.org/jira/browse/NIFI-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222079#comment-15222079
]
ASF GitHub Bot commented on NIFI-1678:
--------------------------------------
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/317#issuecomment-204498317
@mcgilman I agree - we certainly need to address the duplication of
configuration. However, I do believe that is a job for another ticket. I went
ahead and added username/password configs for zookeeper into the
nifi.properties file for now. We can figure out how best to refactor the
configuration in a later ticket before 1.0 is released.
I did push a new commit, which I believe addresses the issue that you laid
out, though, about auth failures. I also found an edge case that wasn't being
handled very well, so I addressed that as well in this latest commit and added
a unit test to verify.
> 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)
