nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (NIFI-6598) RemoteProcessGroup should utilize ManagedState to persist available peers
Date Tue, 01 Oct 2019 13:57:00 GMT


ASF subversion and git services commented on NIFI-6598:

Commit 6541eac625ff1d721867152d728c53483eab822a in nifi's branch refs/heads/master from Koji
[;h=6541eac ]

NIFI-6598 Storing peers into managed-state
- Fixed checkstyle errors.
- Added PeerPersistence interface.
- Expose RemoteProcessGroup state via REST API
- Made stateManager transient.

This closes #3677.

Signed-off-by: Bryan Bende <>

> RemoteProcessGroup should utilize ManagedState to persist available peers
> -------------------------------------------------------------------------
>                 Key: NIFI-6598
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
> Currently NiFi will persist available remote S2S peers into a local file when a RemoteProcessGroup
connects to a remote cluster, in order to recover peers from that file when the RPG restart
communication next time.
> The default file location is '$NIFI_HOME/conf/state'. Although the location is configurable,
in some deployments, the '$NIFI_HOME/conf' is not writable and NiFi fails to write the file.
> Ideally, instead of writing a local file, such state should be written to managed state
as other components (Processors, ControllerServices) do.
> However, we should leave the option to store peers into a local file for external tools
using SiteToSiteClient, but don't use managed state.

This message was sent by Atlassian Jira

View raw message