Hi,

Our network administrators are unable to wire up advanced Load Balancer (AWS 
Application Load Balancer) or (Apache reverse proxy) to leverage a NIFI API 
that may be listening on a port across several nodes.

For instance, a HandleHttpRequest listing on Node-1 on PORT 5112, Node-2 on 
5112, Node-3 on 5112, and so on and so forth…

In an event where a NODE is down (or API stops listening, it happens), or 
disconnected, a call to that Node and PORT will fail and be a pretty bad 
experience for the customer

So

What we would like to have is an external Load Balancer be able to use Round 
Robin (Advanced Features) to redirect the request to an UP Node, but to do this 
the Load Balancer needs a proper health check.

What is a proper “Health Check” for this scenario? How would it be created and 
wired up?

Right now, an API requested that is hosted on NIFI that is proxied by our API 
Manager (WSO2) will fail on the down NODE and not recover - user will probably 
get a 500. APIM is not a good load balancer.

Thanks in advance for this discussion


Best Regards
John Gunvaldson

Reply via email to