[
https://issues.apache.org/jira/browse/NIFI-10102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-10102.
-----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> MiNiFi stops polling C2 server on PullHttpChangeIngestor after one template
> update
> ----------------------------------------------------------------------------------
>
> Key: NIFI-10102
> URL: https://issues.apache.org/jira/browse/NIFI-10102
> Project: Apache NiFi
> Issue Type: Bug
> Components: MiNiFi
> Affects Versions: 1.16.2
> Reporter: Fabio Coutinho
> Priority: Major
>
> I have just tried out MiNiFi on version 1.16.2 and the issue reported on
> NIFI-9967 (MiNiFi doesn't pick up config.yml changes) was solved but I have
> run into another problem.
> I have setup a MiNiFi agent connecting to a C2 using PullHttpChangeIngestor
> and the C2 is connected to a central NiFi server. When I create a new
> template (for instance changing to .v1 to .v2) everything works out fine and
> the MiNiFi agent reloads the config and starts the new flow (.v2 in this
> example) as expected. However the MiNiFi stops querying the C2 for new
> changes.
> Once I restart the MiNiFi agent process, it starts polling again against
> changes. It seems as if after the configuration reset the Thread responsible
> for checking for changes is stopped and never restarted until a full restart
> of MiNiFi process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
