[
https://issues.apache.org/jira/browse/MINIFICPP-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Szasz resolved MINIFICPP-1784.
-------------------------------------
Fix Version/s: 0.12.0
Assignee: Marton Szasz
Resolution: Fixed
> Restart agent after C2 property update
> --------------------------------------
>
> Key: MINIFICPP-1784
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1784
> Project: Apache NiFi MiNiFi C++
> Issue Type: Epic
> Reporter: Gábor Gyimesi
> Assignee: Marton Szasz
> Priority: Minor
> Fix For: 0.12.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Some properties are only applied after the MiNiFi agent is restarted, so to
> be more straightforward it's better to restart the agent after every C2
> property update.
> To be compliant with the kubernetes use case, we should also add a script in
> the docker image to start the agent and restart it when it stops due to
> property update. For this there should be a special exit code to indicate the
> shutdown happened due to property update. In native Windows and Linux
> environments this should be taken care of by the windows service and systemd.
> This change should also pay attention to batch C2 commands, as multiple C2
> commands with multiple updates could happen in a single heartbeat response.
> If there is a property update in a heartbeat response with multiple C2
> commands, the shutdown should only happen after all C2 commands are processed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
