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

["Florian Schmidt (Jira)" <ji...@apache.org>]

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

Florian Schmidt commented on NIFI-10081:
----------------------------------------

After we upgraded our NiFi instance from 1.15.3 to 1.16.3 then to 1.17.0 and then to 1.18.0 our MergeContent processor stopped working aswell.

All MergeContent processors with a CRON-driven schedule configured stopped merging records. Also the run once function stopped working.

It looks like the processor consumes the flowfiles in the queue, doesn't merge the records but also holds the flowfiles back so we get the message "The queue has no FlowFiles.". Stop or terminate does not fix that problem and the process still holds the files. The only way we get our files back is to restart the whole instance.

A fix would be highly appreciated.

 
{noformat}
Ubuntu 22.04.1 LTS, Linux 5.15.0-52-generic
OpenJDK 64-Bit Server VM (build 11.0.16+8-post-Ubuntu-0ubuntu122.04, mixed mode, sharing)
12 Cores, AMD Opteron 62xx class CPU @ 2GHz
70 GiB ECC RAM{noformat}
 
 

> 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)