[
https://issues.apache.org/jira/browse/NIFI-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15793142#comment-15793142
]
Joseph Percivall commented on NIFI-3271:
----------------------------------------
The issue of a CRON job schedule running right before the scheduled time was
already brought up on NIFI-3242. Marking this as duplicate.
> GenerateFlowFile processor creates duplicates with CRON scheduling strategy
> and Primary node only execution
> -----------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3271
> URL: https://issues.apache.org/jira/browse/NIFI-3271
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.1.0
> Reporter: Marco Gaido
> Priority: Critical
>
> The most strange thing about this issue is that it came out only today (we
> have been running our flow for two weeks), while until yesterday everything
> worked as expected without any change.
> We have some GenerateFlowFile processors scheduled on a CRON basis, with
> "Primary node only" as execution. Until yesterday, all FlowFiles were
> generated accordingly without any issue. Today, instead, they started
> creating two different flow files. For instance, a processor which should
> have generated a FlowFile at 8:05:00 am indeed generated a FlowFile at
> 08:04:59 am and one at 8:05:00 am. Both the FlowFiles have been generated by
> the Primary node which is the coordinator too.
> The load of the system is quite low, and the heap space utilization is quite
> low too.
> In the Hortonworks community, I found out another guy experiencing the same
> issue on NiFi 1.0.0:
> https://community.hortonworks.com/questions/69734/nifi-100-generateflowfile-processor-creates-duplic.html.
> I can't understand what is happening and which may be the reason of this
> weird behavior. Do you have any idea?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
