You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "John Joseph (Jira)" <ji...@apache.org> on 2025/10/24 08:25:00 UTC

[jira] [Created] (NIFI-15135) Flow files passing through Notify is not releasing hook in Wait

John Joseph created NIFI-15135:
----------------------------------

             Summary: Flow files passing through Notify is not releasing hook in Wait
                 Key: NIFI-15135
                 URL: https://issues.apache.org/jira/browse/NIFI-15135
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
    Affects Versions: 2.5.0
            Reporter: John Joseph
         Attachments: image-2025-10-24-13-53-04-113.png, image-2025-10-24-13-53-18-208.png, image-2025-10-24-13-53-28-990.png, image-2025-10-24-13-53-48-191.png, image-2025-10-24-13-54-19-958.png

We have nifi 2.5 running on cluster mode.
We have a flow definition that uses Wait and Notify, service used is EmbeddedHazelcastCacheManager and HazelcastMapCacheClient.

The Wait and Notify processors use  the same services, but both of them belong in 2 different sub flow definitions.

We were running performance testing on this flow definition, noticed that though the value passes through Notify processor, the flowfile in the Wait queue was not released.
There are no errors in the logs

We ran with a test case of 70k requests and around 12k of them are waiting in the queue. We checked other application responsible for sending the release hook , it has worked as expected. All these request have also reached its expected final state

We were able to see that the release flowfile has also passed through Notify, but has not actually released it from Wait. 

 

we have default 1 sec scheduling for all the processors 

This is a working template in 1.28.1

 

!image-2025-10-24-13-53-04-113.png!

!image-2025-10-24-13-53-18-208.png!

!image-2025-10-24-13-53-28-990.png!

 

 

!image-2025-10-24-13-53-48-191.png!

 

!image-2025-10-24-13-54-19-958.png!



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