You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2023/08/16 16:18:00 UTC

[jira] [Resolved] (NIFI-10847) Concurrent Multiple Notify Processor make that Wait Processor fails to meet the Target Signal Count.

     [ https://issues.apache.org/jira/browse/NIFI-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann resolved NIFI-10847.
-------------------------------------
    Resolution: Not A Bug

Closing based on description of expected behavior. This could be reopened for further evaluation if there are additional use case details to consider.

> Concurrent Multiple Notify Processor  make that Wait Processor  fails to meet the Target Signal Count.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-10847
>                 URL: https://issues.apache.org/jira/browse/NIFI-10847
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.16.0, 1.17.0
>            Reporter: Zml
>            Assignee: Zml
>            Priority: Minor
>         Attachments: wait-notify_concurrent_start_bug.xml
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The Notify should ensure that the value of the same Identifier is updated synchronously.
>  
> Two Notify Processor, update signal to add 1.
> Excepted: Tagert Signal Value =2   Perform the json merge service
> When all processor start at the same time， the left and right sides take almost the same amount of time.
> Wait processor gets a signal value of 1 instead of the expected 2。
> The Wait  will never wait for the correct target value。
> The Notify should ensure that the value of the same Identifier is updated synchronously.
>  



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