1·The next step is to attach instances to the load balancer (see Listing 8).
下一步是将实例附加到负载均衡器(见清单8)。
2·The device most often used to do this is a load balancer, which is an appliance that accepts requests from the outside world and hands them off to the next available application server.
进行这一操作最常用的设备是一个负载均衡器，这是一个从外部接收请求并将它们移交给下一个可用应用程序服务器的装置。
3·The first parameter is the name of the load balancer, which is unique to you.
第一个参数是负载均衡器的名称，对您来说是惟一的。
4·Often, in a clustered situation, session state is kept on one computer in the cluster, and the load balancer always directs requests from a user to the machine that is storing his or her session.
通常，在集群的情况下，会话状态保存在集群中的一台计算机上，并且负载均衡器总是把用户的请求重定向到保存他(或她)的会话的机器上。
5·If a cell needs to be removed for maintenance or an upgrade, the load balancer can be directed to send traffic to just the cell that is running.
如果由于维护或者升级的原因需要移除一个单元，负载均衡器可以把流量直接发送到正在运行的那个单元。
1·If, however, the path is not in the cluster directory on the server, the load balancer must query a server in a different cluster.
然而，如果服务器的集群目录内没有该路径，负载平衡器必须在不同的集群中查询服务器。
2·When the client sends data, the load balancer pushes that same data to the destination server.
当客户端发送数据时，负载平衡器将相同的数据推送到目的地服务器。
3·The load balancer USES this information to dispatch requests to the proper server subset.
负载平衡器利用这一信息将需求发送给相应的服务器子集。
4·Those options allow the load balancer to forward requests to a random or the least-busy server node, because every server node has the same session-state information.
因为每一个服务器节点都有相同的对话状态信息，所以这些选项允许负载平衡器将请求转发到随机或最繁忙的服务器节点。
5·It also lets you configure your application's load balancer and auto scaling, which is the option that controls horizontal nodes.
它还允许配置应用程序的负载平衡器和自动伸缩功能，后者是控制水平节点的选项。