Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Are there any limits to horizontally scaling Nifi?

Solved Go to solution

Are there any limits to horizontally scaling Nifi?

New Contributor

Is there a maximum amount of nodes a Nifi cluster can contain? If so what and where are the bottlenecks? Are there figures for max data per second or max events per second?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Are there any limits to horizontally scaling Nifi?

Master Guru
@Ben Morris

NiFi has not explicitly defined max for the number of nodes that can be added to a single NiFi cluster.

Just keep in mind that the more nodes you add, the more request replication that must occur between nodes. For example, If a user is connected to node 1 of 100 nodes and makes a change, that change must be replicated to all 99 other nodes. NiFi is configured with a number of node protocol threads (default 10). So NIFi is only capable of replicating that change to 10 nodes at a time. This value should be increased to accommodate larger clusters. Failing to adjust this value my result in nodes disconnecting because they did not receive the change request fast enough. In addition, you may need to be more tolerant on your connection and heartbeat timeouts.

As far as max data per second, that is a hard number to lay out. It is highly dependent on a number of factors.

Mostly affected by your particular dataflow implementation. Since NiFi is just a blank canvas in which you build your dataflow, in the end your dataflow design defines your performance/throughput in most cases. This comes down to which processors you use and how they are configured.

Assuming you have a well designed and optimized dataflow design, you can expect upwards of the following:

39876-screen-shot-2017-10-19-at-84154-am.png

*** These numbers will still be affected by use of some processors. CompressContent for example: this processor can be CPU intensive over longer periods of time when compressing large files, so I can become a bottleneck.

If you found that this answer addressed you question, please take a moment to click "accept".

Thank you,

Matt

2 REPLIES 2

Re: Are there any limits to horizontally scaling Nifi?

Master Guru
@Ben Morris

NiFi has not explicitly defined max for the number of nodes that can be added to a single NiFi cluster.

Just keep in mind that the more nodes you add, the more request replication that must occur between nodes. For example, If a user is connected to node 1 of 100 nodes and makes a change, that change must be replicated to all 99 other nodes. NiFi is configured with a number of node protocol threads (default 10). So NIFi is only capable of replicating that change to 10 nodes at a time. This value should be increased to accommodate larger clusters. Failing to adjust this value my result in nodes disconnecting because they did not receive the change request fast enough. In addition, you may need to be more tolerant on your connection and heartbeat timeouts.

As far as max data per second, that is a hard number to lay out. It is highly dependent on a number of factors.

Mostly affected by your particular dataflow implementation. Since NiFi is just a blank canvas in which you build your dataflow, in the end your dataflow design defines your performance/throughput in most cases. This comes down to which processors you use and how they are configured.

Assuming you have a well designed and optimized dataflow design, you can expect upwards of the following:

39876-screen-shot-2017-10-19-at-84154-am.png

*** These numbers will still be affected by use of some processors. CompressContent for example: this processor can be CPU intensive over longer periods of time when compressing large files, so I can become a bottleneck.

If you found that this answer addressed you question, please take a moment to click "accept".

Thank you,

Matt

Re: Are there any limits to horizontally scaling Nifi?

New Contributor

Hi @Matt Clarke,


Does the table you shared above hold true today as well?


Apache Nifi Crash Course video on https://www.youtube.com/watch?v=fblkgr1PJ0o mentions the same that a cluster should preferably have a single digit number but if really needed you can rather have 2 separate clusters with 10 nodes each and establish a sync between them.


All I am trying to understand is with the latest version it still holds true and 10 nodes are still good to hold hundreds of thousands of events per second?


Thanks in advance!