[jira] [Commented] (NIFI-10081) MergeContent processor is not executed when Scheduling Strategy is set to Cron Driven.

["Etienne Neveu (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572031#comment-17572031 ] 

Etienne Neveu commented on NIFI-10081:
--------------------------------------

We encountered the same issue when upgrading our NiFi cluster from 1.15.3 to 1.16.3 this afternoon.

Our MergeContent processors with a CRON-driven schedule configured to run every 20 minutes stopped merging records.

My colleague tried to configure a 20 min time-driven schedule, but it didn't seem to work either.

He then configured a 1 second time-driven schedule, and when re-starting the processor, it processed the queued input flowfiles.

Weird behaviour. We are rolling back to v1.15.3 to fix our prod, and we'll do some tests on our DEV environment.

> MergeContent processor is not executed when Scheduling Strategy is set to Cron Driven.
> --------------------------------------------------------------------------------------
>
>                 Key: NIFI-10081
>                 URL: https://issues.apache.org/jira/browse/NIFI-10081
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.16.1, 1.16.2
>         Environment: RHEL 7.9, Linux 3.10.0-1160.21.1.el7.x86_64
> java version "1.8.0_331"
> Java(TM) SE Runtime Environment (build 1.8.0_331-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.331-b09, mixed mode)
> Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz
> 6 cores
>            Reporter: Angel Oropeza
>            Priority: Minor
>              Labels: crondriven, merge-content, scheduling
>         Attachments: image-2022-06-01-22-22-32-958.png, image-2022-06-01-22-33-10-811.png, image-2022-06-01-22-33-47-519.png
>
>
> I was able to replicate my problem using the following configuration:
> !image-2022-06-01-22-22-32-958.png!
> The MergeContent configuration is as follows
> !image-2022-06-01-22-33-10-811.png!
> !image-2022-06-01-22-33-47-519.png!
> Although the conditions of the MergeContent processor are met, it does not concatenate the incoming flowfiles.
> The last version in which the above flow worked was version 1.15.3.
> Any suggestions on how to solve this? Is this a bug?
> P.S.: The flow is so designed due to a dependency on only writing one file per day.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)