[jira] [Updated] (NIFI-13436) MiNiFi C2 Flow update - Queue is dropped even component exists in the proposed flow

["Ferenc Erdei (Jira)" <ji...@apache.org>]

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

Ferenc Erdei updated NIFI-13436:
--------------------------------
    Fix Version/s: 2.0.0-M4

> MiNiFi C2 Flow update - Queue is dropped even component exists in the proposed flow
> -----------------------------------------------------------------------------------
>
>                 Key: NIFI-13436
>                 URL: https://issues.apache.org/jira/browse/NIFI-13436
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: MiNiFi
>    Affects Versions: 2.0.0-M3
>            Reporter: Ferenc Erdei
>            Assignee: Ferenc Erdei
>            Priority: Minor
>              Labels: minifi-java
>             Fix For: 2.0.0-M4
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> h2. Issue
> When we propose a new flow for a running MiNiFi instance it first stop the source processors and try to wait until a pre-defined graceful period to have empty queues. If remaining items are in the queues after this period, the given flowfiles are dropped.
> This behaviour may cause data loss if the proposed flow contains some existing components.
> h2. Proposed solution
> After the graceful period expires, we should drop flowfiles only from those queues, that don't exist in the proposed flow.



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