geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Geronimo v3.0 > Clustering and farming
Date Tue, 25 Jan 2011 08:16:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2036/9/4/_/styles/combined.css?spaceKey=GMOxDOC30&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/GMOxDOC30/Clustering+and+farming">Clustering
and farming</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~maojia508">maojia</a>
    </h4>
        <br/>
                         <h4>Changes (3)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-unchanged" >{excerpt}These topics are about how
to set up a cluster and perform server farming.{excerpt} <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >A _cluster_ or _server farm_ is
a group of servers that transparently provide enterprise services, such as Servlets and JavaServer
Pages (JSP) support, as if it <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">was</span>
<span class="diff-added-words"style="background-color: #dfd;">were</span> a single
server. The servers, typically running on separate systems, exchange messages to synchronize
<span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">data,
allowing</span> <span class="diff-added-words"style="background-color: #dfd;">data.
Therefore,</span> any individual node <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">to</span>
<span class="diff-added-words"style="background-color: #dfd;">can</span> process
requests for a distributed application and <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">to</span>
take over a user&#39;s session when its node fails. Configuring multiple servers into
a cluster is commonly called _clustering_. <br></td></tr>
            <tr><td class="diff-unchanged" > <br>Consider using a cluster
of servers when you need to improve the scalability or the availability or your Web applications.
<br></td></tr>
            <tr><td class="diff-changed-lines" >* Clustering improves <span
class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">scalability
by allowing you to</span> <span class="diff-added-words"style="background-color:
#dfd;">scalability. You can</span> increase the system capacity by adding extra <span
class="diff-changed-words">servers<span class="diff-added-chars"style="background-color:
#dfd;"> to the cluster</span>.</span> Load balancing is achieved by adding
a component, like the remote Apache HTTP Server with the Apache Tomcat JK module that sprays
requests to each node in the cluster. <br></td></tr>
            <tr><td class="diff-unchanged" >** Running multiple nodes on the same
host, called _vertical clustering_, is used when limitations in a single node prevent it from
fully utilizing the capacity of the host. <br>** Running multiple nodes on different
hosts, called _horizontal clustering_, is used to add capacity by adding an additional host.
Horizontal clustering is more common than vertical clustering because it also improves availability.
<br></td></tr>
            <tr><td class="diff-changed-lines" >* Clustering improves availability
by automatically synchronizing state data among all the nodes in the cluster. If any node
in the cluster fails, <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">subsequent
requests can be processed by</span> any other node in the <span class="diff-changed-words">cluster<span
class="diff-added-chars"style="background-color: #dfd;"> can process the subsequent requests</span>.</span>
This process, typically called _failover_, occurs on subsequent requests. Any requests being
processed by a node when it fails will still be lost. <br></td></tr>
            <tr><td class="diff-unchanged" > <br>This section is organized
as follows: <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <p>These topics are about how to set up a cluster and perform server farming.</p>

<p>A <em>cluster</em> or <em>server farm</em> is a group of
servers that transparently provide enterprise services, such as Servlets and JavaServer Pages
(JSP) support, as if it were a single server. The servers, typically running on separate systems,
exchange messages to synchronize data. Therefore, any individual node can process requests
for a distributed application and take over a user's session when its node fails. Configuring
multiple servers into a cluster is commonly called <em>clustering</em>.</p>

<p>Consider using a cluster of servers when you need to improve the scalability or the
availability or your Web applications.</p>
<ul>
	<li>Clustering improves scalability. You can increase the system capacity by adding
extra servers to the cluster. Load balancing is achieved by adding a component, like the remote
Apache HTTP Server with the Apache Tomcat JK module that sprays requests to each node in the
cluster.
	<ul>
		<li>Running multiple nodes on the same host, called <em>vertical clustering</em>,
is used when limitations in a single node prevent it from fully utilizing the capacity of
the host.</li>
		<li>Running multiple nodes on different hosts, called <em>horizontal clustering</em>,
is used to add capacity by adding an additional host. Horizontal clustering is more common
than vertical clustering because it also improves availability.</li>
	</ul>
	</li>
	<li>Clustering improves availability by automatically synchronizing state data among
all the nodes in the cluster. If any node in the cluster fails, any other node in the cluster
can process the subsequent requests. This process, typically called <em>failover</em>,
occurs on subsequent requests. Any requests being processed by a node when it fails will still
be lost.</li>
</ul>


<p>This section is organized as follows:</p>
<ul><li><a href="/confluence/display/GMOxDOC30/EJB+failover" title="EJB failover">EJB
failover</a> &mdash; <span class="smalltext">In Geronimo, you can configure
<a href="http://openejb.apache.org/3.0/failover.html" title="OpenEJB failover" class="external-link"
rel="nofollow">OpenEJB for failover scenarios</a>, such as multipoint and multicast.
Further more, Geronimo uses WADI to support failover for Stateful Session Bean (SFSB) in a
unicast way.</span></li><li><a href="/confluence/display/GMOxDOC30/Farming+using+Deployment"
title="Farming using Deployment">Farming using Deployment</a> &mdash; <span
class="smalltext">A configuration can be deployed to a cluster of Geronimo servers via
a single logical deployment step.</span></li><li><a href="/confluence/display/GMOxDOC30/JMS+clustering+in+Geronimo"
title="JMS clustering in Geronimo">JMS clustering in Geronimo</a> &mdash; <span
class="smalltext">JMS clustering in Geronimo is handled by ActiveMQ component directly.</span></li><li><a
href="/confluence/display/GMOxDOC30/Plugin+based+Farming" title="Plugin based Farming">Plugin
based Farming</a> &mdash; <span class="smalltext">This farming system uses
plugins directly and is thus decoupled from the deployment system and allows running the plugin
packaging (or "deployment") and farm administration on different servers or machines.</span></li><li><a
href="/confluence/display/GMOxDOC30/Tomcat+Native+Clustering" title="Tomcat Native Clustering">Tomcat
Native Clustering</a> &mdash; <span class="smalltext">The Tomcat Web container
provides a native clustering solution that can be configured through Geronimo using gbean
definitions within <tt>config.xml</tt> or using <tt>server.xml</tt>
starting from v2.2 just like you did for a standalone Tomcat server.</span></li><li><a
href="/confluence/display/GMOxDOC30/WADI+Clustering" title="WADI Clustering">WADI Clustering</a>
&mdash; <span class="smalltext">Web-applications and Stateful SessionBeans (Geronimo
2.2+) can be clustered by WADI.</span></li></ul>
    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/GMOxDOC30/Clustering+and+farming">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=20645451&revisedVersion=2&originalVersion=1">View
Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/GMOxDOC30/Clustering+and+farming?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message