helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kisho...@apache.org
Subject svn commit: r1486209 [1/13] - in /incubator/helix/site-content: ./ apidocs/reference/org/apache/helix/agent/ apidocs/reference/org/apache/helix/manager/zk/ apidocs/reference/org/apache/helix/recipes/rabbitmq/ helix-admin-webapp/ helix-agent/ helix-core...
Date Fri, 24 May 2013 20:30:43 GMT
Author: kishoreg
Date: Fri May 24 20:30:39 2013
New Revision: 1486209

URL: http://svn.apache.org/r1486209
Log:
Site checkin for project Apache Helix

Added:
    incubator/helix/site-content/xref-test/org/apache/helix/manager/zk/TestZkClient.html
Modified:
    incubator/helix/site-content/Architecture.html
    incubator/helix/site-content/Concepts.html
    incubator/helix/site-content/Features.html
    incubator/helix/site-content/Quickstart.html
    incubator/helix/site-content/Tutorial.html
    incubator/helix/site-content/UseCases.html
    incubator/helix/site-content/apidocs/reference/org/apache/helix/agent/ProcessMonitorThread.html
    incubator/helix/site-content/apidocs/reference/org/apache/helix/manager/zk/ZkCacheEventThread.html
    incubator/helix/site-content/apidocs/reference/org/apache/helix/recipes/rabbitmq/ConsumerThread.html
    incubator/helix/site-content/checkstyle-aggregate.html
    incubator/helix/site-content/checkstyle.rss
    incubator/helix/site-content/dependencies.html
    incubator/helix/site-content/dependency-convergence.html
    incubator/helix/site-content/dependency-info.html
    incubator/helix/site-content/dependency-management.html
    incubator/helix/site-content/distribution-management.html
    incubator/helix/site-content/download.html
    incubator/helix/site-content/helix-admin-webapp/dependencies.html
    incubator/helix/site-content/helix-admin-webapp/dependency-convergence.html
    incubator/helix/site-content/helix-admin-webapp/dependency-info.html
    incubator/helix/site-content/helix-admin-webapp/dependency-management.html
    incubator/helix/site-content/helix-admin-webapp/distribution-management.html
    incubator/helix/site-content/helix-admin-webapp/index.html
    incubator/helix/site-content/helix-admin-webapp/integration.html
    incubator/helix/site-content/helix-admin-webapp/issue-tracking.html
    incubator/helix/site-content/helix-admin-webapp/license.html
    incubator/helix/site-content/helix-admin-webapp/mail-lists.html
    incubator/helix/site-content/helix-admin-webapp/plugin-management.html
    incubator/helix/site-content/helix-admin-webapp/plugins.html
    incubator/helix/site-content/helix-admin-webapp/project-info.html
    incubator/helix/site-content/helix-admin-webapp/project-reports.html
    incubator/helix/site-content/helix-admin-webapp/project-summary.html
    incubator/helix/site-content/helix-admin-webapp/sonar.html
    incubator/helix/site-content/helix-admin-webapp/source-repository.html
    incubator/helix/site-content/helix-admin-webapp/team-list.html
    incubator/helix/site-content/helix-agent/dependencies.html
    incubator/helix/site-content/helix-agent/dependency-convergence.html
    incubator/helix/site-content/helix-agent/dependency-info.html
    incubator/helix/site-content/helix-agent/dependency-management.html
    incubator/helix/site-content/helix-agent/distribution-management.html
    incubator/helix/site-content/helix-agent/index.html
    incubator/helix/site-content/helix-agent/integration.html
    incubator/helix/site-content/helix-agent/issue-tracking.html
    incubator/helix/site-content/helix-agent/license.html
    incubator/helix/site-content/helix-agent/mail-lists.html
    incubator/helix/site-content/helix-agent/plugin-management.html
    incubator/helix/site-content/helix-agent/plugins.html
    incubator/helix/site-content/helix-agent/project-info.html
    incubator/helix/site-content/helix-agent/project-reports.html
    incubator/helix/site-content/helix-agent/project-summary.html
    incubator/helix/site-content/helix-agent/sonar.html
    incubator/helix/site-content/helix-agent/source-repository.html
    incubator/helix/site-content/helix-agent/team-list.html
    incubator/helix/site-content/helix-core/dependencies.html
    incubator/helix/site-content/helix-core/dependency-convergence.html
    incubator/helix/site-content/helix-core/dependency-info.html
    incubator/helix/site-content/helix-core/dependency-management.html
    incubator/helix/site-content/helix-core/distribution-management.html
    incubator/helix/site-content/helix-core/index.html
    incubator/helix/site-content/helix-core/integration.html
    incubator/helix/site-content/helix-core/issue-tracking.html
    incubator/helix/site-content/helix-core/license.html
    incubator/helix/site-content/helix-core/mail-lists.html
    incubator/helix/site-content/helix-core/plugin-management.html
    incubator/helix/site-content/helix-core/plugins.html
    incubator/helix/site-content/helix-core/project-info.html
    incubator/helix/site-content/helix-core/project-reports.html
    incubator/helix/site-content/helix-core/project-summary.html
    incubator/helix/site-content/helix-core/sonar.html
    incubator/helix/site-content/helix-core/source-repository.html
    incubator/helix/site-content/helix-core/team-list.html
    incubator/helix/site-content/index.html
    incubator/helix/site-content/integration.html
    incubator/helix/site-content/involved/building.html
    incubator/helix/site-content/issue-tracking.html
    incubator/helix/site-content/jira-report.html
    incubator/helix/site-content/license.html
    incubator/helix/site-content/mail-lists.html
    incubator/helix/site-content/mockservice/dependencies.html
    incubator/helix/site-content/mockservice/dependency-convergence.html
    incubator/helix/site-content/mockservice/dependency-info.html
    incubator/helix/site-content/mockservice/dependency-management.html
    incubator/helix/site-content/mockservice/distribution-management.html
    incubator/helix/site-content/mockservice/index.html
    incubator/helix/site-content/mockservice/integration.html
    incubator/helix/site-content/mockservice/issue-tracking.html
    incubator/helix/site-content/mockservice/license.html
    incubator/helix/site-content/mockservice/mail-lists.html
    incubator/helix/site-content/mockservice/plugin-management.html
    incubator/helix/site-content/mockservice/plugins.html
    incubator/helix/site-content/mockservice/project-info.html
    incubator/helix/site-content/mockservice/project-reports.html
    incubator/helix/site-content/mockservice/project-summary.html
    incubator/helix/site-content/mockservice/sonar.html
    incubator/helix/site-content/mockservice/source-repository.html
    incubator/helix/site-content/mockservice/team-list.html
    incubator/helix/site-content/modules.html
    incubator/helix/site-content/plugin-management.html
    incubator/helix/site-content/plugins.html
    incubator/helix/site-content/privacy-policy.html
    incubator/helix/site-content/project-info.html
    incubator/helix/site-content/project-reports.html
    incubator/helix/site-content/project-summary.html
    incubator/helix/site-content/recipes/dependencies.html
    incubator/helix/site-content/recipes/dependency-convergence.html
    incubator/helix/site-content/recipes/dependency-info.html
    incubator/helix/site-content/recipes/dependency-management.html
    incubator/helix/site-content/recipes/distributed-lock-manager/dependencies.html
    incubator/helix/site-content/recipes/distributed-lock-manager/dependency-convergence.html
    incubator/helix/site-content/recipes/distributed-lock-manager/dependency-info.html
    incubator/helix/site-content/recipes/distributed-lock-manager/dependency-management.html
    incubator/helix/site-content/recipes/distributed-lock-manager/distribution-management.html
    incubator/helix/site-content/recipes/distributed-lock-manager/index.html
    incubator/helix/site-content/recipes/distributed-lock-manager/integration.html
    incubator/helix/site-content/recipes/distributed-lock-manager/issue-tracking.html
    incubator/helix/site-content/recipes/distributed-lock-manager/license.html
    incubator/helix/site-content/recipes/distributed-lock-manager/mail-lists.html
    incubator/helix/site-content/recipes/distributed-lock-manager/plugin-management.html
    incubator/helix/site-content/recipes/distributed-lock-manager/plugins.html
    incubator/helix/site-content/recipes/distributed-lock-manager/project-info.html
    incubator/helix/site-content/recipes/distributed-lock-manager/project-reports.html
    incubator/helix/site-content/recipes/distributed-lock-manager/project-summary.html
    incubator/helix/site-content/recipes/distributed-lock-manager/sonar.html
    incubator/helix/site-content/recipes/distributed-lock-manager/source-repository.html
    incubator/helix/site-content/recipes/distributed-lock-manager/team-list.html
    incubator/helix/site-content/recipes/distribution-management.html
    incubator/helix/site-content/recipes/index.html
    incubator/helix/site-content/recipes/integration.html
    incubator/helix/site-content/recipes/issue-tracking.html
    incubator/helix/site-content/recipes/license.html
    incubator/helix/site-content/recipes/lock_manager.html
    incubator/helix/site-content/recipes/mail-lists.html
    incubator/helix/site-content/recipes/modules.html
    incubator/helix/site-content/recipes/plugin-management.html
    incubator/helix/site-content/recipes/plugins.html
    incubator/helix/site-content/recipes/project-info.html
    incubator/helix/site-content/recipes/project-reports.html
    incubator/helix/site-content/recipes/project-summary.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/dependencies.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/dependency-convergence.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/dependency-info.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/dependency-management.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/distribution-management.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/index.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/integration.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/issue-tracking.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/license.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/mail-lists.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/plugin-management.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/plugins.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/project-info.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/project-reports.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/project-summary.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/sonar.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/source-repository.html
    incubator/helix/site-content/recipes/rabbitmq-consumer-group/team-list.html
    incubator/helix/site-content/recipes/rabbitmq_consumer_group.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/dependencies.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/dependency-convergence.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/dependency-info.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/dependency-management.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/distribution-management.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/index.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/integration.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/issue-tracking.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/license.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/mail-lists.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/plugin-management.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/plugins.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/project-info.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/project-reports.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/project-summary.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/sonar.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/source-repository.html
    incubator/helix/site-content/recipes/rsync-replicated-file-system/team-list.html
    incubator/helix/site-content/recipes/rsync_replicated_file_store.html
    incubator/helix/site-content/recipes/service-discovery/dependencies.html
    incubator/helix/site-content/recipes/service-discovery/dependency-convergence.html
    incubator/helix/site-content/recipes/service-discovery/dependency-info.html
    incubator/helix/site-content/recipes/service-discovery/dependency-management.html
    incubator/helix/site-content/recipes/service-discovery/distribution-management.html
    incubator/helix/site-content/recipes/service-discovery/index.html
    incubator/helix/site-content/recipes/service-discovery/integration.html
    incubator/helix/site-content/recipes/service-discovery/issue-tracking.html
    incubator/helix/site-content/recipes/service-discovery/license.html
    incubator/helix/site-content/recipes/service-discovery/mail-lists.html
    incubator/helix/site-content/recipes/service-discovery/plugin-management.html
    incubator/helix/site-content/recipes/service-discovery/plugins.html
    incubator/helix/site-content/recipes/service-discovery/project-info.html
    incubator/helix/site-content/recipes/service-discovery/project-reports.html
    incubator/helix/site-content/recipes/service-discovery/project-summary.html
    incubator/helix/site-content/recipes/service-discovery/sonar.html
    incubator/helix/site-content/recipes/service-discovery/source-repository.html
    incubator/helix/site-content/recipes/service-discovery/team-list.html
    incubator/helix/site-content/recipes/service_discovery.html
    incubator/helix/site-content/recipes/sonar.html
    incubator/helix/site-content/recipes/source-repository.html
    incubator/helix/site-content/recipes/task-execution/dependencies.html
    incubator/helix/site-content/recipes/task-execution/dependency-convergence.html
    incubator/helix/site-content/recipes/task-execution/dependency-info.html
    incubator/helix/site-content/recipes/task-execution/dependency-management.html
    incubator/helix/site-content/recipes/task-execution/distribution-management.html
    incubator/helix/site-content/recipes/task-execution/index.html
    incubator/helix/site-content/recipes/task-execution/integration.html
    incubator/helix/site-content/recipes/task-execution/issue-tracking.html
    incubator/helix/site-content/recipes/task-execution/license.html
    incubator/helix/site-content/recipes/task-execution/mail-lists.html
    incubator/helix/site-content/recipes/task-execution/plugin-management.html
    incubator/helix/site-content/recipes/task-execution/plugins.html
    incubator/helix/site-content/recipes/task-execution/project-info.html
    incubator/helix/site-content/recipes/task-execution/project-reports.html
    incubator/helix/site-content/recipes/task-execution/project-summary.html
    incubator/helix/site-content/recipes/task-execution/sonar.html
    incubator/helix/site-content/recipes/task-execution/source-repository.html
    incubator/helix/site-content/recipes/task-execution/team-list.html
    incubator/helix/site-content/recipes/task_dag_execution.html
    incubator/helix/site-content/recipes/team-list.html
    incubator/helix/site-content/releasenotes/release-0.6.0-incubating.html
    incubator/helix/site-content/releasenotes/release-0.6.1-incubating.html
    incubator/helix/site-content/releasing.html
    incubator/helix/site-content/sonar.html
    incubator/helix/site-content/source-repository.html
    incubator/helix/site-content/team-list.html
    incubator/helix/site-content/tutorial_admin.html
    incubator/helix/site-content/tutorial_controller.html
    incubator/helix/site-content/tutorial_health.html
    incubator/helix/site-content/tutorial_messaging.html
    incubator/helix/site-content/tutorial_participant.html
    incubator/helix/site-content/tutorial_propstore.html
    incubator/helix/site-content/tutorial_rebalance.html
    incubator/helix/site-content/tutorial_spectator.html
    incubator/helix/site-content/tutorial_state.html
    incubator/helix/site-content/tutorial_throttling.html
    incubator/helix/site-content/xref-test/allclasses-frame.html
    incubator/helix/site-content/xref-test/org/apache/helix/integration/TestMessagingService.html
    incubator/helix/site-content/xref-test/org/apache/helix/integration/TestSchedulerMessage.html
    incubator/helix/site-content/xref-test/org/apache/helix/integration/package-frame.html
    incubator/helix/site-content/xref-test/org/apache/helix/integration/package-summary.html
    incubator/helix/site-content/xref-test/org/apache/helix/manager/zk/package-frame.html
    incubator/helix/site-content/xref-test/org/apache/helix/manager/zk/package-summary.html
    incubator/helix/site-content/xref-test/org/apache/helix/messaging/handling/TestConfigThreadpoolSize.html
    incubator/helix/site-content/xref/allclasses-frame.html
    incubator/helix/site-content/xref/org/apache/helix/messaging/handling/CurrentStateUpdate.html
    incubator/helix/site-content/xref/org/apache/helix/messaging/handling/GroupMessageHandler.html
    incubator/helix/site-content/xref/org/apache/helix/messaging/handling/HelixStateTransitionHandler.html
    incubator/helix/site-content/xref/org/apache/helix/messaging/handling/package-frame.html
    incubator/helix/site-content/xref/org/apache/helix/messaging/handling/package-summary.html
    incubator/helix/site-content/xref/org/apache/helix/model/AlertStatus.html
    incubator/helix/site-content/xref/org/apache/helix/model/Alerts.html
    incubator/helix/site-content/xref/org/apache/helix/model/package-frame.html
    incubator/helix/site-content/xref/org/apache/helix/model/package-summary.html

Modified: incubator/helix/site-content/Architecture.html
URL: http://svn.apache.org/viewvc/incubator/helix/site-content/Architecture.html?rev=1486209&r1=1486208&r2=1486209&view=diff
==============================================================================
--- incubator/helix/site-content/Architecture.html (original)
+++ incubator/helix/site-content/Architecture.html Fri May 24 20:30:39 2013
@@ -1,13 +1,13 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia at May 22, 2013
+ | Generated by Apache Maven Doxia at May 24, 2013
  | Rendered using Apache Maven Fluido Skin 1.3.0
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <meta name="Date-Revision-yyyymmdd" content="20130522" />
+    <meta name="Date-Revision-yyyymmdd" content="20130524" />
     <meta http-equiv="Content-Language" content="en" />
     <title>Apache Helix - </title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -168,7 +168,7 @@
                 
                 
             
-                  <li id="publishDate" class="pull-right">Last Published: 2013-05-22</li> 
+                  <li id="publishDate" class="pull-right">Last Published: 2013-05-24</li> 
             
                             </ul>
       </div>
@@ -193,11 +193,11 @@ software distributed under the License i
 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 KIND, either express or implied.  See the License for the
 specific language governing permissions and limitations
-under the License. --><p>Helix aims to provide the following abilities to a distributed system</p>
+under the License. --><p>Helix aims to provide the following abilities to a distributed system:</p>
 <ul>
-  <li>Auto management of a cluster hosting partitioned, replicated resources</li>
+  <li>Automatic management of a cluster hosting partitioned, replicated resources.</li>
   <li>Soft and hard failure detection and handling.</li>
-  <li>Automatic load balancing via smart placement of resources on servers(nodes) based on server capacity and resource profile (size of partition, access patterns, etc)</li>
+  <li>Automatic load balancing via smart placement of resources on servers(nodes) based on server capacity and resource profile (size of partition, access patterns, etc).</li>
   <li>Centralized config management and self discovery. Eliminates the need to modify config on each node.</li>
   <li>Fault tolerance and optimized rebalancing during cluster expansion.</li>
   <li>Manages entire operational lifecycle of a node. Addition, start, stop, enable/disable without downtime.</li>
@@ -215,20 +215,20 @@ under the License. --><p>Helix aims to p
   <li>PARTICIPANT: The nodes that actually host the distributed resources.</li>
   <li>SPECTATOR: The nodes that simply observe the PARTICIPANT State and route the request accordingly. Routers, for example, need to know the Instance on which a partition is hosted and its state in order to route the request to the appropriate end point.</li>
   <li>CONTROLLER: The controller observes and controls the PARTICIPANT nodes. It is responsible for coordinating all transitions in the cluster and ensuring that state constraints are satisfied and cluster stability is maintained.</li>
-</ol><p>These are simply logical components and can be deployed as per the system requirements. For example.</p>
+</ol><p>These are simply logical components and can be deployed as per the system requirements. For example:</p>
 <ol style="list-style-type: decimal">
-  <li>Controller can be deployed as a separate service.</li>
-  <li>Controller can be deployed along with Participant but only one Controller will be active at any given time.</li>
-</ol><p>Both have pros and cons, which will be discussed later and one can chose the mode of deployment as per system needs.</p></div><div class="section"><h2>Cluster state/metadata store<a name="Cluster_statemetadata_store"></a></h2><p>We need a distributed store to maintain the state of the cluster and a notification system to notify if there is any change in the cluster state. Helix uses Zookeeper to achieve this functionality.</p><p>Zookeeper provides</p>
+  <li>Controller can be deployed as a separate service</li>
+  <li>Controller can be deployed along with a Participant but only one Controller will be active at any given time.</li>
+</ol><p>Both have pros and cons, which will be discussed later and one can chose the mode of deployment as per system needs.</p></div><div class="section"><h2>Cluster state/metadata store<a name="Cluster_statemetadata_store"></a></h2><p>We need a distributed store to maintain the state of the cluster and a notification system to notify if there is any change in the cluster state. Helix uses Zookeeper to achieve this functionality.</p><p>Zookeeper provides:</p>
 <ul>
   <li>A way to represent PERSISTENT state which basically remains until its deleted.</li>
   <li>A way to represent TRANSIENT/EPHEMERAL state which vanishes when the process that created the STATE dies.</li>
   <li>Notification mechanism when there is a change in PERSISTENT/EPHEMERAL STATE</li>
-</ul><p>The name space provided by ZooKeeper is much like that of a standard file system. A name is a sequence of path elements separated by a slash (/). Every node[ZNODE] in ZooKeepers name space is identified by a path.</p><p>More info on Zookeeper can be found here <a class="externalLink" href="http://zookeeper.apache.org">http://zookeeper.apache.org</a></p></div><div class="section"><h2>Statemachine and constraints<a name="Statemachine_and_constraints"></a></h2><p>Even though the concept of Resource, Partition, Replicas is common to most distributed systems, one thing that differentiates one distributed system from another is the way each partition is assigned a state and the constraints on each state.</p><p>For example, </p>
+</ul><p>The namespace provided by ZooKeeper is much like that of a standard file system. A name is a sequence of path elements separated by a slash (/). Every node[ZNODE] in ZooKeeper's namespace is identified by a path.</p><p>More info on Zookeeper can be found here <a class="externalLink" href="http://zookeeper.apache.org">http://zookeeper.apache.org</a></p></div><div class="section"><h2>Statemachine and constraints<a name="Statemachine_and_constraints"></a></h2><p>Even though the concept of Resource, Partition, Replicas is common to most distributed systems, one thing that differentiates one distributed system from another is the way each partition is assigned a state and the constraints on each state.</p><p>For example:</p>
 <ol style="list-style-type: decimal">
-  <li>If a system is serving READ ONLY data then all partitions replicas are equal and they can either be ONLINE or OFFLINE.</li>
-  <li>If a system takes BOTH READ and WRITES but ensure that WRITES go through only one partition then the states will be MASTER,SLAVE and OFFLINE. Writes go through the MASTER and is replicated to the SLAVES. Optionally, READS can go through SLAVES</li>
-</ol><p>Apart from defining State for each partition, the transition path to each STATE can be application specific. For example, in order to become master it might be a requirement to first become a SLAVE. This ensures that if the SLAVE does not have the data as part of OFFLINE-SLAVE transition it can bootstrap data from other nodes in the system.</p><p>Helix provides a way to configure an application specific state machine along with constraints on each state. Along with constraints on State, Helix also provides a way to specify constraints on transitions.(More on this later)</p>
+  <li>If a system is serving READ ONLY data then all partition's replicas are equal and they can either be ONLINE or OFFLINE.</li>
+  <li>If a system takes BOTH READ and WRITES but ensure that WRITES go through only one partition then the states will be MASTER, SLAVE and OFFLINE. Writes go through the MASTER and is replicated to the SLAVES. Optionally, READS can go through SLAVES.</li>
+</ol><p>Apart from defining STATE for each partition, the transition path to each STATE can be application specific. For example, in order to become MASTER it might be a requirement to first become a SLAVE. This ensures that if the SLAVE does not have the data as part of OFFLINE-SLAVE transition it can bootstrap data from other nodes in the system.</p><p>Helix provides a way to configure an application specific state machine along with constraints on each state. Along with constraints on STATE, Helix also provides a way to specify constraints on transitions. (More on this later.)</p>
 <div class="source"><pre class="prettyprint">          OFFLINE  | SLAVE  |  MASTER  
          _____________________________
         |          |        |         |
@@ -243,20 +243,20 @@ MASTER  | SLAVE    | SLAVE  |   N/A   |
 
 </pre></div><p><img src="images/statemachine.png" alt="Helix Design" /></p></div><div class="section"><h2>Concepts<a name="Concepts"></a></h2><p>The following terminologies are used in Helix to model a state machine.</p>
 <ul>
-  <li>IDEALSTATE:The state in which we need the cluster to be in if all nodes are up and running. In other words, all state constraints are satisfied.</li>
-  <li>CURRENSTATE:Represents the current state of each node in the cluster</li>
-  <li>EXTERNALVIEW:Represents the combined view of CURRENTSTATE of all nodes.</li>
-</ul><p>Goal of Helix is always to make the CURRENTSTATE of the system same as the IDEALSTATE. Some scenarios where this may not be true are</p>
+  <li>IDEALSTATE: The state in which we need the cluster to be in if all nodes are up and running. In other words, all state constraints are satisfied.</li>
+  <li>CURRENTSTATE: Represents the current state of each node in the cluster</li>
+  <li>EXTERNALVIEW: Represents the combined view of CURRENTSTATE of all nodes.</li>
+</ul><p>The goal of Helix is always to make the CURRENTSTATE of the system same as the IDEALSTATE. Some scenarios where this may not be true are:</p>
 <ul>
   <li>When all nodes are down</li>
   <li>When one or more nodes fail</li>
-  <li>New nodes are added and the partitions need to be reassigned.</li>
-</ul><div class="section"><h3>IDEALSTATE<a name="IDEALSTATE"></a></h3><p>Helix lets the application define the IdealState on a resource basis which basically consists of</p>
+  <li>New nodes are added and the partitions need to be reassigned</li>
+</ul><div class="section"><h3>IDEALSTATE<a name="IDEALSTATE"></a></h3><p>Helix lets the application define the IdealState on a resource basis which basically consists of:</p>
 <ul>
-  <li>List of partitions. Example 64</li>
-  <li>Number of replicas for each partition. Example 3</li>
+  <li>List of partitions. Example: 64</li>
+  <li>Number of replicas for each partition. Example: 3</li>
   <li>Node and State for each replica.</li>
-</ul><p>Example</p>
+</ul><p>Example:</p>
 <ul>
   <li>Partition-1, replica-1, Master, Node-1</li>
   <li>Partition-1, replica-2, Slave, Node-2</li>
@@ -264,7 +264,7 @@ MASTER  | SLAVE    | SLAVE  |   N/A   |
   <li>..</li>
   <li>..</li>
   <li>Partition-p, replica-3, Slave, Node-n</li>
-</ul><p>Helix comes with various algorithms to automatically assign the partitions to nodes. The default algorithm minimizes the number of shuffles that happen when new nodes are added to the system</p></div><div class="section"><h3>CURRENTSTATE<a name="CURRENTSTATE"></a></h3><p>Every Instance in the cluster hosts one or more partitions of a resource. Each of the partitions has a State associated with it.</p><p>Example Node-1</p>
+</ul><p>Helix comes with various algorithms to automatically assign the partitions to nodes. The default algorithm minimizes the number of shuffles that happen when new nodes are added to the system</p></div><div class="section"><h3>CURRENTSTATE<a name="CURRENTSTATE"></a></h3><p>Every instance in the cluster hosts one or more partitions of a resource. Each of the partitions has a State associated with it.</p><p>Example Node-1</p>
 <ul>
   <li>Partition-1, Master</li>
   <li>Partition-2, Slave</li>
@@ -279,17 +279,17 @@ MASTER  | SLAVE    | SLAVE  |   N/A   |
   <li>..</li>
   <li>..</li>
   <li>Partition-p, replica-3, Slave, Node-n</li>
-</ul></div></div><div class="section"><h2>Process Workflow<a name="Process_Workflow"></a></h2><p>Mode of operation in a cluster</p><p>A node process can be one of the following</p>
+</ul></div></div><div class="section"><h2>Process Workflow<a name="Process_Workflow"></a></h2><p>Mode of operation in a cluster</p><p>A node process can be one of the following:</p>
 <ul>
-  <li>PARTICIPANT: The process registers itself in the cluster and acts on the messages received in its queue and updates the current state. Example:Storage Node</li>
-  <li>SPECTATOR: The process is simply interested in the changes in the externalView. Router is a spectator of Storage cluster.</li>
-  <li>CONTROLLER:This process actively controls the cluster by reacting to changes in Cluster State and sending messages to PARTICIPANTS</li>
+  <li>PARTICIPANT: The process registers itself in the cluster and acts on the messages received in its queue and updates the current state. Example: Storage Node</li>
+  <li>SPECTATOR: The process is simply interested in the changes in the Externalview. The Router is a spectator of the Storage cluster.</li>
+  <li>CONTROLLER: This process actively controls the cluster by reacting to changes in Cluster State and sending messages to PARTICIPANTS.</li>
 </ul><div class="section"><h3>Participant Node Process<a name="Participant_Node_Process"></a></h3>
 <ul>
   <li>When Node starts up, it registers itself under LIVEINSTANCES</li>
   <li>After registering, it waits for new Messages in the message queue</li>
-  <li>When it receives a message, it will perform the required task as indicated in the message.</li>
-  <li>After the task is completed, depending on the task outcome it updates the CURRENTSTATE.</li>
+  <li>When it receives a message, it will perform the required task as indicated in the message</li>
+  <li>After the task is completed, depending on the task outcome it updates the CURRENTSTATE</li>
 </ul></div><div class="section"><h3>Controller Process<a name="Controller_Process"></a></h3>
 <ul>
   <li>Watches IDEALSTATE</li>
@@ -297,23 +297,48 @@ MASTER  | SLAVE    | SLAVE  |   N/A   |
   <li>Triggers appropriate state transition by sending message to PARTICIPANT</li>
 </ul></div><div class="section"><h3>Spectator Process<a name="Spectator_Process"></a></h3>
 <ul>
-  <li>When the process starts it asks cluster manager agent to be notified of changes in ExternalView</li>
-  <li>When ever it receives a notification it reads the externalView and performs required duties. For Router, it updates its routing table.</li>
-</ul><p>h4. Interaction between controller, participant and spectator</p><p>The following picture shows how controllers, participants and spectators interact with each other.</p><p><img src="images/helix-architecture.png" alt="Helix Architecture" /></p></div></div><div class="section"><h2>Core algorithm<a name="Core_algorithm"></a></h2>
-<ul>
-  <li>Controller gets the Ideal State and the Current State of active storage nodes from ZK</li>
-  <li>Compute the delta between Ideal State and Current State for each partition across all participant nodes</li>
-  <li>For each partition compute tasks based on State Machine Table. Its possible to configure priority on the state Transition. For example in case of Master Slave:
+  <li>When the process starts, it asks cluster manager agent to be notified of changes in ExternalView</li>
+  <li>Whenever it receives a notification, it reads the Externalview and performs required duties. For the Router, it updates its routing table.</li>
+</ul><div class="section"><h4>Interaction between controller, participant and spectator<a name="Interaction_between_controller_participant_and_spectator"></a></h4><p>The following picture shows how controllers, participants and spectators interact with each other.</p><p><img src="images/helix-architecture.png" alt="Helix Architecture" /></p></div></div></div><div class="section"><h2>Core algorithm<a name="Core_algorithm"></a></h2>
+<ul>
+  <li>Controller gets the IdealState and the CurrentState of active storage nodes from Zookeeper</li>
+  <li>Compute the delta between IdealState and CurrentState for each partition across all participant nodes</li>
+  <li>For each partition compute tasks based on the State Machine Table. It's possible to configure priority on the state Transition. For example, in case of Master-Slave:
   <ul>
-    <li>Attempt Mastership transfer if possible without violating constraint.</li>
+    <li>Attempt mastership transfer if possible without violating constraint.</li>
     <li>Partition Addition</li>
     <li>Drop Partition</li>
   </ul></li>
-  <li>Add the tasks in parallel if possible to respective queue for each storage node keeping in mind</li>
-  <li>The tasks added are mutually independent.</li>
-  <li>If a task is dependent on another task being completed do not add that task.</li>
-  <li>After any task is completed by Participant, Controllers gets notified of the change and State Transition algorithm is re-run until the current state is same as Ideal State.</li>
-</ul></div><div class="section"><h2>Helix znode layout<a name="Helix_znode_layout"></a></h2><p>Helix organizes znodes under clusterName in multiple levels. The top level (under clusterName) znodes are all Helix defined and in upper case * PROPERTYSTORE: application property store * STATEMODELDEFES: state model definitions * INSTANCES: instance runtime information including current state and messages * CONFIGS: configurations * IDEALSTATES: ideal states * EXTERNALVIEW: external views * LIVEINSTANCES: live instances * CONTROLLER: cluster controller runtime information</p><p>Under INSTANCES, there are runtime znodes for each instance. An instance organizes znodes as follows: * CURRENTSTATES  * sessionId  * resourceName * ERRORS * STATUSUPDATES * MESSAGES * HEALTHREPORT</p><p>Under CONFIGS, there are different scopes of configurations: * RESOURCE: contains resource scope configurations * CLUSTER: contains cluster scope configurations * PARTICIPANT: contains participant scope con
 figurations</p><p>The following image shows an example of Helix znodes layout for a cluster named test-cluster:</p><p><img src="images/helix-znode-layout.png" alt="Helix znode layout" /></p></div>
+  <li>Add the tasks in parallel if possible to the respective queue for each storage node (if the tasks added are mutually independent)</li>
+  <li>If a task is dependent on another task being completed, do not add that task</li>
+  <li>After any task is completed by a Participant, Controllers gets notified of the change and the State Transition algorithm is re-run until the CurrentState is same as IdealState.</li>
+</ul></div><div class="section"><h2>Helix znode layout<a name="Helix_znode_layout"></a></h2><p>Helix organizes znodes under clusterName in multiple levels. </p><p>The top level (under clusterName) znodes are all Helix defined and in upper case:</p>
+<ul>
+  <li>PROPERTYSTORE: application property store</li>
+  <li>STATEMODELDEFES: state model definitions</li>
+  <li>INSTANCES: instance runtime information including current state and messages</li>
+  <li>CONFIGS: configurations</li>
+  <li>IDEALSTATES: ideal states</li>
+  <li>EXTERNALVIEW: external views</li>
+  <li>LIVEINSTANCES: live instances</li>
+  <li>CONTROLLER: cluster controller runtime information</li>
+</ul><p>Under INSTANCES, there are runtime znodes for each instance. An instance organizes znodes as follows:</p>
+<ul>
+  <li>CURRENTSTATES
+  <ul>
+    <li>sessionId</li>
+    <li>resourceName</li>
+  </ul></li>
+  <li>ERRORS</li>
+  <li>STATUSUPDATES</li>
+  <li>MESSAGES</li>
+  <li>HEALTHREPORT</li>
+</ul><p>Under CONFIGS, there are different scopes of configurations:</p>
+<ul>
+  <li>RESOURCE: contains resource scope configurations</li>
+  <li>CLUSTER: contains cluster scope configurations</li>
+  <li>PARTICIPANT: contains participant scope configurations</li>
+</ul><p>The following image shows an example of Helix znodes layout for a cluster named test-cluster:</p><p><img src="images/helix-znode-layout.png" alt="Helix znode layout" /></p></div>
                   </div>
           </div>
 

Modified: incubator/helix/site-content/Concepts.html
URL: http://svn.apache.org/viewvc/incubator/helix/site-content/Concepts.html?rev=1486209&r1=1486208&r2=1486209&view=diff
==============================================================================
--- incubator/helix/site-content/Concepts.html (original)
+++ incubator/helix/site-content/Concepts.html Fri May 24 20:30:39 2013
@@ -1,13 +1,13 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia at May 22, 2013
+ | Generated by Apache Maven Doxia at May 24, 2013
  | Rendered using Apache Maven Fluido Skin 1.3.0
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <meta name="Date-Revision-yyyymmdd" content="20130522" />
+    <meta name="Date-Revision-yyyymmdd" content="20130524" />
     <meta http-equiv="Content-Language" content="en" />
     <title>Apache Helix - </title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -168,7 +168,7 @@
                 
                 
             
-                  <li id="publishDate" class="pull-right">Last Published: 2013-05-22</li> 
+                  <li id="publishDate" class="pull-right">Last Published: 2013-05-24</li> 
             
                             </ul>
       </div>
@@ -193,16 +193,16 @@ software distributed under the License i
 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 KIND, either express or implied.  See the License for the
 specific language governing permissions and limitations
-under the License. --><p>Helix is based on the simple fact that a given task has the following attributes associated with it </p>
+under the License. --><p>Helix is based on the idea that a given task has the following attributes associated with it:</p>
 <ul>
-  <li>Location of the task, for example it runs on Node N1</li>
-  <li>State, for examples its running, stopped etc.</li>
-</ul><p>A task is referred to as a resource. </p><div class="section"><div class="section"><h3>IDEALSTATE<a name="IDEALSTATE"></a></h3><p>Ideal state simply allows one to map tasks to location and state. A standard way of expressing this in Helix is</p>
+  <li><i>Location of the task</i>. For example it runs on Node N1</li>
+  <li><i>State</i>. For example, it is running, stopped etc.</li>
+</ul><p>In Helix terminology, a task is referred to as a <i>resource</i>.</p><div class="section"><div class="section"><h3>IdealState<a name="IdealState"></a></h3><p>IdealState simply allows one to map tasks to location and state. A standard way of expressing this in Helix:</p>
 <div class="source"><pre class="prettyprint">  &quot;TASK_NAME&quot; : {
     &quot;LOCATION&quot; : &quot;STATE&quot;
   }
 
-</pre></div><p>Consider a simple case where you want to launch a task myTask on node N1. The idealstate for this can be expressed as follows</p>
+</pre></div><p>Consider a simple case where you want to launch a task 'myTask' on node 'N1'. The IdealState for this can be expressed as follows:</p>
 <div class="source"><pre class="prettyprint">{
   &quot;id&quot; : &quot;MyTask&quot;,
   &quot;mapFields&quot; : {
@@ -211,7 +211,7 @@ under the License. --><p>Helix is based 
     }
   }
 }
-</pre></div><div class="section"><h4>PARTITION<a name="PARTITION"></a></h4><p>If this task get too big to fit on one box, you might want to divide it into subTasks. Each subTask is referred to as partition in Helix. Lets say you want to divide the task into 3 subTasks/partitions, the idealstate can be changed as shown below. </p><p>myTask_0, myTask_1, myTask_2 are logical names representing the partitions of myTask. Each tasks runs on N1,N2 and N3 respectively.</p>
+</pre></div></div><div class="section"><h3>Partition<a name="Partition"></a></h3><p>If this task get too big to fit on one box, you might want to divide it into subTasks. Each subTask is referred to as a <i>partition</i> in Helix. Let's say you want to divide the task into 3 subTasks/partitions, the IdealState can be changed as shown below. </p><p>'myTask_0', 'myTask_1', 'myTask_2' are logical names representing the partitions of myTask. Each tasks runs on N1, N2 and N3 respectively.</p>
 <div class="source"><pre class="prettyprint">{
   &quot;id&quot; : &quot;myTask&quot;,
   &quot;simpleFields&quot; : {
@@ -229,7 +229,7 @@ under the License. --><p>Helix is based 
     }
   }
 }
-</pre></div></div><div class="section"><h4>REPLICA<a name="REPLICA"></a></h4><p>Partitioning allows one to split the data/task into multiple subparts. But lets say the request rate each partition increases. The common solution is to have multiple copies for each partition. Helix refers to the copy of a partition as replica. Adding replica also increases the availability of the system during failures. One can see this methodology employed often in Search systems. The index is divided into shard and each shard has multiple copies.</p><p>Lets say you want to add one additional replica for each task. The idealstate can simply be changed as shown below. </p><p>For increasing the availability of the system, its better to place replica of given partition on different nodes.</p>
+</pre></div></div><div class="section"><h3>Replica<a name="Replica"></a></h3><p>Partitioning allows one to split the data/task into multiple subparts. But let's say the request rate each partition increases. The common solution is to have multiple copies for each partition. Helix refers to the copy of a partition as a <i>replica</i>. Adding a replica also increases the availability of the system during failures. One can see this methodology employed often in Search systems. The index is divided into shards, and each shard has multiple copies.</p><p>Let's say you want to add one additional replica for each task. The IdealState can simply be changed as shown below. </p><p>For increasing the availability of the system, it's better to place the replica of a given partition on different nodes.</p>
 <div class="source"><pre class="prettyprint">{
   &quot;id&quot; : &quot;myIndex&quot;,
   &quot;simpleFields&quot; : {
@@ -251,7 +251,7 @@ under the License. --><p>Helix is based 
     }
   }
 }
-</pre></div></div><div class="section"><h4>STATE<a name="STATE"></a></h4><p>Now lets take a slightly complicated scenario where a task represents a database. Unlike an index which is in general read only, database supports both reads and write. Keeping the data consistent among the replica is crucial in distributed data stores. One commonly applied technique is to assign one replica as MASTER and remaining as SLAVE. All writes go to MASTER and are then replicated to SLAVE.</p><p>Helix allows one to assign different states to each replica. Lets say you have two mysql instances N1 and N2 where one will serve as MASTER and another as SLAVE. The ideal state can be changed to</p>
+</pre></div></div><div class="section"><h3>State<a name="State"></a></h3><p>Now let's take a slightly complicated scenario where a task represents a database. Unlike an index which is in general read-only, a database supports both reads and writes. Keeping the data consistent among the replicas is crucial in distributed data stores. One commonly applied technique is to assign one replica as MASTER and remaining replicas as SLAVE. All writes go to the MASTER and are then replicated to the SLAVE replicas.</p><p>Helix allows one to assign different states to each replica. Let's say you have two MySQL instances N1 and N2, where one will serve as MASTER and another as SLAVE. The IdealState can be changed to:</p>
 <div class="source"><pre class="prettyprint">{
   &quot;id&quot; : &quot;myDB&quot;,
   &quot;simpleFields&quot; : {
@@ -266,10 +266,10 @@ under the License. --><p>Helix is based 
   }
 }
 
-</pre></div></div></div><div class="section"><h3>STATE MACHINE and TRANSITIONS<a name="STATE_MACHINE_and_TRANSITIONS"></a></h3><p>Idealstate allows one to exactly specify the desired state of the cluster. Given an idealstate, Helix takes up the responsibility of ensuring that cluster reaches idealstate. Helix CONTROLLER reads the idealstate and then commands the PARTICIPANT to take appropriate actions to move from one state to another until it matches Idealstate. These actions are referred to as transitions in Helix.</p><p>Next logical question is, how does the CONTROLLER compute the transitions required to get to idealstate. This is where finite state machine concept comes in. Helix allows applications to plug in FSM. A state machine consists of the following</p>
+</pre></div></div><div class="section"><h3>State Machine and Transitions<a name="State_Machine_and_Transitions"></a></h3><p>IdealState allows one to exactly specify the desired state of the cluster. Given an IdealState, Helix takes up the responsibility of ensuring that the cluster reaches the IdealState. The Helix <i>controller</i> reads the IdealState and then commands the Participant to take appropriate actions to move from one state to another until it matches the IdealState. These actions are referred to as <i>transitions</i> in Helix.</p><p>The next logical question is: how does the <i>controller</i> compute the transitions required to get to IdealState? This is where the finite state machine concept comes in. Helix allows applications to plug in a finite state machine. A state machine consists of the following:</p>
 <ul>
-  <li>STATE : Describes the role of a replica</li>
-  <li>TRANSITION: An action that allows a replica to move from one STATE to another, thus changing its role.</li>
+  <li>State: Describes the role of a replica</li>
+  <li>Transition: An action that allows a replica to move from one State to another, thus changing its role.</li>
 </ul><p>Here is an example of MASTERSLAVE state machine,</p>
 <div class="source"><pre class="prettyprint">          OFFLINE  | SLAVE  |  MASTER  
          _____________________________
@@ -283,7 +283,7 @@ SLAVE   |  OFFLINE |   N/A  | MASTER  |
 MASTER  | SLAVE    | SLAVE  |   N/A   |
         |__________|________|_________|
 
-</pre></div><p>Helix allows each resource to be associated with one state machine. This means you can have one resource as a index and another as database in the same cluster. One can associate each resource with a state machine as follows</p>
+</pre></div><p>Helix allows each resource to be associated with one state machine. This means you can have one resource as an index and another as a database in the same cluster. One can associate each resource with a state machine as follows:</p>
 <div class="source"><pre class="prettyprint">{
   &quot;id&quot; : &quot;myDB&quot;,
   &quot;simpleFields&quot; : {
@@ -299,10 +299,10 @@ MASTER  | SLAVE    | SLAVE  |   N/A   |
   }
 }
 
-</pre></div></div><div class="section"><h3>CURRENT STATE<a name="CURRENT_STATE"></a></h3><p>Currentstate of a resource simply represents its actual state at a PARTICIPANT. In the below example, </p>
+</pre></div></div><div class="section"><h3>Current State<a name="Current_State"></a></h3><p>CurrentState of a resource simply represents its actual state at a PARTICIPANT. In the below example:</p>
 <ul>
-  <li>INSTANCE_NAME : Unique name representing the process.</li>
-  <li>SESSION_ID: Id that is automatically assigned every time a process joins the cluster.</li>
+  <li>INSTANCE_NAME: Unique name representing the process</li>
+  <li>SESSION_ID: ID that is automatically assigned every time a process joins the cluster</li>
 </ul>
 <div class="source"><pre class="prettyprint">{
   &quot;id&quot;:&quot;MyResource&quot;
@@ -323,7 +323,7 @@ MASTER  | SLAVE    | SLAVE  |   N/A   |
     }
   }
 }
-</pre></div><p>Each node in the cluster has its own Current state.</p></div><div class="section"><h3>EXTERNAL VIEW<a name="EXTERNAL_VIEW"></a></h3><p>In order to communicate with the PARTICIPANTs, external clients need to know the current state of each of the PARTICIPANT. The external clients are referred to as SPECTATORS. In order to make the life of SPECTATOR simple, Helix provides EXTERNALVIEW that is an aggregated view of the current state across all nodes. The EXTERNALVIEW has similar format as IDEALSTATE.</p>
+</pre></div><p>Each node in the cluster has its own CurrentState.</p></div><div class="section"><h3>External View<a name="External_View"></a></h3><p>In order to communicate with the PARTICIPANTs, external clients need to know the current state of each of the PARTICIPANTs. The external clients are referred to as SPECTATORS. In order to make the life of SPECTATOR simple, Helix provides an EXTERNALVIEW that is an aggregated view of the current state across all nodes. The EXTERNALVIEW has a similar format as IDEALSTATE.</p>
 <div class="source"><pre class="prettyprint">{
   &quot;id&quot;:&quot;MyResource&quot;,
   &quot;mapFields&quot;:{
@@ -344,17 +344,17 @@ MASTER  | SLAVE    | SLAVE  |   N/A   |
     }
   }
 }
-</pre></div></div><div class="section"><h3>REBALANCER<a name="REBALANCER"></a></h3><p>The core component of Helix is the CONTROLLER which runs the REBALANCER algorithm on every cluster event. Cluster event can be one of the following</p>
+</pre></div></div><div class="section"><h3>Rebalancer<a name="Rebalancer"></a></h3><p>The core component of Helix is the CONTROLLER which runs the REBALANCER algorithm on every cluster event. Cluster events can be one of the following:</p>
 <ul>
   <li>Nodes start/stop and soft/hard failures</li>
   <li>New nodes are added/removed</li>
   <li>Ideal state changes</li>
-</ul><p>There are few more like config changes etc but the key point to take away is there are many ways to trigger the rebalancer.</p><p>When a rebalancer is run it simply does the following</p>
+</ul><p>There are few more such as config changes, etc. The key takeaway: there are many ways to trigger the rebalancer.</p><p>When a rebalancer is run it simply does the following:</p>
 <ul>
-  <li>Compares the idealstate and current state</li>
-  <li>Computes the transitions required to reach the idealstate.</li>
-  <li>Issues the transitions to PARTICIPANT</li>
-</ul><p>The above steps happen for every change in the system. Once current state matches the idealstate the system is considered stable which implies IDEALSTATE = CURRENTSTATE = EXTERNALVIEW</p></div><div class="section"><h3>DYNAMIC IDEALSTATE<a name="DYNAMIC_IDEALSTATE"></a></h3><p>One of the things that makes Helix powerful is that idealstate can be changed dynamically. This means one can listen to cluster events like node failures and dynamically change the ideal state. Helix will then take care of triggering the respective transitions in the system.</p><p>Helix comes with few algorithms to automatically compute the idealstate based on the constraints. For e.g. if you have a resource 3 partitions and 2 replicas, Helix can automatically compute the idealstate based on the nodes that are currently active. See features page to find out more about various execution modes of Helix like AUTO_REBALANCE, AUTO and CUSTOM. </p></div></div>
+  <li>Compares the IdealState and current state</li>
+  <li>Computes the transitions required to reach the IdealState</li>
+  <li>Issues the transitions to each PARTICIPANT</li>
+</ul><p>The above steps happen for every change in the system. Once the current state matches the IdealState, the system is considered stable which implies 'IDEALSTATE = CURRENTSTATE = EXTERNALVIEW'</p></div><div class="section"><h3>Dynamic IdealState<a name="Dynamic_IdealState"></a></h3><p>One of the things that makes Helix powerful is that IdealState can be changed dynamically. This means one can listen to cluster events like node failures and dynamically change the ideal state. Helix will then take care of triggering the respective transitions in the system.</p><p>Helix comes with few algorithms to automatically compute the IdealState based on the constraints. For example, if you have a resource of 3 partitions and 2 replicas, Helix can automatically compute the IdealState based on the nodes that are currently active. See the <a href="./tutorial_rebalance.html">tutorial</a> to find out more about various execution modes of Helix like AUTO_REBALANCE, AUTO and CUSTOM. </p><
 /div></div>
                   </div>
           </div>
 

Modified: incubator/helix/site-content/Features.html
URL: http://svn.apache.org/viewvc/incubator/helix/site-content/Features.html?rev=1486209&r1=1486208&r2=1486209&view=diff
==============================================================================
--- incubator/helix/site-content/Features.html (original)
+++ incubator/helix/site-content/Features.html Fri May 24 20:30:39 2013
@@ -1,13 +1,13 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia at May 22, 2013
+ | Generated by Apache Maven Doxia at May 24, 2013
  | Rendered using Apache Maven Fluido Skin 1.3.0
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <meta name="Date-Revision-yyyymmdd" content="20130522" />
+    <meta name="Date-Revision-yyyymmdd" content="20130524" />
     <meta http-equiv="Content-Language" content="en" />
     <title>Apache Helix - </title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -168,7 +168,7 @@
                 
                 
             
-                  <li id="publishDate" class="pull-right">Last Published: 2013-05-22</li> 
+                  <li id="publishDate" class="pull-right">Last Published: 2013-05-24</li> 
             
                             </ul>
       </div>

Modified: incubator/helix/site-content/Quickstart.html
URL: http://svn.apache.org/viewvc/incubator/helix/site-content/Quickstart.html?rev=1486209&r1=1486208&r2=1486209&view=diff
==============================================================================
--- incubator/helix/site-content/Quickstart.html (original)
+++ incubator/helix/site-content/Quickstart.html Fri May 24 20:30:39 2013
@@ -1,13 +1,13 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia at May 22, 2013
+ | Generated by Apache Maven Doxia at May 24, 2013
  | Rendered using Apache Maven Fluido Skin 1.3.0
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <meta name="Date-Revision-yyyymmdd" content="20130522" />
+    <meta name="Date-Revision-yyyymmdd" content="20130524" />
     <meta http-equiv="Content-Language" content="en" />
     <title>Apache Helix - </title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -168,7 +168,7 @@
                 
                 
             
-                  <li id="publishDate" class="pull-right">Last Published: 2013-05-22</li> 
+                  <li id="publishDate" class="pull-right">Last Published: 2013-05-24</li> 
             
                             </ul>
       </div>
@@ -341,6 +341,36 @@ ExternalView for myDB:
 {
   &quot;id&quot; : &quot;myDB&quot;,
   &quot;mapFields&quot; : {
+    &quot;myDB_0&quot; : {
+      &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12914&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12915&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_1&quot; : {
+      &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12914&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12915&quot; : &quot;MASTER&quot;
+    },
+    &quot;myDB_2&quot; : {
+      &quot;localhost_12913&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12914&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12915&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_3&quot; : {
+      &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12914&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12915&quot; : &quot;MASTER&quot;
+    },
+    &quot;myDB_4&quot; : {
+      &quot;localhost_12913&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12914&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12915&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_5&quot; : {
+      &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12914&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12915&quot; : &quot;SLAVE&quot;
+    }
   },
   &quot;listFields&quot; : {
   },
@@ -355,6 +385,11 @@ ExternalView for myDB:
 <div class="source"><pre class="prettyprint">./helix-admin.sh --zkSvr localhost:2199  --addNode MYCLUSTER localhost:12916
 ./helix-admin.sh --zkSvr localhost:2199  --addNode MYCLUSTER localhost:12917
 ./helix-admin.sh --zkSvr localhost:2199  --addNode MYCLUSTER localhost:12918
+</pre></div><p>And start up these instances:</p>
+<div class="source"><pre class="prettyprint"># start up each instance.  These are mock implementations that are actively managed by Helix
+./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12916 --stateModelType MasterSlave 2&gt;&amp;1 &gt; /tmp/participant_12916.log
+./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12917 --stateModelType MasterSlave 2&gt;&amp;1 &gt; /tmp/participant_12917.log
+./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12918 --stateModelType MasterSlave 2&gt;&amp;1 &gt; /tmp/participant_12918.log
 </pre></div><p>And now, let Helix do the work for you. To shift the work, simply rebalance. After the rebalance, each node will have one master and two slaves.</p>
 <div class="source"><pre class="prettyprint">./helix-admin.sh --zkSvr localhost:2199 --rebalance MYCLUSTER myDB 3
 </pre></div></div><div class="section"><h4>View the cluster<a name="View_the_cluster"></a></h4><p>OK, let's see how it looks:</p>
@@ -416,6 +451,36 @@ ExternalView for myDB:
 {
   &quot;id&quot; : &quot;myDB&quot;,
   &quot;mapFields&quot; : {
+    &quot;myDB_0&quot; : {
+      &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12914&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12917&quot; : &quot;MASTER&quot;
+    },
+    &quot;myDB_1&quot; : {
+      &quot;localhost_12916&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12917&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12918&quot; : &quot;MASTER&quot;
+    },
+    &quot;myDB_2&quot; : {
+      &quot;localhost_12913&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12917&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12918&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_3&quot; : {
+      &quot;localhost_12915&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12917&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12918&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_4&quot; : {
+      &quot;localhost_12916&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12917&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12918&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_5&quot; : {
+      &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12914&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12915&quot; : &quot;SLAVE&quot;
+    }
   },
   &quot;listFields&quot; : {
   },
@@ -423,7 +488,7 @@ ExternalView for myDB:
     &quot;BUCKET_SIZE&quot; : &quot;0&quot;
   }
 }
-</pre></div><p>Mission accomplished. The partitions are nicely balanced.</p></div><div class="section"><h4>How about Failover?<a name="How_about_Failover"></a></h4><p>Building a fault tolerant system isn't trivial, but with Helix, it's easy. Helix detects a failed instance, and triggers mastership transfer automatically.</p><p>First, lets fail an instance:</p><p><i>KILL A NODE (need to find the pid via listInstanceInfo)</i></p><p>We lost localhost:12918, so myDB_1 lost its MASTER. Helix can fix that, it will transfer mastership to a healthy node that is currently a SLAVE, say localhost:12197. Helix balances the load as best as it can, given there are 6 partitions on 5 nodes. Let's see:</p>
+</pre></div><p>Mission accomplished. The partitions are nicely balanced.</p></div><div class="section"><h4>How about Failover?<a name="How_about_Failover"></a></h4><p>Building a fault tolerant system isn't trivial, but with Helix, it's easy. Helix detects a failed instance, and triggers mastership transfer automatically.</p><p>First, lets fail an instance. In this example, we'll kill localhost:12918 to simulate a failure.</p><p>We lost localhost:12918, so myDB_1 lost its MASTER. Helix can fix that, it will transfer mastership to a healthy node that is currently a SLAVE, say localhost:12197. Helix balances the load as best as it can, given there are 6 partitions on 5 nodes. Let's see:</p>
 <div class="source"><pre class="prettyprint">./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo MYCLUSTER myDB
 
 IdealState for myDB:
@@ -437,23 +502,23 @@ IdealState for myDB:
     },
     &quot;myDB_1&quot; : {
       &quot;localhost_12916&quot; : &quot;SLAVE&quot;,
-      &quot;localhost_12917&quot; : &quot;MASTER&quot;
-      &quot;localhost_12918&quot; : &quot;OFFLINE&quot;
+      &quot;localhost_12917&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12918&quot; : &quot;MASTER&quot;
     },
     &quot;myDB_2&quot; : {
       &quot;localhost_12913&quot; : &quot;MASTER&quot;,
       &quot;localhost_12917&quot; : &quot;SLAVE&quot;,
-      &quot;localhost_12918&quot; : &quot;OFFLINE&quot;
+      &quot;localhost_12918&quot; : &quot;SLAVE&quot;
     },
     &quot;myDB_3&quot; : {
       &quot;localhost_12915&quot; : &quot;MASTER&quot;,
       &quot;localhost_12917&quot; : &quot;SLAVE&quot;,
-      &quot;localhost_12918&quot; : &quot;OFFLINE&quot;
+      &quot;localhost_12918&quot; : &quot;SLAVE&quot;
     },
     &quot;myDB_4&quot; : {
       &quot;localhost_12916&quot; : &quot;MASTER&quot;,
       &quot;localhost_12917&quot; : &quot;SLAVE&quot;,
-      &quot;localhost_12918&quot; : &quot;OFFLINE&quot;
+      &quot;localhost_12918&quot; : &quot;SLAVE&quot;
     },
     &quot;myDB_5&quot; : {
       &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
@@ -463,9 +528,9 @@ IdealState for myDB:
   },
   &quot;listFields&quot; : {
     &quot;myDB_0&quot; : [ &quot;localhost_12917&quot;, &quot;localhost_12913&quot;, &quot;localhost_12914&quot; ],
-    &quot;myDB_1&quot; : [ &quot;localhost_12917&quot;, &quot;localhost_12916&quot;, &quot;localhost_12918&quot; ],
-    &quot;myDB_2&quot; : [ &quot;localhost_12913&quot;, &quot;localhost_12917&quot;, &quot;localhost_12918&quot; ],
-    &quot;myDB_3&quot; : [ &quot;localhost_12915&quot;, &quot;localhost_12917&quot;, &quot;localhost_12918&quot; ],
+    &quot;myDB_1&quot; : [ &quot;localhost_12918&quot;, &quot;localhost_12917&quot;, &quot;localhost_12916&quot; ],
+    &quot;myDB_2&quot; : [ &quot;localhost_12913&quot;, &quot;localhost_12918&quot;, &quot;localhost_12917&quot; ],
+    &quot;myDB_3&quot; : [ &quot;localhost_12915&quot;, &quot;localhost_12918&quot;, &quot;localhost_12917&quot; ],
     &quot;myDB_4&quot; : [ &quot;localhost_12916&quot;, &quot;localhost_12917&quot;, &quot;localhost_12918&quot; ],
     &quot;myDB_5&quot; : [ &quot;localhost_12914&quot;, &quot;localhost_12915&quot;, &quot;localhost_12913&quot; ]
   },
@@ -482,6 +547,32 @@ ExternalView for myDB:
 {
   &quot;id&quot; : &quot;myDB&quot;,
   &quot;mapFields&quot; : {
+    &quot;myDB_0&quot; : {
+      &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12914&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12917&quot; : &quot;MASTER&quot;
+    },
+    &quot;myDB_1&quot; : {
+      &quot;localhost_12916&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12917&quot; : &quot;MASTER&quot;
+    },
+    &quot;myDB_2&quot; : {
+      &quot;localhost_12913&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12917&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_3&quot; : {
+      &quot;localhost_12915&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12917&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_4&quot; : {
+      &quot;localhost_12916&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12917&quot; : &quot;SLAVE&quot;
+    },
+    &quot;myDB_5&quot; : {
+      &quot;localhost_12913&quot; : &quot;SLAVE&quot;,
+      &quot;localhost_12914&quot; : &quot;MASTER&quot;,
+      &quot;localhost_12915&quot; : &quot;SLAVE&quot;
+    }
   },
   &quot;listFields&quot; : {
   },

Modified: incubator/helix/site-content/Tutorial.html
URL: http://svn.apache.org/viewvc/incubator/helix/site-content/Tutorial.html?rev=1486209&r1=1486208&r2=1486209&view=diff
==============================================================================
--- incubator/helix/site-content/Tutorial.html (original)
+++ incubator/helix/site-content/Tutorial.html Fri May 24 20:30:39 2013
@@ -1,13 +1,13 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia at May 22, 2013
+ | Generated by Apache Maven Doxia at May 24, 2013
  | Rendered using Apache Maven Fluido Skin 1.3.0
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <meta name="Date-Revision-yyyymmdd" content="20130522" />
+    <meta name="Date-Revision-yyyymmdd" content="20130524" />
     <meta http-equiv="Content-Language" content="en" />
     <title>Apache Helix - </title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -168,7 +168,7 @@
                 
                 
             
-                  <li id="publishDate" class="pull-right">Last Published: 2013-05-22</li> 
+                  <li id="publishDate" class="pull-right">Last Published: 2013-05-24</li> 
             
                             </ul>
       </div>

Modified: incubator/helix/site-content/UseCases.html
URL: http://svn.apache.org/viewvc/incubator/helix/site-content/UseCases.html?rev=1486209&r1=1486208&r2=1486209&view=diff
==============================================================================
--- incubator/helix/site-content/UseCases.html (original)
+++ incubator/helix/site-content/UseCases.html Fri May 24 20:30:39 2013
@@ -1,13 +1,13 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia at May 22, 2013
+ | Generated by Apache Maven Doxia at May 24, 2013
  | Rendered using Apache Maven Fluido Skin 1.3.0
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <meta name="Date-Revision-yyyymmdd" content="20130522" />
+    <meta name="Date-Revision-yyyymmdd" content="20130524" />
     <meta http-equiv="Content-Language" content="en" />
     <title>Apache Helix - </title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -168,7 +168,7 @@
                 
                 
             
-                  <li id="publishDate" class="pull-right">Last Published: 2013-05-22</li> 
+                  <li id="publishDate" class="pull-right">Last Published: 2013-05-24</li> 
             
                             </ul>
       </div>

Modified: incubator/helix/site-content/apidocs/reference/org/apache/helix/agent/ProcessMonitorThread.html
URL: http://svn.apache.org/viewvc/incubator/helix/site-content/apidocs/reference/org/apache/helix/agent/ProcessMonitorThread.html?rev=1486209&r1=1486208&r2=1486209&view=diff
==============================================================================
--- incubator/helix/site-content/apidocs/reference/org/apache/helix/agent/ProcessMonitorThread.html (original)
+++ incubator/helix/site-content/apidocs/reference/org/apache/helix/agent/ProcessMonitorThread.html Fri May 24 20:30:39 2013
@@ -643,22 +643,6 @@ From class
             
             
             
-            <a href="http://download.oracle.com/javase/6/docs/api/index.html?java/lang/Object.html">Object</a></nobr>
-        </td>
-        <td class="jd-linkcol" width="100%"><nobr>
-        <span class="sympad">clone</span>()</nobr>
-        
-  </td></tr>
-
-
-	 
-    <tr class=" api apilevel-" >
-        <td class="jd-typecol"><nobr>
-            
-            
-            
-            
-            
             int</nobr>
         </td>
         <td class="jd-linkcol" width="100%"><nobr>
@@ -668,7 +652,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -684,7 +668,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -700,7 +684,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -716,7 +700,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -732,7 +716,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -748,7 +732,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -764,7 +748,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -780,7 +764,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -796,7 +780,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -812,7 +796,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -828,7 +812,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -844,7 +828,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -860,7 +844,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -876,7 +860,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -892,7 +876,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -908,7 +892,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -924,7 +908,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -940,7 +924,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -956,7 +940,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -972,7 +956,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -988,7 +972,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1004,7 +988,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             synchronized
@@ -1020,7 +1004,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             synchronized
@@ -1036,7 +1020,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1052,7 +1036,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1068,7 +1052,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1084,7 +1068,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1100,7 +1084,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1116,7 +1100,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1132,7 +1116,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1148,7 +1132,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1164,7 +1148,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1180,7 +1164,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1196,7 +1180,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             synchronized
@@ -1212,7 +1196,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             synchronized
@@ -1228,7 +1212,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1244,7 +1228,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1260,7 +1244,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1276,7 +1260,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             

Modified: incubator/helix/site-content/apidocs/reference/org/apache/helix/manager/zk/ZkCacheEventThread.html
URL: http://svn.apache.org/viewvc/incubator/helix/site-content/apidocs/reference/org/apache/helix/manager/zk/ZkCacheEventThread.html?rev=1486209&r1=1486208&r2=1486209&view=diff
==============================================================================
--- incubator/helix/site-content/apidocs/reference/org/apache/helix/manager/zk/ZkCacheEventThread.html (original)
+++ incubator/helix/site-content/apidocs/reference/org/apache/helix/manager/zk/ZkCacheEventThread.html Fri May 24 20:30:39 2013
@@ -652,22 +652,6 @@ From class
             
             
             
-            <a href="http://download.oracle.com/javase/6/docs/api/index.html?java/lang/Object.html">Object</a></nobr>
-        </td>
-        <td class="jd-linkcol" width="100%"><nobr>
-        <span class="sympad">clone</span>()</nobr>
-        
-  </td></tr>
-
-
-	 
-    <tr class=" api apilevel-" >
-        <td class="jd-typecol"><nobr>
-            
-            
-            
-            
-            
             int</nobr>
         </td>
         <td class="jd-linkcol" width="100%"><nobr>
@@ -677,7 +661,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -693,7 +677,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -709,7 +693,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -725,7 +709,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -741,7 +725,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -757,7 +741,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -773,7 +757,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -789,7 +773,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -805,7 +789,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -821,7 +805,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -837,7 +821,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -853,7 +837,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -869,7 +853,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -885,7 +869,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -901,7 +885,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -917,7 +901,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -933,7 +917,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -949,7 +933,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -965,7 +949,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -981,7 +965,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -997,7 +981,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1013,7 +997,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             synchronized
@@ -1029,7 +1013,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             synchronized
@@ -1045,7 +1029,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1061,7 +1045,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1077,7 +1061,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1093,7 +1077,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1109,7 +1093,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1125,7 +1109,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1141,7 +1125,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1157,7 +1141,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1173,7 +1157,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1189,7 +1173,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1205,7 +1189,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             synchronized
@@ -1221,7 +1205,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             synchronized
@@ -1237,7 +1221,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1253,7 +1237,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1269,7 +1253,7 @@ From class
 
 
 	 
-    <tr class=" api apilevel-" >
+    <tr class="alt-color api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             
@@ -1285,7 +1269,7 @@ From class
 
 
 	 
-    <tr class="alt-color api apilevel-" >
+    <tr class=" api apilevel-" >
         <td class="jd-typecol"><nobr>
             
             



Mime
View raw message