trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r792569 - in /websites/staging/trafficserver/trunk/content/docs/trunk: STATUS admin/cluster-howto/index.en.html
Date Tue, 12 Jul 2011 10:32:33 GMT
Author: buildbot
Date: Tue Jul 12 10:32:32 2011
New Revision: 792569

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/STATUS
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/STATUS
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/STATUS (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/STATUS Tue Jul 12 10:32:32 2011
@@ -64,7 +64,7 @@ hierachical-caching - done (commented ou
 configuring-cache - done
 monitoring-traffic
 configuring-traffic-server
-cluster-howto
+cluster-howto - done
 security-options
 working-log-files
 traffic-line-commands - This needs work!

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html
(original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html
Tue Jul 12 10:32:32 2011
@@ -39,7 +39,7 @@
   <div class="main">
     
     <div id="content">
-      <h2 id="traffic_server_cluster">Traffic Server Cluster</h2>
+      <h1 id="traffic_server_cluster">Traffic Server Cluster</h1>
 <p>Traffic Server scales from a single node to multiple nodes that form a
 cluster allowing you to improve system performance and reliability. This
 chapter discusses the following topics:</p>
@@ -47,7 +47,7 @@ chapter discusses the following topics:<
 <ul>
 <li><a href="#traffic_server_cluster">Traffic Server Cluster</a><ul>
 <li><a href="#UnderstandingTSClusters">Understanding Traffic Server Clusters</a><ul>
-<li><a href="#ManagementOnlyClustering">Management-Only Clustering</a><ul>
+<li><a href="#ManagementOnlyClustering">Management-Only Clustering</a></li>
 <li><a href="#FullClustering">Full Clustering</a></li>
 </ul>
 </li>
@@ -56,10 +56,8 @@ chapter discusses the following topics:<
 </ul>
 </li>
 </ul>
-</li>
-</ul>
 </div>
-<h3 id="UnderstandingTSClusters">Understanding Traffic Server Clusters</h3>
+<h2 id="UnderstandingTSClusters">Understanding Traffic Server Clusters</h2>
 <p>A Traffic Server cluster consists of multiple Traffic Server nodes. The
 nodes in a cluster share configuration information and can form a single
 logical cache. Traffic Server detects the addition and deletion of nodes in
@@ -71,7 +69,7 @@ cluster. Traffic Server has two clusteri
 <li>Management-only mode; refer to Management-Only Clustering below.</li>
 <li>Full-clustering mode; refer to Full Clustering</li>
 </ul>
-<h4 id="ManagementOnlyClustering">Management-Only Clustering</h4>
+<h3 id="ManagementOnlyClustering">Management-Only Clustering</h3>
 <p>In management-only clustering mode, Traffic Server cluster nodes share
 configuration information. You can administer all the nodes at the same
 time. Traffic Server uses a multicast management protocol to provide a
@@ -79,7 +77,7 @@ single system image of your Traffic Serv
 cluster membership, configuration, and exceptions is shared across all
 nodes, and the <code>traffic_manager</code> process automatically propagates
 configuration changes to all the nodes.</p>
-<h4 id="FullClustering">Full Clustering</h4>
+<h3 id="FullClustering">Full Clustering</h3>
 <p>In full-clustering mode, as well as sharing configuration information, a
 Traffic Server cluster distributes its cache across its nodes into a
 single, virtual object store, rather than replicating the cache node by
@@ -96,14 +94,14 @@ protocol to obtain an object from siblin
 references to the missing node on all nodes in the cluster.</p>
 <p>Full clustering recommends a dedicated network interface for cluster
 communication to get better performance.</p>
-<h3 id="EnableClusteringMode">Enable Clustering Mode</h3>
+<h2 id="EnableClusteringMode">Enable Clustering Mode</h2>
 <p>Before you put a node into a Cluster, please make sure the following thing
 checked:</p>
 <ul>
 <li>you are using the samy Operation System:<ul>
 <li>Using the same distrobution, ie: RHEL 5.5</li>
 <li>Have same kernel, ie: 2.6.18-194.17.1.el5</li>
-<li>The same ARCH, ie: x86_64</li>
+<li>The same ARCH, ie: <code>x86_64</code></li>
 </ul>
 </li>
 <li>install with the same version of Traffic Server</li>
@@ -116,33 +114,37 @@ individually. You may following these in
 <ol>
 <li>
 <p>setup the same cluster name, or proxy name, e.g. MyCluster:</p>
-<div class="codehilite"><pre><span class="n">traffic_line</span>
<span class="o">-</span><span class="n">s</span> <span class="n">proxy</span><span
class="o">.</span><span class="n">config</span><span class="o">.</span><span
class="n">proxy_name</span> <span class="o">-</span><span class="n">v</span>
<span class="n">MyCluster</span>
+<div class="codehilite"><pre>traffic_line -s proxy.config.proxy_name -v MyCluster
 </pre></div>
 
 
 </li>
 <li>
 <p>enable cluster mode:</p>
-<div class="codehilite"><pre><span class="n">traffic_line</span>
<span class="o">-</span><span class="n">s</span> <span class="n">proxy</span><span
class="o">.</span><span class="nb">local</span><span class="o">.</span><span
class="n">cluster</span><span class="o">.</span><span class="n">type</span>
<span class="o">-</span><span class="n">v</span> <span class="mi">1</span>
-<span class="n">traffic_line</span> <span class="o">-</span><span
class="n">s</span> <span class="n">proxy</span><span class="o">.</span><span
class="n">config</span><span class="o">.</span><span class="n">cluster</span><span
class="o">.</span><span class="n">ethernet_interface</span> <span
class="o">-</span><span class="n">v</span> <span class="n">eth0</span>
+<div class="codehilite"><pre>traffic_line -s proxy.local.cluster.type -v 1
+traffic_line -s proxy.config.cluster.ethernet_interface -v eth0
 </pre></div>
 
 
-<p>eth0 should be replaced by your real interface, we recommends a 
+<p><code>eth0</code> should be replaced by your real interface, we recommends
a 
  dedicated interface here. Refer to <a href="../configuration-files/records.config#proxy.local.cluster.type"><code>proxy.local.cluster.type</code></a>
  for a full description.</p>
 </li>
 <li>
 <p>enable:</p>
-<p>traffic_line -x</p>
+<div class="codehilite"><pre>traffic_line -x
+</pre></div>
+
+
 </li>
 </ol>
-<p>Traffic Server will join into the Cluster in about 10 seconds, you man run
+<p>Traffic Server will join into the Cluster in about 10 seconds and you can run
 <code>traffic_line -r proxy.process.cluster.nodes</code> to check the hosts in
cluster
-or checkout the cluster.config in config dir.</p>
+or checkout the <a href="../configuration-files/cluster.configcluster.config"><code>cluster.config</code></a>
+in the configuration directory.</p>
 <p>After a successful join of the cluster, all changes of global configurations on
any
 node, will take effect on <strong>all</strong> node now.</p>
-<h3 id="DeletingNodesFromCluster">Deleting Nodes from a Cluster</h3>
+<h2 id="DeletingNodesFromCluster">Deleting Nodes from a Cluster</h2>
 <p>To delete a node from the Traffic Server cluster, just roll back
 <code>proxy.config.cluster.type</code> to the default value 3 and reload.</p>
     </div>



Mime
View raw message