Dear NiFi Development Team, First of all, I would like to express our sincere respect and appreciation for your continuous efforts in developing and maintaining Apache NiFi. Our team has been using NiFi since 2019, and it has played a crucial role in our data processing workflows over the years.
Our Environment: - NiFi Version: 1.22.0 (3-node cluster mode) - Java Version: jdk-11.0.16.1 - Operating System: Red Hat 8.10 - CPU: 32 cores - Memory: 48GB Current Issue: Recently, we have encountered a significant slowdown during NiFi cluster restarts. The startup process takes approximately 10 to 15 minutes, and the `nifi-app.log` indicates that NiFi is spending most of this time restoring components. For example, we see many log entries like: 2025-11-15 15:13:51,911 INFO [main] o.a.n.f.s.StandardVersionedComponentSynchronizer Added Connection[ID=70a5878d-0199-1000-ffff-ffff9a65a5f2, Source ID=7097063b-0199-1000-0000-0000565ddd06, Dest ID=7096bae9-0199-1000-ffff-ffffbae5c592] to StandardProcessGroup[identifier=70967de1-0199-1000-0000-00001dde7b99,name=Filter empty files] 2025-11-15 15:13:51,913 INFO [main] o.a.n.f.s.StandardVersionedComponentSynchronizer Added Connection[ID=7097150c-0199-1000-ffff-ffffd3ea7bb1, Source ID=7096aedf-0199-1000-0000-000061416339, Dest ID=7097063b-0199-1000-0000-0000565ddd06] to StandardProcessGroup[identifier=70967de1-0199-1000-0000-00001dde7b99,name=Filter empty files] 2025-11-15 15:13:51,914 INFO [main] o.a.n.f.s.StandardVersionedComponentSynchronizer Added Connection[ID=70a4170c-0199-1000-0000-00000c861b3a, Source ID=70a1808b-0199-1000-0000-000010d88e3d, Dest ID=92923d85-ec54-12f9-97aa-43ac5442d61c] to StandardProcessGroup[identifier=70967de1-0199-1000-0000-00001dde7b99,name=Filter empty files] 2025-11-15 15:13:51,915 INFO [main] o.a.n.f.s.StandardVersionedComponentSynchronizer Added Connection[ID=70a16555-0199-1000-0000-00002007ddf8, Source ID=7097063b-0199-1000-0000-0000565ddd06, Dest ID=70a1808b-0199-1000-0000-000010d88e3d] to StandardProcessGroup[identifier=70967de1-0199-1000-0000-00001dde7b99,name=Filter empty files] 2025-11-15 15:13:51,915 INFO [main] o.a.n.f.s.StandardVersionedComponentSynchronizer Added Connection[ID=70a3f911-0199-1000-0000-0000498a8368, Source ID=70a1808b-0199-1000-0000-000010d88e3d, Dest ID=7096bae9-0199-1000-ffff-ffffbae5c592] to StandardProcessGroup[identifier=70967de1-0199-1000-0000-00001dde7b99,name=Filter empty files] 2025-11-15 15:13:51,916 INFO [main] o.a.n.f.s.StandardVersionedComponentSynchronizer Added Connection[ID=70a44583-0199-1000-ffff-ffffc73bccdb, Source ID=b4f138b4-271e-16af-b734-a2005561c5b3, Dest ID=b4f138b4-271e-16af-b734-a2005561c5b3] to StandardProcessGroup[identifier=70967de1-0199-1000-0000-00001dde7b99,name=Filter empty files] Our Flow Summary: - Processors: 20,725 - Connections: 34,000 - Process Groups: 217 - Output Ports: 215 We understand that the large number of components on our canvas contributes to the slow startup. However, we believe that there may be room for optimization. Suggestion: Would it be possible to make the `o.a.n.f.s.StandardVersionedComponentSynchronizer Added` process configurable for multi-threading via `nifi.properties`? Allowing this synchronization to run in parallel could significantly reduce startup times, especially for large flows like ours. We would greatly appreciate your consideration of this feature, and we are happy to provide more details or assist with testing if needed. Thank you again for your hard work and dedication to the NiFi project! Best regards, Duke Liu Mediatek
