You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "timeabarna (via GitHub)" <gi...@apache.org> on 2023/04/25 08:03:18 UTC

[GitHub] [nifi] timeabarna commented on pull request #7185: NIFI-11473 Flow version change in NiFi should not stop a component wh…

timeabarna commented on PR #7185:
URL: https://github.com/apache/nifi/pull/7185#issuecomment-1521344218

   Hello @mattyb149,
   
   I've created a GenerateFlowFile processor which is running.  Created a version where only position changed.
   Added debug point at FlowUpdateResource updateFlow method and a debug point to StandardVersionedFlowSynchronizer updateProcessor method.
   
   At version change, without patch:
   FlowUpdateResource updateFlow runningComponents set contains GenerateFlowFile processor.
   StandardVersionedFlowSynchronizer updateProcessor goes to the updateProcessor if branch
   nifi-app.log shows FlowUpdateResource Stopping 1 Processors and FlowUpdateResource Restarting 1 Processors
   
   With patch:
   FlowUpdateResource updateFlow runningComponents set empty.
   StandardVersionedFlowSynchronizer updateProcessor goes to the setPosition if branch
   nifi-app.log shows FlowUpdateResource Stopping 0 Processors and FlowUpdateResource Restarting 0 Processors
   If my memory serves well only Updating Flow can be seen on UI.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org