[
https://issues.apache.org/jira/browse/NIFI-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16453038#comment-16453038
]
ASF GitHub Bot commented on NIFI-5092:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2643
+1 LGTM, ran build with unit tests and contrib-check, and verified the
intended behavior. Thanks for this improvement! Merging to master
> S2S Bulletin Reporting Task will not send recent bulletins after a restart
> --------------------------------------------------------------------------
>
> Key: NIFI-5092
> URL: https://issues.apache.org/jira/browse/NIFI-5092
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> Bulletins are stored in memory by NiFi on a 5-minutes rolling window. Each
> bulletin has a bulletin ID and it starts with the value 0. Upon NiFi
> restarts, the new generated bulletins will also have an ID starting with the
> value 0.
> Currently the reporting task is locally storing the ID of the last bulletin
> sent through S2S. But this should not be the case because if the last
> bulletin ID is X when NiFi is restarted, then all new generated bulletins
> with ID <= X will be ignored.
> The state management of this reporting task should be completely removed.
> Starting/stopping the reporting task won't be impacting the behavior since
> the ID of the last bulletin sent is stored in local variable.
> *Current workaround* - after a NiFi restart, stop the reporting task, clear
> the state of the reporting task and start the reporting task.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
