Who provides enterprise support for Apache NiFi?
The Apache project provides releases and community help but no support contract. Independent providers such as AceMQ support Apache NiFi on any infrastructure, 24/7, with response targets from 15 minutes, by plan.
What does 24/7 NiFi support cover with AceMQ?
Round-the-clock incident response from 15 minutes on top plans, a written root cause after each P1, plus tuning, certificate advice, capacity reviews and upgrade planning. A typical Sev 1: a node out of disk with a stopped flow. An engineer finds the backpressured connection and frees repository space safely. P2 is 1 hour.
Can you fix a NiFi node that fills its disk and stops processing?
Yes, and it is one of our most common calls. It is almost always a stalled downstream processor plus a connection with no backpressure threshold. We recover space safely through content archive expiration and controlled draining, then set thresholds and separate the repositories.
Why does a NiFi node keep disconnecting from the cluster?
GC pauses longer than the heartbeat interval are the usual cause, followed by ZooKeeper session timeouts under I/O contention and flow mismatch on rejoin. We correlate GC logs, heartbeat timing and ZooKeeper events against disconnect times, then fix heap, timeouts and the flow design behind long pauses.
Can you help with the move from NiFi 1.x to 2.x?
Yes. Apache lists 1.28 as the last 1.x minor release and encourages moving to NiFi 2. We inventory custom processors, rework them against the 2.x extension model, and rehearse the cutover with a rollback.
What are the first things to check when NiFi stalls?
The backpressured connection and its downstream processor, free space on each repository volume, thread pool use, the cluster node count in the UI and certificate expiry dates. Those five checks explain most stalls.
Do you support MiNiFi edge agents?
Yes: agent configuration, connectivity to the central cluster and certificate lifecycle for a fleet.
What does a NiFi health check include?
Repository growth trends, backpressure settings per connection, heap against attribute volume, heartbeat and ZooKeeper timing, certificate expiry, flow drift between nodes, and a ranked remediation plan. Quotes are answered within 1 hour.
Do we need a yearly NiFi support contract?
No. A flow health check, a repository recovery or a NiFi 1.x to 2.x migration plan can be scoped as a separate engagement. Teams whose flows feed revenue or reporting tend to add the annual agreement, which brings 24/7 response and engineers who know the canvas.
What determines the price of NiFi support?
Contracts generally fall between $24,000 and $72,000 a year (USD). Node count, FlowFile throughput, NiFi version, whether Kubernetes is in use, MiNiFi fleet size and the response plan all enter the quote. Send those and we reply with a quote within 1 hour.