[
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482928#comment-16482928
]
ASF GitHub Bot commented on NIFI-5186:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2722
@joewitt I think I understand now what you were seeing. If I create two
different DebugFlow processors, each with a validation pause of 10 seconds, and
then I create an UpdateAttribute and configure each of them in quick
succession, I see UpdateAttribute in a 'Validating' state for many seconds. I
have created a new JIRA for this, though, NIFI-5222, as I don't think it's
something that should really block merging this PR in. The issue appears to be
that we kick off validation 3 times each time that we click "Update" and so if
we update both DebugFlow processors, we end up kicking off 6 validation tasks
instead of 2, and that ends up blocking UpdateAttribute since we have only 5
threads in the pool.
> Update UI to account for asynchronous validation
> ------------------------------------------------
>
> Key: NIFI-5186
> URL: https://issues.apache.org/jira/browse/NIFI-5186
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Blocker
> Fix For: 1.7.0
>
>
> This Jira is a follow up to NIFI-950. The new asynchronous validation
> introduces a new state VALIDATING. This VALIDATING state will be entered
> following any modifications (create, update) to the component (Processor,
> Controller Service, Reporting Task). All component validation is done in the
> background on a recurring interval. When obtaining the current state, we will
> return the last known state unless it is VALIDATING as a result of a
> modification.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
