Based on official figures a WNLB cluster should support up to 32 nodes. Manual configuration of all nodes is required making it more difficult to scale and troubleshoot.Since WNLB is incompatible with Windows Clustering, WNLB cannot be used for application such as Exchange DAGs where this is used.Only supports source IP address affinity/persistence.All hosts in a cluster must be located in the same subnet.Unable to consider each servers current CPU load and RAM utilisation when distributing client load.If a particular server service fails, WNLB cannot detect the failure and will still route requests to that server. It can only detect server outage by IP address. Potential uneven spread of workloads across cluster nodes resulting in slow user response times and high latency for the application. Does not support multiple scheduling algorithms for distributing client load.Unicast mode relies on this to operate, multicast mode also causes switch flooding unless the switch is configured with static mappings of the multicast MAC addresses to the ports that the NLB nodes are connected to. Whilst Windows Network Load Balancing (WNLB) has been constantly improved in each version of Windows since it's introduction in Windows 2000, it still has a fairly extensive list of disadvantages when compared to a hardware or virtual based loadbalancer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |