You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2019. It is now read-only.
The possible steps to implement load balancing with swarm nodes can be enumerated as follows:
Both public and private IP swarm node support because the swarm node may deploy on IoT devices that have private IP only.
First available process in the queue list has the highest priority because of swarm node deploy on a wide variety of devices, we should set the higher level device on the top.
Available process in the queue list means First available process in the list has highest priority refer the chapter of Passenger library documentation for detail. And according to the this, we should put higher level swarm node in the In front of the list of requests handler.
The possible steps to implement load balancing with swarm nodes can be enumerated as follows:
Reference:
The text was updated successfully, but these errors were encountered: