You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Nathan Gough (Jira)" <ji...@apache.org> on 2019/09/30 15:21:00 UTC
[jira] [Resolved] (NIFI-6624) Automatically migrate old embedded
zookeeper.properties files to the new format
[ https://issues.apache.org/jira/browse/NIFI-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Gough resolved NIFI-6624.
--------------------------------
Resolution: Done
> Automatically migrate old embedded zookeeper.properties files to the new format
> -------------------------------------------------------------------------------
>
> Key: NIFI-6624
> URL: https://issues.apache.org/jira/browse/NIFI-6624
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Affects Versions: 1.9.2
> Reporter: Nathan Gough
> Assignee: Nathan Gough
> Priority: Major
> Fix For: 1.10.0
>
>
> The 3.5.x Zookeeper properties file has changed:
> [https://zookeeper.apache.org/doc/r3.5.2-alpha/zookeeperReconfig.html#sc_reconfig_clientport]
> As a result, the current embedded zookeeper bundled with NiFi will require a minor change to the zookeeper.properties file. We could potentially do this automatically by removing the clientPort line and appending the value to the end of the server string/s.
> The assumption here would be that the client port is currently configured the same across all servers. If not, we would not be able to auto-migrate the change, and we would need to fail the start and get the user to configure the zookeeper.properties file correctly across all nodes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)