[ https://issues.apache.org/jira/browse/NIFI-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651690#comment-15651690 ]
ASF GitHub Bot commented on NIFI-2996: -------------------------------------- GitHub user mosermw opened a pull request: https://github.com/apache/nifi/pull/1192 NIFI-2996 validate processors only when they are in STOPPED state Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder? - [x] Have you written or updated unit tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mosermw/nifi nifi-2996 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1192.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1192 ---- commit 73d444c8164387ea7ed8cc1bc6f118d566f87ed7 Author: Mike Moser <mose...@apache.org> Date: 2016-11-09T17:38:04Z NIFI-2996 validate processors only when they are in STOPPED state ---- > Processor/Service validation takes exponentially longer to run as the graph > grows > --------------------------------------------------------------------------------- > > Key: NIFI-2996 > URL: https://issues.apache.org/jira/browse/NIFI-2996 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.0.0, 0.7.1 > Reporter: Michael Moser > Assignee: Michael Moser > > As you add processors that reference controller services to your NiFi, the > validation that occurs during normal UI usage increases dramatically. > When running in a cluster, I have to increase the nifi.properties > nifi.cluster.node.read.timeout well beyond its 5 sec default timeout in order > for the UI to work. Eventually, simple operations in the UI take close to a > minute to happen. > As a test, I created an SSLContextService using certs created with the > amazingly useful nifi-toolkit. I created a DistributedMapCacheClientService > that references this SSLContextService. Then I created 108 > FetchDistributedMapCache processors that reference the > DistributedMapCacheClient service. I used ${hostname(true)} for my > FetchDistributedMapCache processor's Cache Entry Identifier property. > When NiFi is up with no UI connected, during a single "NiFi status" phase I > noticed that the SSLContextService was validated 108 times and the EL > hostname(true) was evaluated 216 times. When I connect the UI and go through > a normal status refresh cycle, the SSLContextService was validated 432 times > and the EL hostname(true) was evaluated 864 times. These validations take a > full second on my slowest machine. > In NiFi 0.x, the expensive REST API call is > /nifi-api/controller/controller-services/node. > In NiFi 1.x, it appears to divide the work among REST API calls to > /nifi-api/process-groups/UUID and > /nifi-api/flow/process-groups/UUID/controller-services and > /nifi-api/flow/status > Rather than attempting to fix StandardSSLContextService or the EL > HostnameEvaluator, I wonder if there was a more generic approach to helping > resolve this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)