I like to know how K2 does NLB, since K2 is composed of components and K2 Server services, how actually does the NLB works when the web tier calls K2 API?
+4
End of the day there is a cluster of K2 servers which all respond to a NLB cluster name. the K2 servers in the cluster constantly talk to each other and keep their process definitions, etc up to date. When your API calls K2 one of the nodes in the cluster will be directed to respond by the NLB.
+2
Thanks Jey, what if the web server/app server and K2 are installed on the same server (Web/app server is NLB)? Would that make any difference?
+3
Since NLB is not a K2 feature I think the answer is going to be general as well. Web servers are often tied together using NLB. Jey already answered about K2 servers. Putting them both on the same server or not doesn't really change anything other than performance considerations. The actual location of the servers doesn't matter so much except for how you install your systems and deploy code or k2 processes.
+9
NLB configuration for a web layer requires you to configure it for session affinity set to single whereas the K2 layer's session affinity is set to none (to conserve server resources). If both K2 and the web layer are on the same boxes, you need to configure the session affinity to single to cater for session state management. This is true unless you are using a central session state management server for your web servers (e.g. SQL server).
Reply
View our Community Site Map
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.