[ https://issues.apache.org/jira/browse/NIFI-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942264#comment-16942264 ]
Rob Fellows commented on NIFI-6735: ----------------------------------- At first, I was unable to reproduce this bug. However, by adding a {{customValidate}} method override to {{ListFile.java}} with a {{Thread.sleep(10000L)}}, I was able to force it. > Updating parameter used by running processor can result in the processor not > restarting because it doesn't wait for validation to complete. > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: NIFI-6735 > URL: https://issues.apache.org/jira/browse/NIFI-6735 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.10.0 > Reporter: Rob Fellows > Assignee: Rob Fellows > Priority: Major > Fix For: 1.10.0 > > Attachments: Processor fails to restart.png > > > There is a timing issue when updating a parameter that is referenced by a > running processor. Updating the parameter context stops the processor and > tries to restart it. However, validation of the processor might not be > complete by the time it is attempted to be restarted and you can get an error > (see attached image) and the processor does not restart automatically. > > Steps to reproduce: > 1) Create a process group with a ListFile and LogAttribute processor . > 2) Have the input dir be a parameter on the ListFile. Set the parameter on > the PG. > 3) Have that running. Then go change the parameter value on the PG level. > It will auto-restart for you but fail because validation wasn't done yet for > ListFIle resulting in a now not running processor. -- This message was sent by Atlassian Jira (v8.3.4#803005)