You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/05/10 20:23:00 UTC
[jira] [Commented] (NIFI-10976) Add Migration Capabilities from ZooKeeper to Kubernetes
[ https://issues.apache.org/jira/browse/NIFI-10976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721541#comment-17721541 ]
ASF subversion and git services commented on NIFI-10976:
--------------------------------------------------------
Commit e302f2aff7af6ec1165e8fa739eaa63dc7e20699 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e302f2aff7 ]
NIFI-10976 Added Previous Cluster State Provider configuration (#7235)
- Added methods to enumerate Stored Component Identifiers on State Provider interface and implementations
- Added nifi.state.management.provider.cluster.previous to nifi.properties
- Updated State Manager Provider to restore Cluster State from Previous Cluster Provider
- Updated Configuring State Providers documentation for new property
> Add Migration Capabilities from ZooKeeper to Kubernetes
> -------------------------------------------------------
>
> Key: NIFI-10976
> URL: https://issues.apache.org/jira/browse/NIFI-10976
> Project: Apache NiFi
> Issue Type: Sub-task
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Fix For: 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Following initial implementation for the Kubernetes State Provider, migration tools should be created to read from ZooKeeper and write to Kubernetes ConfigMaps. This should facilitate moving existing deployments from ZooKeeper to Kubernetes while preserving cluster state information. The existing ZooKeeper migrator provides a basis for the implementation, but additional work will be necessary to support TLS connections to ZooKeeper. Refactoring the current implementation for more intuitive command design, as support for configurable destinations may be required.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)