WebLogic负载平衡 [英] WebLogic load balancing
问题描述
我目前正在开发一个在WebLogic集群环境中受支持的项目.我已经成功设置了集群，但是现在我想要一个负载平衡解决方案(当前，仅出于测试目的，我将WebLogic的HttpClusterServlet与 round-robin 负载平衡一起使用).
是否有任何文档可以清楚地比较各种为WebLogic提供负载平衡的方式(优点和缺点)?
I'm currently developing a project supported on a WebLogic clustered environment. I've successfully set up the cluster, but now I want a load-balancing solution (currently, only for testing purposes, I'm using WebLogic's HttpClusterServlet with round-robin load-balancing).
Is there any documentation that gives a clear comparison (with pros and cons) of the various ways of providing load-balancing for WebLogic?
这些是我要介绍的主要主题:
These are the main topics I want to cover:
- 性能(正常以及故障转移)；
- 可以检测到哪些故障，并且故障转移恢复有多快；
- 透明到失败(例如，能够自动重试幂等请求)；
- 每个负载平衡解决方案如何适应各种拓扑(N层，群集)
- Performance (normal and on failover);
- What failures can be detected and how fast is the failover recovery;
- Transparency to failure (e.g., ability to automatically retry an idempotent request);
- How well is each load-balancing solution adapted to various topologies (N-tier, clustering)
预先感谢您的帮助.
推荐答案
是否有任何文档可以清楚地比较各种为WebLogic提供负载平衡的方式(优点和缺点)?
Is there any documentation that gives a clear comparison (with pros and cons) of the various ways of providing load-balancing for WebLogic?
目前尚不清楚您正在构建哪种应用程序以及所涉及的技术是什么.但是...
It's not clear what kind of application you are building and what kind of technologies are involved. But...
您将在故障转移和复制中找到有用的信息.群集和群集中的负载平衡(另请参见集群实施程序)，但是，至少在我所知的范围内，没有对不同选项进行真正的比较.但是，选择并不那么复杂:1.硬件负载平衡器的性能将比软件负载平衡器好，并且2.如果您选择软件负载平衡器，那么Apache的WebLogic插件是(推荐)BEA推荐的生产选择.实际上，对于Web应用程序，通常将静态文件放在Web服务器上，从而使用Apache mod_wl插件.请参见安装和配置Apache HTTP Server插件章.
You will find useful information in Failover and Replication in a Cluster and Load Balancing in a Cluster (also look at Cluster Implementation Procedures) but, no real comparison between the different options, at least not to my knowledge. But, the choice isn't that complex: 1. Hardware load balancers will perform better than software load balancers and 2. If you go for software load balancers, then WebLogic plugin for Apache is the recommended (by BEA) choice for production. Actually, for web apps, its pretty usual to put the static files on a web server and thus to use the Apache mod_wl plugin. See the Installing and Configuring the Apache HTTP Server Plug-In chapter.
这些是我要介绍的主要主题:
These are the main topics I want to cover:
-
性能(正常和故障转移时)::如果此问题与持久性会话有关，则WebLogic使用
Performance (normal and on failover): If this question is about persistent session, WebLogic uses in memory replication by default and this works pretty well with a relatively low overhead.
可以检测到哪些故障以及故障转移恢复的速度如何:不清楚您使用的是哪种协议.但是请参见连接错误和群集故障转移 .
What failures can be detected and how fast is the failover recovery: It is unclear which protocols you're using. But see Connection Errors and Clustering Failover.
对失败的透明性(例如，自动重试幂等请求的能力):弄清正在使用的协议将使回答变得更加容易.如果此问题与HTTP请求有关，请参见图3-1连接故障转移.
Transparency to failure (e.g., ability to automatically retry an idempotent request): Clarifying the protocols you are using would make answering easier. If this question is about HTTP requests, then see Figure 3-1 Connection Failover.
每种负载均衡解决方案对各种拓扑(N层，群集)的适应程度如何:这个问题尚不清楚，而且太模糊(对我而言).但是，也许可以看看集群体系结构.
How well is each load-balancing solution adapted to various topologies (N-tier, clustering): The question is unclear and too vague (for me). But maybe have a look at Cluster Architectures.
Oh, by the way, another nice chapter that you must read Clustering Best Practices.
这篇关于WebLogic负载平衡的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
