You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by jx...@apache.org on 2021/11/21 19:58:19 UTC
[helix] branch master updated: Remove 0.8 series doc
This is an automated email from the ASF dual-hosted git repository.
jxue pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/helix.git
The following commit(s) were added to refs/heads/master by this push:
new cb6dc84 Remove 0.8 series doc
cb6dc84 is described below
commit cb6dc849c01819af8d7d7c8e60fa8d53c6ccd4a6
Author: Junkai Xue <jx...@linkedin.com>
AuthorDate: Sun Nov 21 11:58:11 2021 -0800
Remove 0.8 series doc
---
website/0.8.0/pom.xml | 51 --
website/0.8.0/src/site/apt/privacy-policy.apt | 52 --
.../src/site/apt/releasenotes/release-0.8.0.apt | 249 ------
website/0.8.0/src/site/markdown/Building.md | 42 -
website/0.8.0/src/site/markdown/Features.md | 313 -------
website/0.8.0/src/site/markdown/Quickstart.md | 663 --------------
website/0.8.0/src/site/markdown/Tutorial.md | 207 -----
website/0.8.0/src/site/markdown/index.md | 51 --
.../src/site/markdown/recipes/lock_manager.md | 236 -----
.../markdown/recipes/rabbitmq_consumer_group.md | 213 -----
.../recipes/rsync_replicated_file_store.md | 162 ----
.../src/site/markdown/recipes/service_discovery.md | 184 ----
.../site/markdown/recipes/task_dag_execution.md | 199 -----
website/0.8.0/src/site/markdown/tutorial_admin.md | 408 ---------
website/0.8.0/src/site/markdown/tutorial_agent.md | 169 ----
.../0.8.0/src/site/markdown/tutorial_controller.md | 153 ----
website/0.8.0/src/site/markdown/tutorial_health.md | 46 -
.../0.8.0/src/site/markdown/tutorial_messaging.md | 70 --
.../src/site/markdown/tutorial_participant.md | 102 ---
.../0.8.0/src/site/markdown/tutorial_propstore.md | 34 -
.../0.8.0/src/site/markdown/tutorial_rebalance.md | 181 ----
.../src/site/markdown/tutorial_rest_service.md | 951 ---------------------
.../0.8.0/src/site/markdown/tutorial_spectator.md | 75 --
website/0.8.0/src/site/markdown/tutorial_state.md | 131 ---
.../src/site/markdown/tutorial_task_framework.md | 382 ---------
.../src/site/markdown/tutorial_task_throttling.md | 41 -
.../0.8.0/src/site/markdown/tutorial_throttling.md | 39 -
website/0.8.0/src/site/markdown/tutorial_ui.md | 118 ---
.../site/markdown/tutorial_user_content_store.md | 67 --
.../site/markdown/tutorial_user_def_rebalancer.md | 172 ----
website/0.8.0/src/site/markdown/tutorial_yaml.md | 102 ---
website/0.8.0/src/site/resources/.htaccess | 20 -
website/0.8.0/src/site/resources/JobExample.json | 19 -
.../0.8.0/src/site/resources/WorkflowExample.json | 46 -
.../resources/css/bootstrap-responsive.min.css | 9 -
.../0.8.0/src/site/resources/css/bootstrap.min.css | 9 -
website/0.8.0/src/site/resources/download.cgi | 22 -
.../src/site/resources/images/PFS-Generic.png | Bin 72435 -> 0 bytes
.../src/site/resources/images/RSYNC_BASED_PFS.png | Bin 78007 -> 0 bytes
.../site/resources/images/TaskFrameworkLayers.png | Bin 11622 -> 0 bytes
.../src/site/resources/images/UIScreenshot.png | Bin 83460 -> 0 bytes
.../src/site/resources/images/UIScreenshot2.png | Bin 121388 -> 0 bytes
.../0.8.0/src/site/resources/js/bootstrap.min.js | 6 -
website/0.8.0/src/site/resources/js/jquery.min.js | 2 -
website/0.8.0/src/site/site.xml | 143 ----
website/0.8.0/src/site/xdoc/download.xml.vm | 214 -----
website/0.8.0/src/test/conf/testng.xml | 27 -
website/0.8.1/pom.xml | 51 --
website/0.8.1/src/site/apt/privacy-policy.apt | 52 --
.../src/site/apt/releasenotes/release-0.8.1.apt | 135 ---
website/0.8.1/src/site/markdown/Building.md | 42 -
website/0.8.1/src/site/markdown/Features.md | 313 -------
website/0.8.1/src/site/markdown/Metrics.md | 217 -----
website/0.8.1/src/site/markdown/Quickstart.md | 663 --------------
website/0.8.1/src/site/markdown/Tutorial.md | 207 -----
website/0.8.1/src/site/markdown/design_crushed.md | 173 ----
website/0.8.1/src/site/markdown/index.md | 58 --
.../src/site/markdown/recipes/lock_manager.md | 236 -----
.../markdown/recipes/rabbitmq_consumer_group.md | 213 -----
.../recipes/rsync_replicated_file_store.md | 162 ----
.../src/site/markdown/recipes/service_discovery.md | 184 ----
.../site/markdown/recipes/task_dag_execution.md | 199 -----
website/0.8.1/src/site/markdown/tutorial_admin.md | 408 ---------
website/0.8.1/src/site/markdown/tutorial_agent.md | 169 ----
.../0.8.1/src/site/markdown/tutorial_controller.md | 153 ----
website/0.8.1/src/site/markdown/tutorial_health.md | 46 -
.../0.8.1/src/site/markdown/tutorial_messaging.md | 70 --
.../src/site/markdown/tutorial_participant.md | 102 ---
.../0.8.1/src/site/markdown/tutorial_propstore.md | 34 -
.../0.8.1/src/site/markdown/tutorial_rebalance.md | 181 ----
.../src/site/markdown/tutorial_rest_service.md | 951 ---------------------
.../0.8.1/src/site/markdown/tutorial_spectator.md | 75 --
website/0.8.1/src/site/markdown/tutorial_state.md | 131 ---
.../src/site/markdown/tutorial_task_framework.md | 395 ---------
.../src/site/markdown/tutorial_task_throttling.md | 41 -
.../0.8.1/src/site/markdown/tutorial_throttling.md | 39 -
website/0.8.1/src/site/markdown/tutorial_ui.md | 118 ---
.../site/markdown/tutorial_user_content_store.md | 67 --
.../site/markdown/tutorial_user_def_rebalancer.md | 172 ----
website/0.8.1/src/site/markdown/tutorial_yaml.md | 102 ---
website/0.8.1/src/site/resources/.htaccess | 20 -
website/0.8.1/src/site/resources/JobExample.json | 19 -
.../0.8.1/src/site/resources/WorkflowExample.json | 46 -
.../resources/css/bootstrap-responsive.min.css | 9 -
.../0.8.1/src/site/resources/css/bootstrap.min.css | 9 -
website/0.8.1/src/site/resources/download.cgi | 22 -
.../src/site/resources/images/PFS-Generic.png | Bin 72435 -> 0 bytes
.../src/site/resources/images/RSYNC_BASED_PFS.png | Bin 78007 -> 0 bytes
.../site/resources/images/TaskFrameworkLayers.png | Bin 11622 -> 0 bytes
.../src/site/resources/images/UIScreenshot.png | Bin 83460 -> 0 bytes
.../src/site/resources/images/UIScreenshot2.png | Bin 121388 -> 0 bytes
.../images/design/crushed/after-using-crushed.png | Bin 9935 -> 0 bytes
.../images/design/crushed/before-using-crush.png | Bin 10286 -> 0 bytes
.../resources/images/design/crushed/classes.png | Bin 14742 -> 0 bytes
.../images/design/crushed/crushed-master-dist.png | Bin 18725 -> 0 bytes
.../design/crushed/crushed-partition-dist.png | Bin 16630 -> 0 bytes
.../images/design/crushed/cursh-master-dist.png | Bin 18036 -> 0 bytes
.../images/design/crushed/cursh-partition-dist.png | Bin 16391 -> 0 bytes
.../crushed/example-cluster-master-dist-after.png | Bin 12899 -> 0 bytes
.../design/crushed/example-cluster-master-dist.png | Bin 13601 -> 0 bytes
.../crushed/example-cluster-partition-dist.png | Bin 13472 -> 0 bytes
.../crushed/example-movement-on-expansion.png | Bin 31833 -> 0 bytes
.../design/crushed/node-down-master-move.png | Bin 16897 -> 0 bytes
.../design/crushed/node-down-partition-move.png | Bin 15982 -> 0 bytes
.../images/design/crushed/performance.png | Bin 17532 -> 0 bytes
.../0.8.1/src/site/resources/js/bootstrap.min.js | 6 -
website/0.8.1/src/site/resources/js/jquery.min.js | 2 -
website/0.8.1/src/site/site.xml | 143 ----
website/0.8.1/src/site/xdoc/download.xml.vm | 226 -----
website/0.8.1/src/test/conf/testng.xml | 27 -
website/0.8.2/pom.xml | 51 --
website/0.8.2/src/site/apt/privacy-policy.apt | 52 --
.../src/site/apt/releasenotes/release-0.8.2.apt | 101 ---
.../src/site/apt/releasenotes/release-0.8.2.apt~ | 100 ---
website/0.8.2/src/site/markdown/Building.md | 42 -
website/0.8.2/src/site/markdown/Features.md | 313 -------
website/0.8.2/src/site/markdown/Metrics.md | 217 -----
website/0.8.2/src/site/markdown/Quickstart.md | 663 --------------
website/0.8.2/src/site/markdown/Tutorial.md | 207 -----
website/0.8.2/src/site/markdown/design_crushed.md | 173 ----
website/0.8.2/src/site/markdown/index.md | 58 --
.../src/site/markdown/recipes/lock_manager.md | 236 -----
.../markdown/recipes/rabbitmq_consumer_group.md | 213 -----
.../recipes/rsync_replicated_file_store.md | 162 ----
.../src/site/markdown/recipes/service_discovery.md | 184 ----
.../site/markdown/recipes/task_dag_execution.md | 199 -----
website/0.8.2/src/site/markdown/tutorial_admin.md | 408 ---------
website/0.8.2/src/site/markdown/tutorial_agent.md | 169 ----
.../0.8.2/src/site/markdown/tutorial_controller.md | 153 ----
website/0.8.2/src/site/markdown/tutorial_health.md | 46 -
.../0.8.2/src/site/markdown/tutorial_messaging.md | 70 --
.../src/site/markdown/tutorial_participant.md | 102 ---
.../0.8.2/src/site/markdown/tutorial_propstore.md | 34 -
.../0.8.2/src/site/markdown/tutorial_rebalance.md | 181 ----
.../src/site/markdown/tutorial_rest_service.md | 951 ---------------------
.../0.8.2/src/site/markdown/tutorial_spectator.md | 75 --
website/0.8.2/src/site/markdown/tutorial_state.md | 131 ---
.../src/site/markdown/tutorial_task_framework.md | 395 ---------
.../src/site/markdown/tutorial_task_throttling.md | 41 -
.../0.8.2/src/site/markdown/tutorial_throttling.md | 39 -
website/0.8.2/src/site/markdown/tutorial_ui.md | 118 ---
.../site/markdown/tutorial_user_content_store.md | 67 --
.../site/markdown/tutorial_user_def_rebalancer.md | 172 ----
website/0.8.2/src/site/markdown/tutorial_yaml.md | 102 ---
website/0.8.2/src/site/resources/.htaccess | 20 -
website/0.8.2/src/site/resources/JobExample.json | 19 -
.../0.8.2/src/site/resources/WorkflowExample.json | 46 -
.../resources/css/bootstrap-responsive.min.css | 9 -
.../0.8.2/src/site/resources/css/bootstrap.min.css | 9 -
website/0.8.2/src/site/resources/download.cgi | 22 -
.../src/site/resources/images/PFS-Generic.png | Bin 72435 -> 0 bytes
.../src/site/resources/images/RSYNC_BASED_PFS.png | Bin 78007 -> 0 bytes
.../site/resources/images/TaskFrameworkLayers.png | Bin 11622 -> 0 bytes
.../src/site/resources/images/UIScreenshot.png | Bin 83460 -> 0 bytes
.../src/site/resources/images/UIScreenshot2.png | Bin 121388 -> 0 bytes
.../images/design/crushed/after-using-crushed.png | Bin 9935 -> 0 bytes
.../images/design/crushed/before-using-crush.png | Bin 10286 -> 0 bytes
.../resources/images/design/crushed/classes.png | Bin 14742 -> 0 bytes
.../images/design/crushed/crushed-master-dist.png | Bin 18725 -> 0 bytes
.../design/crushed/crushed-partition-dist.png | Bin 16630 -> 0 bytes
.../images/design/crushed/cursh-master-dist.png | Bin 18036 -> 0 bytes
.../images/design/crushed/cursh-partition-dist.png | Bin 16391 -> 0 bytes
.../crushed/example-cluster-master-dist-after.png | Bin 12899 -> 0 bytes
.../design/crushed/example-cluster-master-dist.png | Bin 13601 -> 0 bytes
.../crushed/example-cluster-partition-dist.png | Bin 13472 -> 0 bytes
.../crushed/example-movement-on-expansion.png | Bin 31833 -> 0 bytes
.../design/crushed/node-down-master-move.png | Bin 16897 -> 0 bytes
.../design/crushed/node-down-partition-move.png | Bin 15982 -> 0 bytes
.../images/design/crushed/performance.png | Bin 17532 -> 0 bytes
.../0.8.2/src/site/resources/js/bootstrap.min.js | 6 -
website/0.8.2/src/site/resources/js/jquery.min.js | 2 -
website/0.8.2/src/site/site.xml | 143 ----
website/0.8.2/src/site/xdoc/download.xml.vm | 226 -----
website/0.8.2/src/test/conf/testng.xml | 27 -
website/0.8.3/pom.xml | 51 --
website/0.8.3/src/site/apt/privacy-policy.apt | 52 --
.../src/site/apt/releasenotes/release-0.8.3.apt | 80 --
website/0.8.3/src/site/markdown/Building.md | 42 -
website/0.8.3/src/site/markdown/Features.md | 313 -------
website/0.8.3/src/site/markdown/Metrics.md | 217 -----
website/0.8.3/src/site/markdown/Quickstart.md | 663 --------------
website/0.8.3/src/site/markdown/Tutorial.md | 208 -----
website/0.8.3/src/site/markdown/design_crushed.md | 173 ----
website/0.8.3/src/site/markdown/index.md | 58 --
.../0.8.3/src/site/markdown/quota_scheduling.md | 173 ----
.../src/site/markdown/recipes/lock_manager.md | 236 -----
.../markdown/recipes/rabbitmq_consumer_group.md | 213 -----
.../recipes/rsync_replicated_file_store.md | 162 ----
.../src/site/markdown/recipes/service_discovery.md | 184 ----
.../site/markdown/recipes/task_dag_execution.md | 199 -----
website/0.8.3/src/site/markdown/tutorial_admin.md | 408 ---------
website/0.8.3/src/site/markdown/tutorial_agent.md | 169 ----
.../0.8.3/src/site/markdown/tutorial_controller.md | 153 ----
website/0.8.3/src/site/markdown/tutorial_health.md | 46 -
.../0.8.3/src/site/markdown/tutorial_messaging.md | 70 --
.../src/site/markdown/tutorial_participant.md | 102 ---
.../0.8.3/src/site/markdown/tutorial_propstore.md | 34 -
.../0.8.3/src/site/markdown/tutorial_rebalance.md | 181 ----
.../src/site/markdown/tutorial_rest_service.md | 951 ---------------------
.../0.8.3/src/site/markdown/tutorial_spectator.md | 75 --
website/0.8.3/src/site/markdown/tutorial_state.md | 131 ---
.../src/site/markdown/tutorial_task_framework.md | 395 ---------
.../src/site/markdown/tutorial_task_throttling.md | 41 -
.../0.8.3/src/site/markdown/tutorial_throttling.md | 39 -
website/0.8.3/src/site/markdown/tutorial_ui.md | 118 ---
.../site/markdown/tutorial_user_content_store.md | 67 --
.../site/markdown/tutorial_user_def_rebalancer.md | 172 ----
website/0.8.3/src/site/markdown/tutorial_yaml.md | 102 ---
website/0.8.3/src/site/resources/.htaccess | 20 -
website/0.8.3/src/site/resources/JobExample.json | 19 -
.../0.8.3/src/site/resources/WorkflowExample.json | 46 -
.../resources/css/bootstrap-responsive.min.css | 9 -
.../0.8.3/src/site/resources/css/bootstrap.min.css | 9 -
website/0.8.3/src/site/resources/download.cgi | 22 -
.../src/site/resources/images/PFS-Generic.png | Bin 72435 -> 0 bytes
.../src/site/resources/images/RSYNC_BASED_PFS.png | Bin 78007 -> 0 bytes
.../site/resources/images/TaskFrameworkLayers.png | Bin 11622 -> 0 bytes
.../src/site/resources/images/UIScreenshot.png | Bin 83460 -> 0 bytes
.../src/site/resources/images/UIScreenshot2.png | Bin 121388 -> 0 bytes
.../images/design/crushed/after-using-crushed.png | Bin 9935 -> 0 bytes
.../images/design/crushed/before-using-crush.png | Bin 10286 -> 0 bytes
.../resources/images/design/crushed/classes.png | Bin 14742 -> 0 bytes
.../images/design/crushed/crushed-master-dist.png | Bin 18725 -> 0 bytes
.../design/crushed/crushed-partition-dist.png | Bin 16630 -> 0 bytes
.../images/design/crushed/cursh-master-dist.png | Bin 18036 -> 0 bytes
.../images/design/crushed/cursh-partition-dist.png | Bin 16391 -> 0 bytes
.../crushed/example-cluster-master-dist-after.png | Bin 12899 -> 0 bytes
.../design/crushed/example-cluster-master-dist.png | Bin 13601 -> 0 bytes
.../crushed/example-cluster-partition-dist.png | Bin 13472 -> 0 bytes
.../crushed/example-movement-on-expansion.png | Bin 31833 -> 0 bytes
.../design/crushed/node-down-master-move.png | Bin 16897 -> 0 bytes
.../design/crushed/node-down-partition-move.png | Bin 15982 -> 0 bytes
.../images/design/crushed/performance.png | Bin 17532 -> 0 bytes
.../images/quota_InstanceCapacityManager.jpeg | Bin 93818 -> 0 bytes
.../src/site/resources/images/quota_intro.png | Bin 450591 -> 0 bytes
.../0.8.3/src/site/resources/js/bootstrap.min.js | 6 -
website/0.8.3/src/site/resources/js/jquery.min.js | 2 -
website/0.8.3/src/site/site.xml | 143 ----
website/0.8.3/src/site/xdoc/download.xml.vm | 226 -----
website/0.8.3/src/test/conf/testng.xml | 27 -
website/0.8.4/pom.xml | 51 --
website/0.8.4/src/site/apt/privacy-policy.apt | 52 --
.../src/site/apt/releasenotes/release-0.8.4.apt | 86 --
website/0.8.4/src/site/markdown/Building.md | 42 -
website/0.8.4/src/site/markdown/Features.md | 313 -------
website/0.8.4/src/site/markdown/Metrics.md | 217 -----
website/0.8.4/src/site/markdown/Quickstart.md | 663 --------------
website/0.8.4/src/site/markdown/Tutorial.md | 208 -----
.../src/site/markdown/auto_exit_maintenance.md | 169 ----
website/0.8.4/src/site/markdown/design_crushed.md | 173 ----
website/0.8.4/src/site/markdown/index.md | 58 --
.../0.8.4/src/site/markdown/quota_scheduling.md | 173 ----
.../src/site/markdown/recipes/lock_manager.md | 236 -----
.../markdown/recipes/rabbitmq_consumer_group.md | 213 -----
.../recipes/rsync_replicated_file_store.md | 162 ----
.../src/site/markdown/recipes/service_discovery.md | 184 ----
.../site/markdown/recipes/task_dag_execution.md | 199 -----
website/0.8.4/src/site/markdown/tutorial_admin.md | 408 ---------
website/0.8.4/src/site/markdown/tutorial_agent.md | 169 ----
.../0.8.4/src/site/markdown/tutorial_controller.md | 153 ----
website/0.8.4/src/site/markdown/tutorial_health.md | 46 -
.../0.8.4/src/site/markdown/tutorial_messaging.md | 70 --
.../src/site/markdown/tutorial_participant.md | 102 ---
.../0.8.4/src/site/markdown/tutorial_propstore.md | 34 -
.../0.8.4/src/site/markdown/tutorial_rebalance.md | 181 ----
.../src/site/markdown/tutorial_rest_service.md | 951 ---------------------
.../0.8.4/src/site/markdown/tutorial_spectator.md | 75 --
website/0.8.4/src/site/markdown/tutorial_state.md | 131 ---
.../src/site/markdown/tutorial_task_framework.md | 395 ---------
.../src/site/markdown/tutorial_task_throttling.md | 41 -
.../0.8.4/src/site/markdown/tutorial_throttling.md | 39 -
website/0.8.4/src/site/markdown/tutorial_ui.md | 118 ---
.../site/markdown/tutorial_user_content_store.md | 67 --
.../site/markdown/tutorial_user_def_rebalancer.md | 172 ----
website/0.8.4/src/site/markdown/tutorial_yaml.md | 102 ---
website/0.8.4/src/site/resources/.htaccess | 20 -
website/0.8.4/src/site/resources/JobExample.json | 19 -
.../0.8.4/src/site/resources/WorkflowExample.json | 46 -
.../resources/css/bootstrap-responsive.min.css | 9 -
.../0.8.4/src/site/resources/css/bootstrap.min.css | 9 -
website/0.8.4/src/site/resources/download.cgi | 22 -
.../src/site/resources/images/PFS-Generic.png | Bin 72435 -> 0 bytes
.../src/site/resources/images/RSYNC_BASED_PFS.png | Bin 78007 -> 0 bytes
.../site/resources/images/TaskFrameworkLayers.png | Bin 11622 -> 0 bytes
.../src/site/resources/images/UIScreenshot.png | Bin 83460 -> 0 bytes
.../src/site/resources/images/UIScreenshot2.png | Bin 121388 -> 0 bytes
.../resources/images/auto-exit-maintenance.jpg | Bin 38492 -> 0 bytes
.../images/design/crushed/after-using-crushed.png | Bin 9935 -> 0 bytes
.../images/design/crushed/before-using-crush.png | Bin 10286 -> 0 bytes
.../resources/images/design/crushed/classes.png | Bin 14742 -> 0 bytes
.../images/design/crushed/crushed-master-dist.png | Bin 18725 -> 0 bytes
.../design/crushed/crushed-partition-dist.png | Bin 16630 -> 0 bytes
.../images/design/crushed/cursh-master-dist.png | Bin 18036 -> 0 bytes
.../images/design/crushed/cursh-partition-dist.png | Bin 16391 -> 0 bytes
.../crushed/example-cluster-master-dist-after.png | Bin 12899 -> 0 bytes
.../design/crushed/example-cluster-master-dist.png | Bin 13601 -> 0 bytes
.../crushed/example-cluster-partition-dist.png | Bin 13472 -> 0 bytes
.../crushed/example-movement-on-expansion.png | Bin 31833 -> 0 bytes
.../design/crushed/node-down-master-move.png | Bin 16897 -> 0 bytes
.../design/crushed/node-down-partition-move.png | Bin 15982 -> 0 bytes
.../images/design/crushed/performance.png | Bin 17532 -> 0 bytes
.../images/quota_InstanceCapacityManager.jpeg | Bin 93818 -> 0 bytes
.../src/site/resources/images/quota_intro.png | Bin 450591 -> 0 bytes
.../0.8.4/src/site/resources/js/bootstrap.min.js | 6 -
website/0.8.4/src/site/resources/js/jquery.min.js | 2 -
website/0.8.4/src/site/site.xml | 143 ----
website/0.8.4/src/site/xdoc/download.xml.vm | 226 -----
website/0.8.4/src/test/conf/testng.xml | 27 -
website/pom.xml | 5 -
website/src/site/resources/.htaccess | 5 -
website/src/site/site.xml | 5 -
311 files changed, 33626 deletions(-)
diff --git a/website/0.8.0/pom.xml b/website/0.8.0/pom.xml
deleted file mode 100644
index 71bef02..0000000
--- a/website/0.8.0/pom.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" ?>
-<!--
- ~ Licensed to the Apache Software Foundation (ASF) under one
- ~ or more contributor license agreements. See the NOTICE file
- ~ distributed with this work for additional information
- ~ regarding copyright ownership. The ASF licenses this file
- ~ to you under the Apache License, Version 2.0 (the
- ~ "License"); you may not use this file except in compliance
- ~ with the License. You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "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.
- -->
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
- <modelVersion>4.0.0</modelVersion>
-
- <parent>
- <groupId>org.apache.helix</groupId>
- <artifactId>website</artifactId>
- <version>1.0.3-SNAPSHOT</version>
- </parent>
-
- <artifactId>0.8.0-docs</artifactId>
- <packaging>bundle</packaging>
- <name>Apache Helix :: Website :: 0.8.0</name>
-
- <properties>
- </properties>
-
- <dependencies>
- <dependency>
- <groupId>org.testng</groupId>
- <artifactId>testng</artifactId>
- <version>6.0.1</version>
- </dependency>
- </dependencies>
- <build>
- <pluginManagement>
- <plugins>
- </plugins>
- </pluginManagement>
- <plugins>
- </plugins>
- </build>
-</project>
diff --git a/website/0.8.0/src/site/apt/privacy-policy.apt b/website/0.8.0/src/site/apt/privacy-policy.apt
deleted file mode 100644
index ada9363..0000000
--- a/website/0.8.0/src/site/apt/privacy-policy.apt
+++ /dev/null
@@ -1,52 +0,0 @@
- ----
- Privacy Policy
- -----
- Olivier Lamy
- -----
- 2013-02-04
- -----
-
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "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.
-
-Privacy Policy
-
- Information about your use of this website is collected using server access logs and a tracking cookie. The
- collected information consists of the following:
-
- [[1]] The IP address from which you access the website;
-
- [[2]] The type of browser and operating system you use to access our site;
-
- [[3]] The date and time you access our site;
-
- [[4]] The pages you visit; and
-
- [[5]] The addresses of pages from where you followed a link to our site.
-
- []
-
- Part of this information is gathered using a tracking cookie set by the
- {{{http://www.google.com/analytics/}Google Analytics}} service and handled by Google as described in their
- {{{http://www.google.com/privacy.html}privacy policy}}. See your browser documentation for instructions on how to
- disable the cookie if you prefer not to share this data with Google.
-
- We use the gathered information to help us make our site more useful to visitors and to better understand how and
- when our site is used. We do not track or collect personally identifiable information or associate gathered data
- with any personally identifying information from other sources.
-
- By using this website, you consent to the collection of this data in the manner and for the purpose described above.
diff --git a/website/0.8.0/src/site/apt/releasenotes/release-0.8.0.apt b/website/0.8.0/src/site/apt/releasenotes/release-0.8.0.apt
deleted file mode 100644
index 027c367..0000000
--- a/website/0.8.0/src/site/apt/releasenotes/release-0.8.0.apt
+++ /dev/null
@@ -1,249 +0,0 @@
- -----
- Release Notes for Apache Helix 0.8.0
- -----
-
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "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.
-
-~~ NOTE: For help with the syntax of this file, see:
-~~ http://maven.apache.org/guides/mini/guide-apt-format.html
-
-Release Notes for Apache Helix 0.8.0
-
- The Apache Helix team would like to announce the release of Apache Helix 0.8.0.
-
- This is the twelfth release under the Apache umbrella, and the eighth as a top-level project.
-
- Helix is a generic cluster management framework used for the automatic management of partitioned, replicated and distributed resources hosted on a cluster of nodes. Helix provides the following features:
-
- * Automatic assignment of resource/partition to nodes
-
- * Node failure detection and recovery
-
- * Dynamic addition of Resources
-
- * Dynamic addition of nodes to the cluster
-
- * Pluggable distributed state machine to manage the state of a resource via state transitions
-
- * Automatic load balancing and throttling of transitions
-
-[]
-
-* Detailed Changes
-
-** New Features
-
- * Helix REST 2.0
-
- * All admin operations are exposed via restful API
-
- * Support all task framework API
-
- * Helix Rest 2.0 uses standard HTTP methods if possible, instead of customized command as in HelixAdminWeb
-
- * Access log can be enabled for both read and write access
-
- * New Helix UI (helix-front) which allows you to :
-
- * View detailed cluster information
-
- * View resources / instances in a Helix cluster
-
- * View partition placement and health status in a resource
-
- * Create new Helix clusters
-
- * Enable / Disable a cluster / resource / instance
-
- * Add an instance into a Helix cluster
-
- * New Full-auto rebalancer featured with :
-
- * CRUSH-based rack-aware partition placement algorithm
-
- * Delayed rebalance which minimizes re-shuffle of the resident partitions on an instance during short-period outage, while still maintaining minimal active replicas for application's availability need
-
- * Throttled partition movements that allows maximum number of pending state transitions to be set at cluster, resource or instance level
-
- * New P2P (Participant-to-participant) state-transition message to allow much faster mastership handoff
-
- * Helix Cluster Maintenance Mode
-
- * Application can put a cluster into maintenance mode. When a cluster in maintenance mode, no new partitions will be bootstrapped, however, existing partitions will still be maintained
-
-** Bug Fixes
-
- * Fixed NPE if rebalance strategy is not specified in IS.
-
- * Fixed a minor issue when updating a workflowConfig with empty workflowId.
-
- * Fixed MultiRound CRUSH that cannot select any node from second round
-
- * Fixed a bug in caching bestpossible states in ClusterDataCache.
-
- * Fixed MissingTopStatePartitionGauge reports negative number issue.
-
- * Fixed TaskStateModel thread leaking issue, and name all thread-pool created in Helix.
-
- * Fixed no master replica when all of replica in new instances turn to ERROR state when migrating existing replicas to all new instances in DelayedAutoRebalancer.
-
- * Fixed NPE in clusterstatusmonitor.
-
- * Fixed build the workflowconfig by fromHelixProperty
-
- * Fixed comparison method violating the contract
-
- * Fixed NPEs for HelixTask Executors
-
- * Fixed WorkflowConfig.Builder.fromMap() to copy WorkflowID
-
- * Fixed a bug where context could not be read due to missing NAME field
-
- * Fixed deadlock in GenericHelixController
-
- * Fixed active MBean domain names for different instance types.
-
- * Fixed duplication of HelixCallBackMonitors
-
- * Fixed a bug when deleting a job from queue without context
-
- * Fixed a NPE in DelayedAutoRebalancer, adding more debug logs.
-
- * Fixed unexpected idealstate overwrite when persist assignment is on.
-
- * Fixed disconnected zkConnection issue.
-
- * Fixed Resource json format issue.
-
- * Fixed ClusterConfig record output
-
- * Fixed resource config set path
-
- * Fixed rest JSON methods for restful service.
-
- * Fixed NPE for get disabled partitions
-
- * Fixed enable/disable partition in instances for specified resources
-
- * Fixed deleteJob from a recurrent job queue
-
- * Fixed a bug in AutoRebalanceStrategy, that assigned orphan replicas to its preferred nodes instead of random nodes.
-
- * Fixed a bug in BestPossibleExternalViewVerifier
-
- * Fixed Validation logic in JobConfig
-
- * Fixed Target Resource conflicts with number of tasks setting
-
- * Fixed JobQueue ignoring FailedThreshold
-
- * Fixed NPE when first time call WorkflowRebalancer
-
- * Fixed java 6 compatibility issue in AutoRebalancer.
-
- * Fixes for using 1.8 feature in 1.6 environment
-
- * Fixed BestPossibleExternalViewVerifier toString NPE
-
- * Fixed Task State Model INIT priority number
-
- * Fixed task assignment in instance group tag check
-
- * Do not set MaxPartitionPerNode in IdealState if it is not greater than 0.
-
- * Fixed missing workflowtype assignment in builder
-
- * Fixed NPE in ClusterStateVerifier
-
- * Fixed thread leaking problems in TaskStateModel. Using shared thread pool for all tasks and timeout tasks among all taskStateModels.
-
- * Fixed jobConfig to expose number_of_concurrent_task_per_instance to znode.
-
- * Fixed the bug when job expiry time is shorter than job schedule interval in recurring job queue. Add more debug log in TaskRebalancer.
-
-
-** Improvements
-
- * Performance Improvement
-
- * Task framework rebalance pipeline was separated from resource management pipeline in the controller
-
- * Reads and writes to ZK are batched during controller's rebalance pipeline to decrease the latency
-
- * Optimized the rebalance pipeline with cached data to avoid redundant calculation
-
- * New P2P (Participant-to-participant) state-transition message to allow much faster mastership handoff
-
- * New target external view to allow spectators to have a speculative view of ongoing rebalancing
-
- * Monitor Improvement
-
- * A set of new MBeans to monitor traffic and latency between controller/participant and Zookeeper
-
- * More MBeans to monitor performance of controller's rebalance pipeline
-
- * More MBeans to monitor running and queued workflows and jobs
-
- * Job scheduling should fail if the target resource does not exist anymore at the time of scheduling
-
- * Improved Integration test run speed
-
- * Added periodic rebalance to Helix controller
-
- * Upgraded Zookeeper dependency and fixed various zk connection and data update issues
-
- * Refactored the monitoring framework to simplify interfaces
-
- * Added monitor to ZkClient to monitor the pending callbacks
-
- * Improve the data load in Helix Spectator (RoutingTableProvider), which includes: 1) Put event callback handler in a spearate thread so other ZK event callbacks won't be blocked. 2) Deduplicate the callbacks from same event type, always keep just one latest copy of event callback in the event queue. 3) Add methods to return all instances and liveInstances in the cluster
-
- * Add cluster config to tolerate ERROR Partition when trying to schedule load balance transition
-
- * Optimize ClusterDataCache's data refresh strategy by: 1) cacheing CurrentStates locally and update only these that have been changed from zk. 2) Controller listens on ResourceConfig changes 3) Cache resource configs locally and update them all if there is any changes to resource configs
-
- * Avoid cascading failure by automatically disabling the cluster when too many partitions are crammed into an instance
-
- * Allow user to define a preference list for a partition in FULL-AUTO rebalance mode
-
- * Allow each individual change listener to selectively enable/disable PreFetch and BatchMode during the callback handling.
-
- * Added Cluster level state transition timeout
-
- * Persist participant's offline timestamp in ParticipantHistory
-
- * Added Serialization for HelixProperty
-
- * Added partition level priority support
-
- * Optimize partition movement when autorebalancing using the default strategy
-
- * Add support for flexible hirerachy representation of a cluster topology
-
- * Add StrictMatchExternalViewVerifier that verifies whether the ExternalViews of given resources (or all resources in the cluster) match exactly as its ideal mapping (in idealstate)
-
- * Improved Task Retry support
-
- * Generate Idealstate for a job resource only when it starts to run and remove it once the job is completed.
-
-
-[]
-
-Cheers,
---
-The Apache Helix Team
diff --git a/website/0.8.0/src/site/markdown/Building.md b/website/0.8.0/src/site/markdown/Building.md
deleted file mode 100644
index 8ae2fb5..0000000
--- a/website/0.8.0/src/site/markdown/Building.md
+++ /dev/null
@@ -1,42 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-Build Instructions
-------------------
-
-### From Source
-
-Requirements: JDK 1.6+, Maven 2.0.8+
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-mvn install package -DskipTests
-```
-
-### Maven Dependency
-
-```
-<dependency>
- <groupId>org.apache.helix</groupId>
- <artifactId>helix-core</artifactId>
- <version>0.8.0</version>
-</dependency>
-```
diff --git a/website/0.8.0/src/site/markdown/Features.md b/website/0.8.0/src/site/markdown/Features.md
deleted file mode 100644
index ba9d0e7..0000000
--- a/website/0.8.0/src/site/markdown/Features.md
+++ /dev/null
@@ -1,313 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Features</title>
-</head>
-
-Features
-----------------------------
-
-
-### CONFIGURING IDEALSTATE
-
-
-Read concepts page for definition of Idealstate.
-
-The placement of partitions in a DDS is very critical for reliability and scalability of the system.
-For example, when a node fails, it is important that the partitions hosted on that node are reallocated evenly among the remaining nodes. Consistent hashing is one such algorithm that can guarantee this.
-Helix by default comes with a variant of consistent hashing based of the RUSH algorithm.
-
-This means given a number of partitions, replicas and number of nodes Helix does the automatic assignment of partition to nodes such that
-
-* Each node has the same number of partitions and replicas of the same partition do not stay on the same node.
-* When a node fails, the partitions will be equally distributed among the remaining nodes
-* When new nodes are added, the number of partitions moved will be minimized along with satisfying the above two criteria.
-
-
-Helix provides multiple ways to control the placement and state of a replica.
-
-```
-
- |AUTO REBALANCE| AUTO | CUSTOM |
- -----------------------------------------
- LOCATION | HELIX | APP | APP |
- -----------------------------------------
- STATE | HELIX | HELIX | APP |
- -----------------------------------------
-```
-
-#### HELIX EXECUTION MODE
-
-
-Idealstate is defined as the state of the DDS when all nodes are up and running and healthy.
-Helix uses this as the target state of the system and computes the appropriate transitions needed in the system to bring it to a stable state.
-
-Helix supports 3 different execution modes which allows application to explicitly control the placement and state of the replica.
-
-##### AUTO_REBALANCE
-
-When the idealstate mode is set to AUTO_REBALANCE, Helix controls both the location of the replica along with the state. This option is useful for applications where creation of a replica is not expensive. Example
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO_REBALANCE",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- }
- "listFields" : {
- "MyResource_0" : [],
- "MyResource_1" : [],
- "MyResource_2" : []
- },
- "mapFields" : {
- }
-}
-```
-
-If there are 3 nodes in the cluster, then Helix will internally compute the ideal state as
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- },
- "mapFields" : {
- "MyResource_0" : {
- "N1" : "MASTER",
- "N2" : "SLAVE",
- },
- "MyResource_1" : {
- "N2" : "MASTER",
- "N3" : "SLAVE",
- },
- "MyResource_2" : {
- "N3" : "MASTER",
- "N1" : "SLAVE",
- }
- }
-}
-```
-
-Another typical example is evenly distributing a group of tasks among the currently alive processes. For example, if there are 60 tasks and 4 nodes, Helix assigns 15 tasks to each node.
-When one node fails Helix redistributes its 15 tasks to the remaining 3 nodes. Similarly, if a node is added, Helix re-allocates 3 tasks from each of the 4 nodes to the 5th node.
-
-#### AUTO
-
-When the idealstate mode is set to AUTO, Helix only controls STATE of the replicas where as the location of the partition is controlled by application. Example: The below idealstate indicates thats 'MyResource_0' must be only on node1 and node2. But gives the control of assigning the STATE to Helix.
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- }
- "listFields" : {
- "MyResource_0" : [node1, node2],
- "MyResource_1" : [node2, node3],
- "MyResource_2" : [node3, node1]
- },
- "mapFields" : {
- }
-}
-```
-In this mode when node1 fails, unlike in AUTO-REBALANCE mode the partition is not moved from node1 to others nodes in the cluster. Instead, Helix will decide to change the state of MyResource_0 in N2 based on the system constraints. For example, if a system constraint specified that there should be 1 Master and if the Master failed, then node2 will be made the new master.
-
-#### CUSTOM
-
-Helix offers a third mode called CUSTOM, in which application can completely control the placement and state of each replica. Applications will have to implement an interface that Helix will invoke when the cluster state changes.
-Within this callback, the application can recompute the idealstate. Helix will then issue appropriate transitions such that Idealstate and Currentstate converges.
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "CUSTOM",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- },
- "mapFields" : {
- "MyResource_0" : {
- "N1" : "MASTER",
- "N2" : "SLAVE",
- },
- "MyResource_1" : {
- "N2" : "MASTER",
- "N3" : "SLAVE",
- },
- "MyResource_2" : {
- "N3" : "MASTER",
- "N1" : "SLAVE",
- }
- }
-}
-```
-
-For example, the current state of the system might be 'MyResource_0' -> {N1:MASTER,N2:SLAVE} and the application changes the ideal state to 'MyResource_0' -> {N1:SLAVE,N2:MASTER}. Helix will not blindly issue MASTER-->SLAVE to N1 and SLAVE-->MASTER to N2 in parallel since it might result in a transient state where both N1 and N2 are masters.
-Helix will first issue MASTER-->SLAVE to N1 and after its completed it will issue SLAVE-->MASTER to N2.
-
-
-### State Machine Configuration
-
-Helix comes with 3 default state models that are most commonly used. Its possible to have multiple state models in a cluster.
-Every resource that is added should have a reference to the state model.
-
-* MASTER-SLAVE: Has 3 states OFFLINE,SLAVE,MASTER. Max masters is 1. Slaves will be based on the replication factor. Replication factor can be specified while adding the resource
-* ONLINE-OFFLINE: Has 2 states OFFLINE and ONLINE. Very simple state model and most applications start off with this state model.
-* LEADER-STANDBY:1 Leader and many stand bys. In general the standby's are idle.
-
-Apart from providing the state machine configuration, one can specify the constraints of states and transitions.
-
-For example one can say
-Master:1. Max number of replicas in Master state at any time is 1.
-OFFLINE-SLAVE:5 Max number of Offline-Slave transitions that can happen concurrently in the system
-
-STATE PRIORITY
-Helix uses greedy approach to satisfy the state constraints. For example if the state machine configuration says it needs 1 master and 2 slaves but only 1 node is active, Helix must promote it to master. This behavior is achieved by providing the state priority list as MASTER,SLAVE.
-
-STATE TRANSITION PRIORITY
-Helix tries to fire as many transitions as possible in parallel to reach the stable state without violating constraints. By default Helix simply sorts the transitions alphabetically and fires as many as it can without violating the constraints.
-One can control this by overriding the priority order.
-
-### Config management
-
-Helix allows applications to store application specific properties. The configuration can have different scopes.
-
-* Cluster
-* Node specific
-* Resource specific
-* Partition specific
-
-Helix also provides notifications when any configs are changed. This allows applications to support dynamic configuration changes.
-
-See HelixManager.getConfigAccessor for more info
-
-### Intra cluster messaging api
-
-This is an interesting feature which is quite useful in practice. Often times, nodes in DDS requires a mechanism to interact with each other. One such requirement is a process of bootstrapping a replica.
-
-Consider a search system use case where the index replica starts up and it does not have an index. One of the commonly used solutions is to get the index from a common location or to copy the index from another replica.
-Helix provides a messaging api, that can be used to talk to other nodes in the system. The value added that Helix provides here is, message recipient can be specified in terms of resource,
-partition, state and Helix ensures that the message is delivered to all of the required recipients. In this particular use case, the instance can specify the recipient criteria as all replicas of P1.
-Since Helix is aware of the global state of the system, it can send the message to appropriate nodes. Once the nodes respond Helix provides the bootstrapping replica with all the responses.
-
-This is a very generic api and can also be used to schedule various periodic tasks in the cluster like data backups etc.
-System Admins can also perform adhoc tasks like on demand backup or execute a system command(like rm -rf ;-)) across all nodes.
-
-```
- ClusterMessagingService messagingService = manager.getMessagingService();
- //CONSTRUCT THE MESSAGE
- Message requestBackupUriRequest = new Message(
- MessageType.USER_DEFINE_MSG, UUID.randomUUID().toString());
- requestBackupUriRequest
- .setMsgSubType(BootstrapProcess.REQUEST_BOOTSTRAP_URL);
- requestBackupUriRequest.setMsgState(MessageState.NEW);
- //SET THE RECIPIENT CRITERIA, All nodes that satisfy the criteria will receive the message
- Criteria recipientCriteria = new Criteria();
- recipientCriteria.setInstanceName("%");
- recipientCriteria.setRecipientInstanceType(InstanceType.PARTICIPANT);
- recipientCriteria.setResource("MyDB");
- recipientCriteria.setPartition("");
- //Should be processed only the process that is active at the time of sending the message.
- //This means if the recipient is restarted after message is sent, it will not be processed.
- recipientCriteria.setSessionSpecific(true);
- // wait for 30 seconds
- int timeout = 30000;
- //The handler that will be invoked when any recipient responds to the message.
- BootstrapReplyHandler responseHandler = new BootstrapReplyHandler();
- //This will return only after all recipients respond or after timeout.
- int sentMessageCount = messagingService.sendAndWait(recipientCriteria,
- requestBackupUriRequest, responseHandler, timeout);
-```
-
-See HelixManager.getMessagingService for more info.
-
-
-### Application specific property storage
-
-There are several usecases where applications needs support for distributed data structures. Helix uses Zookeeper to store the application data and hence provides notifications when the data changes.
-One value add Helix provides is the ability to specify cache the data and also write through cache. This is more efficient than reading from ZK every time.
-
-See HelixManager.getHelixPropertyStore
-
-### Throttling
-
-Since all state changes in the system are triggered through transitions, Helix can control the number of transitions that can happen in parallel. Some of the transitions may be light weight but some might involve moving data around which is quite expensive.
-Helix allows applications to set threshold on transitions. The threshold can be set at the multiple scopes.
-
-* MessageType e.g STATE_TRANSITION
-* TransitionType e.g SLAVE-MASTER
-* Resource e.g database
-* Node i.e per node max transitions in parallel.
-
-See HelixManager.getHelixAdmin.addMessageConstraint()
-
-### Health monitoring and alerting
-
-This in currently in development mode, not yet productionized.
-
-Helix provides ability for each node in the system to report health metrics on a periodic basis.
-Helix supports multiple ways to aggregate these metrics like simple SUM, AVG, EXPONENTIAL DECAY, WINDOW. Helix will only persist the aggregated value.
-Applications can define threshold on the aggregate values according to the SLA's and when the SLA is violated Helix will fire an alert.
-Currently Helix only fires an alert but eventually we plan to use this metrics to either mark the node dead or load balance the partitions.
-This feature will be valuable in for distributed systems that support multi-tenancy and have huge variation in work load patterns. Another place this can be used is to detect skewed partitions and rebalance the cluster.
-
-This feature is not yet stable and do not recommend to be used in production.
-
-
-### Controller deployment modes
-
-Read Architecture wiki for more details on the Role of a controller. In simple words, it basically controls the participants in the cluster by issuing transitions.
-
-Helix provides multiple options to deploy the controller.
-
-#### STANDALONE
-
-Controller can be started as a separate process to manage a cluster. This is the recommended approach. How ever since one controller can be a single point of failure, multiple controller processes are required for reliability.
-Even if multiple controllers are running only one will be actively managing the cluster at any time and is decided by a leader election process. If the leader fails, another leader will resume managing the cluster.
-
-Even though we recommend this method of deployment, it has the drawback of having to manage an additional service for each cluster. See Controller As a Service option.
-
-#### EMBEDDED
-
-If setting up a separate controller process is not viable, then it is possible to embed the controller as a library in each of the participant.
-
-#### CONTROLLER AS A SERVICE
-
-One of the cool feature we added in helix was use a set of controllers to manage a large number of clusters.
-For example if you have X clusters to be managed, instead of deploying X*3(3 controllers for fault tolerance) controllers for each cluster, one can deploy only 3 controllers. Each controller can manage X/3 clusters.
-If any controller fails the remaining two will manage X/2 clusters. At LinkedIn, we always deploy controllers in this mode.
-
-
-
-
-
-
-
-
diff --git a/website/0.8.0/src/site/markdown/Quickstart.md b/website/0.8.0/src/site/markdown/Quickstart.md
deleted file mode 100644
index e0f2878..0000000
--- a/website/0.8.0/src/site/markdown/Quickstart.md
+++ /dev/null
@@ -1,663 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Quickstart</title>
-</head>
-
-Quickstart
----------
-
-Get Helix
----------
-
-First, let\'s get Helix. Either build it, or download it.
-
-### Build
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-mvn install package -DskipTests
-cd helix-core/target/helix-core-pkg/bin # This folder contains all the scripts used in following sections
-chmod +x *
-```
-
-### Download
-
-Download the 0.8.0 release package [here](./download.html)
-
-Overview
---------
-
-In this Quickstart, we\'ll set up a master-slave replicated, partitioned system. Then we\'ll demonstrate how to add a node, rebalance the partitions, and show how Helix manages failover.
-
-
-Let\'s Do It
-------------
-
-Helix provides command line interfaces to set up the cluster and view the cluster state. The best way to understand how Helix views a cluster is to build a cluster.
-
-### Get to the Tools Directory
-
-If you built the code:
-
-```
-cd helix/helix/helix-core/target/helix-core-pkg/bin
-```
-
-If you downloaded the release package, extract it.
-
-
-Short Version
--------------
-You can observe the components working together in this demo, which does the following:
-
-* Create a cluster
-* Add 2 nodes (participants) to the cluster
-* Set up a resource with 6 partitions and 2 replicas: 1 Master, and 1 Slave per partition
-* Show the cluster state after Helix balances the partitions
-* Add a third node
-* Show the cluster state. Note that the third node has taken mastership of 2 partitions.
-* Kill the third node (Helix takes care of failover)
-* Show the cluster state. Note that the two surviving nodes take over mastership of the partitions from the failed node
-
-### Run the Demo
-
-```
-cd helix/helix/helix-core/target/helix-core-pkg/bin
-./quickstart.sh
-```
-
-#### The Initial Setup
-
-2 nodes are set up and the partitions are rebalanced.
-
-The cluster state is as follows:
-
-```
-CLUSTER STATE: After starting 2 nodes
- localhost_12000 localhost_12001
-MyResource_0 M S
-MyResource_1 S M
-MyResource_2 M S
-MyResource_3 M S
-MyResource_4 S M
-MyResource_5 S M
-```
-
-Note there is one master and one slave per partition.
-
-#### Add a Node
-
-A third node is added and the cluster is rebalanced.
-
-The cluster state changes to:
-
-```
-CLUSTER STATE: After adding a third node
- localhost_12000 localhost_12001 localhost_12002
-MyResource_0 S M S
-MyResource_1 S S M
-MyResource_2 M S S
-MyResource_3 S S M
-MyResource_4 M S S
-MyResource_5 S M S
-```
-
-Note there is one master and _two_ slaves per partition. This is expected because there are three nodes.
-
-#### Kill a Node
-
-Finally, a node is killed to simulate a failure
-
-Helix makes sure each partition has a master. The cluster state changes to:
-
-```
-CLUSTER STATE: After the 3rd node stops/crashes
- localhost_12000 localhost_12001 localhost_12002
-MyResource_0 S M -
-MyResource_1 S M -
-MyResource_2 M S -
-MyResource_3 M S -
-MyResource_4 M S -
-MyResource_5 S M -
-```
-
-
-Long Version
-------------
-Now you can run the same steps by hand. In this detailed version, we\'ll do the following:
-
-* Define a cluster
-* Add two nodes to the cluster
-* Add a 6-partition resource with 1 master and 2 slave replicas per partition
-* Verify that the cluster is healthy and inspect the Helix view
-* Expand the cluster: add a few nodes and rebalance the partitions
-* Failover: stop a node and verify the mastership transfer
-
-### Install and Start ZooKeeper
-
-Zookeeper can be started in standalone mode or replicated mode.
-
-More information is available at
-
-* http://zookeeper.apache.org/doc/r3.3.3/zookeeperStarted.html
-* http://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#sc_zkMulitServerSetup
-
-In this example, let\'s start zookeeper in local mode.
-
-#### Start ZooKeeper Locally on Port 2199
-
-```
-./start-standalone-zookeeper.sh 2199 &
-```
-
-### Define the Cluster
-
-The helix-admin tool is used for cluster administration tasks. In the Quickstart, we\'ll use the command line interface. Helix supports a REST interface as well.
-
-zookeeper_address is of the format host:port e.g localhost:2199 for standalone or host1:port,host2:port for multi-node.
-
-Next, we\'ll set up a cluster MYCLUSTER cluster with these attributes:
-
-* 3 instances running on localhost at ports 12913,12914,12915
-* One database named myDB with 6 partitions
-* Each partition will have 3 replicas with 1 master, 2 slaves
-* ZooKeeper running locally at localhost:2199
-
-#### Create the Cluster MYCLUSTER
-
-```
-# ./helix-admin.sh --zkSvr <zk_address> --addCluster <clustername>
-./helix-admin.sh --zkSvr localhost:2199 --addCluster MYCLUSTER
-```
-
-### Add Nodes to the Cluster
-
-In this case we\'ll add three nodes: localhost:12913, localhost:12914, localhost:12915
-
-```
-# helix-admin.sh --zkSvr <zk_address> --addNode <clustername> <host:port>
-./helix-admin.sh --zkSvr localhost:2199 --addNode MYCLUSTER localhost:12913
-./helix-admin.sh --zkSvr localhost:2199 --addNode MYCLUSTER localhost:12914
-./helix-admin.sh --zkSvr localhost:2199 --addNode MYCLUSTER localhost:12915
-```
-
-### Define the Resource and Partitioning
-
-In this example, the resource is a database, partitioned 6 ways. Note that in a production system, it\'s common to over-partition for better load balancing. Helix has been used in production to manage hundreds of databases each with 10s or 100s of partitions running on 10s of physical nodes.
-
-#### Create a Database with 6 Partitions using the MasterSlave State Model
-
-Helix ensures there will be exactly one master for each partition.
-
-```
-# helix-admin.sh --zkSvr <zk_address> --addResource <clustername> <resourceName> <numPartitions> <StateModelName>
-./helix-admin.sh --zkSvr localhost:2199 --addResource MYCLUSTER myDB 6 MasterSlave
-```
-
-#### Let Helix Assign Partitions to Nodes
-
-This command will distribute the partitions amongst all the nodes in the cluster. In this example, each partition has 3 replicas.
-
-```
-# helix-admin.sh --zkSvr <zk_address> --rebalance <clustername> <resourceName> <replication factor>
-./helix-admin.sh --zkSvr localhost:2199 --rebalance MYCLUSTER myDB 3
-```
-
-Now the cluster is defined in ZooKeeper. The nodes (localhost:12913, localhost:12914, localhost:12915) and resource (myDB, with 6 partitions using the MasterSlave model) are all properly configured. And the _IdealState_ has been calculated, assuming a replication factor of 3.
-
-### Start the Helix Controller
-
-Now that the cluster is defined in ZooKeeper, the Helix controller can manage the cluster.
-
-```
-# Start the cluster manager, which will manage MYCLUSTER
-./run-helix-controller.sh --zkSvr localhost:2199 --cluster MYCLUSTER 2>&1 > /tmp/controller.log &
-```
-
-### Start up the Cluster to be Managed
-
-We\'ve started up ZooKeeper, defined the cluster, the resources, the partitioning, and started up the Helix controller. Next, we\'ll start up the nodes of the system to be managed. Each node is a Participant, which is an instance of the system component to be managed. Helix assigns work to Participants, keeps track of their roles and health, and takes action when a node fails.
-
-```
-# 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 12913 --stateModelType MasterSlave 2>&1 > /tmp/participant_12913.log
-./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12914 --stateModelType MasterSlave 2>&1 > /tmp/participant_12914.log
-./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12915 --stateModelType MasterSlave 2>&1 > /tmp/participant_12915.log
-```
-
-### Inspect the Cluster
-
-Now, let\'s see the Helix view of our cluster. We\'ll work our way down as follows:
-
-```
-Clusters -> MYCLUSTER -> instances -> instance detail
- -> resources -> resource detail
- -> partitions
-```
-
-A single Helix controller can manage multiple clusters, though so far, we\'ve only defined one cluster. Let\'s see:
-
-```
-# List existing clusters
-./helix-admin.sh --zkSvr localhost:2199 --listClusters
-
-Existing clusters:
-MYCLUSTER
-```
-
-Now, let\'s see the Helix view of MYCLUSTER:
-
-```
-# helix-admin.sh --zkSvr <zk_address> --listClusterInfo <clusterName>
-./helix-admin.sh --zkSvr localhost:2199 --listClusterInfo MYCLUSTER
-
-Existing resources in cluster MYCLUSTER:
-myDB
-Instances in cluster MYCLUSTER:
-localhost_12915
-localhost_12914
-localhost_12913
-```
-
-Let\'s look at the details of an instance:
-
-```
-# ./helix-admin.sh --zkSvr <zk_address> --listInstanceInfo <clusterName> <InstanceName>
-./helix-admin.sh --zkSvr localhost:2199 --listInstanceInfo MYCLUSTER localhost_12913
-
-InstanceConfig: {
- "id" : "localhost_12913",
- "mapFields" : {
- },
- "listFields" : {
- },
- "simpleFields" : {
- "HELIX_ENABLED" : "true",
- "HELIX_HOST" : "localhost",
- "HELIX_PORT" : "12913"
- }
-}
-```
-
-
-#### Query Information about a Resource
-
-```
-# helix-admin.sh --zkSvr <zk_address> --listResourceInfo <clusterName> <resourceName>
-./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo MYCLUSTER myDB
-
-IdealState for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- },
- "myDB_1" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "MASTER"
- },
- "myDB_4" : {
- "localhost_12913" : "MASTER",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- "myDB_0" : [ "localhost_12914", "localhost_12913", "localhost_12915" ],
- "myDB_1" : [ "localhost_12915", "localhost_12913", "localhost_12914" ],
- "myDB_2" : [ "localhost_12913", "localhost_12915", "localhost_12914" ],
- "myDB_3" : [ "localhost_12915", "localhost_12913", "localhost_12914" ],
- "myDB_4" : [ "localhost_12913", "localhost_12914", "localhost_12915" ],
- "myDB_5" : [ "localhost_12914", "localhost_12915", "localhost_12913" ]
- },
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "REBALANCE_MODE" : "SEMI_AUTO",
- "NUM_PARTITIONS" : "6",
- "REPLICAS" : "3",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- "STATE_MODEL_FACTORY_NAME" : "DEFAULT"
- }
-}
-
-ExternalView for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- },
- "myDB_1" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "MASTER"
- },
- "myDB_4" : {
- "localhost_12913" : "MASTER",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- },
- "simpleFields" : {
- "BUCKET_SIZE" : "0"
- }
-}
-```
-
-Now, let\'s look at one of the partitions:
-
-```
-# helix-admin.sh --zkSvr <zk_address> --listResourceInfo <clusterName> <partition>
-./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo mycluster myDB_0
-```
-
-### Expand the Cluster
-
-Next, we\'ll show how Helix does the work that you\'d otherwise have to build into your system. When you add capacity to your cluster, you want the work to be evenly distributed. In this example, we started with 3 nodes, with 6 partitions. The partitions were evenly balanced, 2 masters and 4 slaves per node. Let\'s add 3 more nodes: localhost:12916, localhost:12917, localhost:12918
-
-```
-./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
-```
-
-And start up these instances:
-
-```
-# 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>&1 > /tmp/participant_12916.log
-./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12917 --stateModelType MasterSlave 2>&1 > /tmp/participant_12917.log
-./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12918 --stateModelType MasterSlave 2>&1 > /tmp/participant_12918.log
-```
-
-
-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.
-
-```
-./helix-admin.sh --zkSvr localhost:2199 --rebalance MYCLUSTER myDB 3
-```
-
-### View the Cluster
-
-OK, let\'s see how it looks:
-
-
-```
-./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo MYCLUSTER myDB
-
-IdealState for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_1" : {
- "localhost_12916" : "SLAVE",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12915" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_4" : {
- "localhost_12916" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- "myDB_0" : [ "localhost_12917", "localhost_12913", "localhost_12914" ],
- "myDB_1" : [ "localhost_12918", "localhost_12917", "localhost_12916" ],
- "myDB_2" : [ "localhost_12913", "localhost_12917", "localhost_12918" ],
- "myDB_3" : [ "localhost_12915", "localhost_12917", "localhost_12918" ],
- "myDB_4" : [ "localhost_12916", "localhost_12917", "localhost_12918" ],
- "myDB_5" : [ "localhost_12914", "localhost_12915", "localhost_12913" ]
- },
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "REBALANCE_MODE" : "SEMI_AUTO",
- "NUM_PARTITIONS" : "6",
- "REPLICAS" : "3",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- "STATE_MODEL_FACTORY_NAME" : "DEFAULT"
- }
-}
-
-ExternalView for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_1" : {
- "localhost_12916" : "SLAVE",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12915" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_4" : {
- "localhost_12916" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- },
- "simpleFields" : {
- "BUCKET_SIZE" : "0"
- }
-}
-```
-
-Mission accomplished. The partitions are nicely balanced.
-
-### How about Failover?
-
-Building a fault tolerant system isn\'t trivial, but with Helix, it\'s easy. Helix detects a failed instance, and triggers mastership transfer automatically.
-
-First, let's fail an instance. In this example, we\'ll kill localhost:12918 to simulate a failure.
-
-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:
-
-
-```
-./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo MYCLUSTER myDB
-
-IdealState for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_1" : {
- "localhost_12916" : "SLAVE",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12915" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_4" : {
- "localhost_12916" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- "myDB_0" : [ "localhost_12917", "localhost_12913", "localhost_12914" ],
- "myDB_1" : [ "localhost_12918", "localhost_12917", "localhost_12916" ],
- "myDB_2" : [ "localhost_12913", "localhost_12918", "localhost_12917" ],
- "myDB_3" : [ "localhost_12915", "localhost_12918", "localhost_12917" ],
- "myDB_4" : [ "localhost_12916", "localhost_12917", "localhost_12918" ],
- "myDB_5" : [ "localhost_12914", "localhost_12915", "localhost_12913" ]
- },
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "REBALANCE_MODE" : "SEMI_AUTO",
- "NUM_PARTITIONS" : "6",
- "REPLICAS" : "3",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- "STATE_MODEL_FACTORY_NAME" : "DEFAULT"
- }
-}
-
-ExternalView for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_1" : {
- "localhost_12916" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12917" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12915" : "MASTER",
- "localhost_12917" : "SLAVE"
- },
- "myDB_4" : {
- "localhost_12916" : "MASTER",
- "localhost_12917" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- },
- "simpleFields" : {
- "BUCKET_SIZE" : "0"
- }
-}
-```
-
-As we\'ve seen in this Quickstart, Helix takes care of partitioning, load balancing, elasticity, failure detection and recovery.
-
-### ZooInspector
-
-You can view all of the underlying data by going direct to zookeeper. Use ZooInspector that comes with zookeeper to browse the data. This is a java applet (make sure you have X windows)
-
-To start zooinspector run the following command from <zk_install_directory>/contrib/ZooInspector
-
-```
-java -cp zookeeper-3.3.3-ZooInspector.jar:lib/jtoaster-1.0.4.jar:../../lib/log4j-1.2.15.jar:../../zookeeper-3.3.3.jar org.apache.zookeeper.inspector.ZooInspector
-```
-
-### Next
-
-Now that you understand the idea of Helix, read the [tutorial](./Tutorial.html) to learn how to choose the right state model and constraints for your system, and how to implement it. In many cases, the built-in features meet your requirements. And best of all, Helix is a customizable framework, so you can plug in your own behavior, while retaining the automation provided by Helix.
-
diff --git a/website/0.8.0/src/site/markdown/Tutorial.md b/website/0.8.0/src/site/markdown/Tutorial.md
deleted file mode 100644
index d487d99..0000000
--- a/website/0.8.0/src/site/markdown/Tutorial.md
+++ /dev/null
@@ -1,207 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial</title>
-</head>
-
-# Helix Tutorial
-
-In this tutorial, we will cover the roles of a Helix-managed cluster, and show the code you need to write to integrate with it. In many cases, there is a simple default behavior that is often appropriate, but you can also customize the behavior.
-
-Convention: we first cover the _basic_ approach, which is the easiest to implement. Then, we'll describe _advanced_ options, which give you more control over the system behavior, but require you to write more code.
-
-
-### Prerequisites
-
-1. Read [Concepts/Terminology](../Concepts.html) and [Architecture](../Architecture.html)
-2. Read the [Quickstart guide](./Quickstart.html) to learn how Helix models and manages a cluster
-3. Install Helix source. See: [Quickstart](./Quickstart.html) for the steps.
-
-### Tutorial Outline
-
-1. [Participant](./tutorial_participant.html)
-2. [Spectator](./tutorial_spectator.html)
-3. [Controller](./tutorial_controller.html)
-4. [Rebalancing Algorithms](./tutorial_rebalance.html)
-5. [User-Defined Rebalancing](./tutorial_user_def_rebalancer.html)
-6. [State Machines](./tutorial_state.html)
-7. [Messaging](./tutorial_messaging.html)
-8. [Customized health check](./tutorial_health.html)
-9. [Throttling](./tutorial_throttling.html)
-10. [Application Property Store](./tutorial_propstore.html)
-11. [Admin Interface](./tutorial_admin.html)
-12. [YAML Cluster Setup](./tutorial_yaml.html)
-13. [Helix Agent (for non-JVM systems)](./tutorial_agent.html)
-14. [Task Framework](./tutorial_task_framework.html)
- 1. [Task with User Defined Content Store](./tutorial_user_content_store.html)
- 2. [Task Throttling](./tutorial_task_throttling.html)
-15. [Helix REST Service 2.0](./tutorial_rest_service.html)
-16. [Helix UI Setup](./tutorial_ui.html)
-
-### Preliminaries
-
-First, we need to set up the system. Let\'s walk through the steps in building a distributed system using Helix.
-
-#### Start ZooKeeper
-
-This starts a zookeeper in standalone mode. For production deployment, see [Apache ZooKeeper](http://zookeeper.apache.org) for instructions.
-
-```
-./start-standalone-zookeeper.sh 2199 &
-```
-
-#### Create a Cluster
-
-Creating a cluster will define the cluster in appropriate znodes on ZooKeeper.
-
-Using the Java API:
-
-```
-// Create setup tool instance
-// Note: ZK_ADDRESS is the host:port of Zookeeper
-String ZK_ADDRESS = "localhost:2199";
-admin = new ZKHelixAdmin(ZK_ADDRESS);
-
-String CLUSTER_NAME = "helix-demo";
-//Create cluster namespace in zookeeper
-admin.addCluster(CLUSTER_NAME);
-```
-
-OR
-
-Using the command-line interface:
-
-```
-./helix-admin.sh --zkSvr localhost:2199 --addCluster helix-demo
-```
-
-
-#### Configure the Nodes of the Cluster
-
-First we\'ll add new nodes to the cluster, then configure the nodes in the cluster. Each node in the cluster must be uniquely identifiable.
-The most commonly used convention is hostname:port.
-
-```
-String CLUSTER_NAME = "helix-demo";
-int NUM_NODES = 2;
-String hosts[] = new String[]{"localhost","localhost"};
-String ports[] = new String[]{7000,7001};
-for (int i = 0; i < NUM_NODES; i++)
-{
- InstanceConfig instanceConfig = new InstanceConfig(hosts[i]+ "_" + ports[i]);
- instanceConfig.setHostName(hosts[i]);
- instanceConfig.setPort(ports[i]);
- instanceConfig.setInstanceEnabled(true);
-
- //Add additional system specific configuration if needed. These can be accessed during the node start up.
- instanceConfig.getRecord().setSimpleField("key", "value");
- admin.addInstance(CLUSTER_NAME, instanceConfig);
-}
-```
-
-#### Configure the Resource
-
-A __resource__ represents the actual task performed by the nodes. It can be a database, index, topic, queue or any other processing entity.
-A resource can be divided into many sub-parts known as __partitions__.
-
-
-##### Define the State Model and Constraints
-
-For scalability and fault tolerance, each partition can have one or more replicas.
-The __state model__ allows one to declare the system behavior by first enumerating the various STATES, and the TRANSITIONS between them.
-A simple model is ONLINE-OFFLINE where ONLINE means the task is active and OFFLINE means it\'s not active.
-You can also specify how many replicas must be in each state, these are known as __constraints__.
-For example, in a search system, one might need more than one node serving the same index to handle the load.
-
-The allowed states:
-
-* MASTER
-* SLAVE
-* OFFLINE
-
-The allowed transitions:
-
-* OFFLINE to SLAVE
-* SLAVE to OFFLINE
-* SLAVE to MASTER
-* MASTER to SLAVE
-
-The constraints:
-
-* no more than 1 MASTER per partition
-* the rest of the replicas should be slaves
-
-The following snippet shows how to declare the state model and constraints for the MASTER-SLAVE model.
-
-```
-StateModelDefinition.Builder builder = new StateModelDefinition.Builder(STATE_MODEL_NAME);
-
-// Add states and their rank to indicate priority. A lower rank corresponds to a higher priority
-builder.addState(MASTER, 1);
-builder.addState(SLAVE, 2);
-builder.addState(OFFLINE);
-
-// Set the initial state when the node starts
-builder.initialState(OFFLINE);
-
-// Add transitions between the states.
-builder.addTransition(OFFLINE, SLAVE);
-builder.addTransition(SLAVE, OFFLINE);
-builder.addTransition(SLAVE, MASTER);
-builder.addTransition(MASTER, SLAVE);
-
-// set constraints on states
-
-// static constraint: upper bound of 1 MASTER
-builder.upperBound(MASTER, 1);
-
-// dynamic constraint: R means it should be derived based on the replication factor for the cluster
-// this allows a different replication factor for each resource without
-// having to define a new state model
-
-builder.dynamicUpperBound(SLAVE, "R");
-
-StateModelDefinition statemodelDefinition = builder.build();
-admin.addStateModelDef(CLUSTER_NAME, STATE_MODEL_NAME, myStateModel);
-```
-
-##### Assigning Partitions to Nodes
-
-The final goal of Helix is to ensure that the constraints on the state model are satisfied.
-Helix does this by assigning a __state__ to a partition (such as MASTER, SLAVE), and placing it on a particular node.
-
-There are 3 assignment modes Helix can operate in:
-
-* FULL_AUTO: Helix decides the placement and state of a partition.
-* SEMI_AUTO: Application decides the placement but Helix decides the state of a partition.
-* CUSTOMIZED: Application controls the placement and state of a partition.
-
-For more information on the assignment modes, see the [Rebalancing Algorithms](./tutorial_rebalance.html) section of this tutorial.
-
-```
-String RESOURCE_NAME = "MyDB";
-int NUM_PARTITIONS = 6;
-STATE_MODEL_NAME = "MasterSlave";
-String MODE = "SEMI_AUTO";
-int NUM_REPLICAS = 2;
-
-admin.addResource(CLUSTER_NAME, RESOURCE_NAME, NUM_PARTITIONS, STATE_MODEL_NAME, MODE);
-admin.rebalance(CLUSTER_NAME, RESOURCE_NAME, NUM_REPLICAS);
-```
diff --git a/website/0.8.0/src/site/markdown/index.md b/website/0.8.0/src/site/markdown/index.md
deleted file mode 100644
index e86a16d..0000000
--- a/website/0.8.0/src/site/markdown/index.md
+++ /dev/null
@@ -1,51 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Helix 0.8.0 Documentation</title>
-</head>
-
-### Get Helix
-
-[Download](./download.html)
-
-[Building](./Building.html)
-
-[Release Notes](./releasenotes/release-0.8.0.html)
-
-### Hands-On
-
-[Quickstart](./Quickstart.html)
-
-[Tutorial](./Tutorial.html)
-
-[Javadocs](http://helix.apache.org/javadocs/0.8.0/index.html)
-
-### Recipes
-
-[Distributed lock manager](./recipes/lock_manager.html)
-
-[Rabbit MQ consumer group](./recipes/rabbitmq_consumer_group.html)
-
-[Rsync replicated file store](./recipes/rsync_replicated_file_store.html)
-
-[Service discovery](./recipes/service_discovery.html)
-
-[Distributed task DAG execution](./recipes/task_dag_execution.html)
-
diff --git a/website/0.8.0/src/site/markdown/recipes/lock_manager.md b/website/0.8.0/src/site/markdown/recipes/lock_manager.md
deleted file mode 100644
index 7e276e3..0000000
--- a/website/0.8.0/src/site/markdown/recipes/lock_manager.md
+++ /dev/null
@@ -1,236 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-Distributed Lock Manager
-------------------------
-Distributed locks are used to synchronize accesses shared resources. Most applications today use ZooKeeper to model distributed locks.
-
-The simplest way to model a lock using ZooKeeper is (See ZooKeeper leader recipe for an exact and more advanced solution)
-
-* Each process tries to create an emphemeral node
-* If the node is successfully created, the process acquires the lock
-* Otherwise, it will watch the ZNode and try to acquire the lock again if the current lock holder disappears
-
-This is good enough if there is only one lock. But in practice, an application will need many such locks. Distributing and managing the locks among difference process becomes challenging. Extending such a solution to many locks will result in:
-
-* Uneven distribution of locks among nodes; the node that starts first will acquire all the locks. Nodes that start later will be idle.
-* When a node fails, how the locks will be distributed among remaining nodes is not predicable.
-* When new nodes are added the current nodes don\'t relinquish the locks so that new nodes can acquire some locks
-
-In other words we want a system to satisfy the following requirements.
-
-* Distribute locks evenly among all nodes to get better hardware utilization
-* If a node fails, the locks that were acquired by that node should be evenly distributed among other nodes
-* If nodes are added, locks must be evenly re-distributed among nodes.
-
-Helix provides a simple and elegant solution to this problem. Simply specify the number of locks and Helix will ensure that above constraints are satisfied.
-
-To quickly see this working run the `lock-manager-demo` script where 12 locks are evenly distributed among three nodes, and when a node fails, the locks get re-distributed among remaining two nodes. Note that Helix does not re-shuffle the locks completely, instead it simply distributes the locks relinquished by dead node among 2 remaining nodes evenly.
-
-----------------------------------------------------------------------------------------
-
-### Short Version
-This version starts multiple threads within the same process to simulate a multi node deployment. Try the long version to get a better idea of how it works.
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-mvn clean install package -DskipTests
-cd recipes/distributed-lock-manager/target/distributed-lock-manager-pkg/bin
-chmod +x *
-./lock-manager-demo
-```
-
-#### Output
-
-```
-./lock-manager-demo
-STARTING localhost_12000
-STARTING localhost_12002
-STARTING localhost_12001
-STARTED localhost_12000
-STARTED localhost_12002
-STARTED localhost_12001
-localhost_12001 acquired lock:lock-group_3
-localhost_12000 acquired lock:lock-group_8
-localhost_12001 acquired lock:lock-group_2
-localhost_12001 acquired lock:lock-group_4
-localhost_12002 acquired lock:lock-group_1
-localhost_12002 acquired lock:lock-group_10
-localhost_12000 acquired lock:lock-group_7
-localhost_12001 acquired lock:lock-group_5
-localhost_12002 acquired lock:lock-group_11
-localhost_12000 acquired lock:lock-group_6
-localhost_12002 acquired lock:lock-group_0
-localhost_12000 acquired lock:lock-group_9
-lockName acquired By
-======================================
-lock-group_0 localhost_12002
-lock-group_1 localhost_12002
-lock-group_10 localhost_12002
-lock-group_11 localhost_12002
-lock-group_2 localhost_12001
-lock-group_3 localhost_12001
-lock-group_4 localhost_12001
-lock-group_5 localhost_12001
-lock-group_6 localhost_12000
-lock-group_7 localhost_12000
-lock-group_8 localhost_12000
-lock-group_9 localhost_12000
-Stopping localhost_12000
-localhost_12000 Interrupted
-localhost_12001 acquired lock:lock-group_9
-localhost_12001 acquired lock:lock-group_8
-localhost_12002 acquired lock:lock-group_6
-localhost_12002 acquired lock:lock-group_7
-lockName acquired By
-======================================
-lock-group_0 localhost_12002
-lock-group_1 localhost_12002
-lock-group_10 localhost_12002
-lock-group_11 localhost_12002
-lock-group_2 localhost_12001
-lock-group_3 localhost_12001
-lock-group_4 localhost_12001
-lock-group_5 localhost_12001
-lock-group_6 localhost_12002
-lock-group_7 localhost_12002
-lock-group_8 localhost_12001
-lock-group_9 localhost_12001
-
-```
-
-----------------------------------------------------------------------------------------
-
-### Long version
-This provides more details on how to setup the cluster and where to plugin application code.
-
-#### Start ZooKeeper
-
-```
-./start-standalone-zookeeper 2199
-```
-
-#### Create a Cluster
-
-```
-./helix-admin --zkSvr localhost:2199 --addCluster lock-manager-demo
-```
-
-#### Create a Lock Group
-
-Create a lock group and specify the number of locks in the lock group.
-
-```
-./helix-admin --zkSvr localhost:2199 --addResource lock-manager-demo lock-group 6 OnlineOffline --mode AUTO_REBALANCE
-```
-
-#### Start the Nodes
-
-Create a Lock class that handles the callbacks.
-
-```
-public class Lock extends StateModel {
- private String lockName;
-
- public Lock(String lockName) {
- this.lockName = lockName;
- }
-
- public void lock(Message m, NotificationContext context) {
- System.out.println(" acquired lock:"+ lockName );
- }
-
- public void release(Message m, NotificationContext context) {
- System.out.println(" releasing lock:"+ lockName );
- }
-
-}
-```
-
-and a LockFactory that creates Locks
-
-```
-public class LockFactory extends StateModelFactory<Lock> {
- /* Instantiates the lock handler, one per lockName */
- public Lock create(String lockName) {
- return new Lock(lockName);
- }
-}
-```
-
-At node start up, simply join the cluster and Helix will invoke the appropriate callbacks on the appropriate Lock instance. One can start any number of nodes and Helix detects that a new node has joined the cluster and re-distributes the locks automatically.
-
-```
-public class LockProcess {
- public static void main(String args) {
- String zkAddress= "localhost:2199";
- String clusterName = "lock-manager-demo";
- //Give a unique id to each process, most commonly used format hostname_port
- String instanceName ="localhost_12000";
- ZKHelixAdmin helixAdmin = new ZKHelixAdmin(zkAddress);
- //configure the instance and provide some metadata
- InstanceConfig config = new InstanceConfig(instanceName);
- config.setHostName("localhost");
- config.setPort("12000");
- admin.addInstance(clusterName, config);
- //join the cluster
- HelixManager manager;
- manager = HelixManagerFactory.getHelixManager(clusterName,
- instanceName,
- InstanceType.PARTICIPANT,
- zkAddress);
- manager.getStateMachineEngine().registerStateModelFactory("OnlineOffline", modelFactory);
- manager.connect();
- Thread.currentThread.join();
- }
-}
-```
-
-#### Start the Controller
-
-The controller can be started either as a separate process or can be embedded within each node process
-
-##### Separate Process
-This is recommended when number of nodes in the cluster \> 100. For fault tolerance, you can run multiple controllers on different boxes.
-
-```
-./run-helix-controller --zkSvr localhost:2199 --cluster lock-manager-demo 2>&1 > /tmp/controller.log &
-```
-
-##### Embedded Within the Node Process
-This is recommended when the number of nodes in the cluster is less than 100. To start a controller from each process, simply add the following lines to MyClass
-
-```
-public class LockProcess {
- public static void main(String args) {
- String zkAddress= "localhost:2199";
- String clusterName = "lock-manager-demo";
- // .
- // .
- manager.connect();
- HelixManager controller;
- controller = HelixControllerMain.startHelixController(zkAddress,
- clusterName,
- "controller",
- HelixControllerMain.STANDALONE);
- Thread.currentThread.join();
- }
-}
-```
diff --git a/website/0.8.0/src/site/markdown/recipes/rabbitmq_consumer_group.md b/website/0.8.0/src/site/markdown/recipes/rabbitmq_consumer_group.md
deleted file mode 100644
index e0659db..0000000
--- a/website/0.8.0/src/site/markdown/recipes/rabbitmq_consumer_group.md
+++ /dev/null
@@ -1,213 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-
-RabbitMQ Consumer Group
------------------------
-
-[RabbitMQ](http://www.rabbitmq.com/) is well-known open source software the provides robust messaging for applications.
-
-One of the commonly implemented recipes using this software is a work queue. [http://www.rabbitmq.com/tutorials/tutorial-four-java.html](http://www.rabbitmq.com/tutorials/tutorial-four-java.html) describes the use case where
-
-* A producer sends a message with a routing key
-* The message is routed to the queue whose binding key exactly matches the routing key of the message
-* There are multiple consumers and each consumer is interested in processing only a subset of the messages by binding to the interested keys
-
-The example provided [here](http://www.rabbitmq.com/tutorials/tutorial-four-java.html) describes how multiple consumers can be started to process all the messages.
-
-While this works, in production systems one needs the following:
-
-* Ability to handle failures: when a consumer fails, another consumer must be started or the other consumers must start processing these messages that should have been processed by the failed consumer
-* When the existing consumers cannot keep up with the task generation rate, new consumers will be added. The tasks must be redistributed among all the consumers
-
-In this recipe, we demonstrate handling of consumer failures and new consumer additions using Helix.
-
-Mapping this usecase to Helix is pretty easy as the binding key/routing key is equivalent to a partition.
-
-Let's take an example. Lets say the queue has 6 partitions, and we have 2 consumers to process all the queues.
-What we want is all 6 queues to be evenly divided among 2 consumers.
-Eventually when the system scales, we add more consumers to keep up. This will make each consumer process tasks from 2 queues.
-Now let's say that a consumer failed, reducing the number of active consumers to 2. This means each consumer must process 3 queues.
-
-We showcase how such a dynamic application can be developed using Helix. Even though we use RabbitMQ as the pub/sub system one can extend this solution to other pub/sub systems.
-
-### Try It
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-mvn clean install package -DskipTests
-cd recipes/rabbitmq-consumer-group/bin
-chmod +x *
-export HELIX_PKG_ROOT=`pwd`/helix-core/target/helix-core-pkg
-export HELIX_RABBITMQ_ROOT=`pwd`/recipes/rabbitmq-consumer-group/
-chmod +x $HELIX_PKG_ROOT/bin/*
-chmod +x $HELIX_RABBITMQ_ROOT/bin/*
-```
-
-#### Install RabbitMQ
-
-Setting up RabbitMQ on a local box is straightforward. You can find the instructions here
-http://www.rabbitmq.com/download.html
-
-#### Start ZK
-
-Start ZooKeeper at port 2199
-
-```
-$HELIX_PKG_ROOT/bin/start-standalone-zookeeper 2199
-```
-
-#### Setup the Consumer Group Cluster
-
-This will setup the cluster by creating a "rabbitmq-consumer-group" cluster and adds a "topic" with "6" queues.
-
-```
-$HELIX_RABBITMQ_ROOT/bin/setup-cluster.sh localhost:2199
-```
-
-#### Add Consumers
-
-Start 2 consumers in 2 different terminals. Each consumer is given a unique ID.
-
-```
-//start-consumer.sh zookeeperAddress (e.g. localhost:2181) consumerId , rabbitmqServer (e.g. localhost)
-$HELIX_RABBITMQ_ROOT/bin/start-consumer.sh localhost:2199 0 localhost
-$HELIX_RABBITMQ_ROOT/bin/start-consumer.sh localhost:2199 1 localhost
-
-```
-
-#### Start the Helix Controller
-
-Now start a Helix controller that starts managing the "rabbitmq-consumer-group" cluster.
-
-```
-$HELIX_RABBITMQ_ROOT/bin/start-cluster-manager.sh localhost:2199
-```
-
-#### Send Messages to the Topic
-
-Start sending messages to the topic. This script randomly selects a routing key (1-6) and sends the message to topic.
-Based on the key, messages gets routed to the appropriate queue.
-
-```
-$HELIX_RABBITMQ_ROOT/bin/send-message.sh localhost 20
-```
-
-After running this, you should see all 20 messages being processed by 2 consumers.
-
-#### Add Another Consumer
-
-Once a new consumer is started, Helix detects it. In order to balance the load between 3 consumers, it deallocates 1 partition from the existing consumers and allocates it to the new consumer. We see that
-each consumer is now processing only 2 queues.
-Helix makes sure that old nodes are asked to stop consuming before the new consumer is asked to start consuming for a given partition. But the transitions for each partition can happen in parallel.
-
-```
-$HELIX_RABBITMQ_ROOT/bin/start-consumer.sh localhost:2199 2 localhost
-```
-
-Send messages again to the topic
-
-```
-$HELIX_RABBITMQ_ROOT/bin/send-message.sh localhost 100
-```
-
-You should see that messages are now received by all 3 consumers.
-
-#### Stop a Consumer
-
-In any terminal press CTRL^C and notice that Helix detects the consumer failure and distributes the 2 partitions that were processed by failed consumer to the remaining 2 active consumers.
-
-
-### How does this work?
-
-Find the entire code [here](https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tree;f=recipes/rabbitmq-consumer-group/src/main/java/org/apache/helix/recipes/rabbitmq).
-
-#### Cluster Setup
-
-This step creates ZNode on ZooKeeper for the cluster and adds the state model. We use online offline state model since there is no need for other states. The consumer is either processing a queue or it is not.
-
-It creates a resource called "rabbitmq-consumer-group" with 6 partitions. The execution mode is set to AUTO_REBALANCE. This means that the Helix controls the assignment of partition to consumers and automatically distributes the partitions evenly among the active consumers. When a consumer is added or removed, it ensures that a minimum number of partitions are shuffled.
-
-```
-zkclient = new ZkClient(zkAddr, ZkClient.DEFAULT_SESSION_TIMEOUT,
- ZkClient.DEFAULT_CONNECTION_TIMEOUT, new ZNRecordSerializer());
-ZKHelixAdmin admin = new ZKHelixAdmin(zkclient);
-
-// add cluster
-admin.addCluster(clusterName, true);
-
-// add state model definition
-StateModelConfigGenerator generator = new StateModelConfigGenerator();
-admin.addStateModelDef(clusterName, "OnlineOffline",
- new StateModelDefinition(generator.generateConfigForOnlineOffline()));
-
-// add resource "topic" which has 6 partitions
-String resourceName = "rabbitmq-consumer-group";
-admin.addResource(clusterName, resourceName, 6, "OnlineOffline", "AUTO_REBALANCE");
-```
-
-### Starting the Consumers
-
-The only thing consumers need to know is the ZooKeeper address, cluster name and consumer ID. It does not need to know anything else.
-
-```
-_manager = HelixManagerFactory.getZKHelixManager(_clusterName,
- _consumerId,
- InstanceType.PARTICIPANT,
- _zkAddr);
-
-StateMachineEngine stateMach = _manager.getStateMachineEngine();
-ConsumerStateModelFactory modelFactory =
- new ConsumerStateModelFactory(_consumerId, _mqServer);
-stateMach.registerStateModelFactory("OnlineOffline", modelFactory);
-
-_manager.connect();
-```
-
-Once the consumer has registered the state model and the controller is started, the consumer starts getting callbacks (onBecomeOnlineFromOffline) for the partition it needs to host. All it needs to do as part of the callback is to start consuming messages from the appropriate queue. Similarly, when the controller deallocates a partitions from a consumer, it fires onBecomeOfflineFromOnline for the same partition.
-As a part of this transition, the consumer will stop consuming from a that queue.
-
-```
-@Transition(to = "ONLINE", from = "OFFLINE")
-public void onBecomeOnlineFromOffline(Message message, NotificationContext context) {
- LOG.debug(_consumerId + " becomes ONLINE from OFFLINE for " + _partition);
- if (_thread == null) {
- LOG.debug("Starting ConsumerThread for " + _partition + "...");
- _thread = new ConsumerThread(_partition, _mqServer, _consumerId);
- _thread.start();
- LOG.debug("Starting ConsumerThread for " + _partition + " done");
-
- }
-}
-
-@Transition(to = "OFFLINE", from = "ONLINE")
-public void onBecomeOfflineFromOnline(Message message, NotificationContext context)
- throws InterruptedException {
- LOG.debug(_consumerId + " becomes OFFLINE from ONLINE for " + _partition);
- if (_thread != null) {
- LOG.debug("Stopping " + _consumerId + " for " + _partition + "...");
- _thread.interrupt();
- _thread.join(2000);
- _thread = null;
- LOG.debug("Stopping " + _consumerId + " for " + _partition + " done");
- }
-}
-```
diff --git a/website/0.8.0/src/site/markdown/recipes/rsync_replicated_file_store.md b/website/0.8.0/src/site/markdown/recipes/rsync_replicated_file_store.md
deleted file mode 100644
index 2ace265..0000000
--- a/website/0.8.0/src/site/markdown/recipes/rsync_replicated_file_store.md
+++ /dev/null
@@ -1,162 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-Near-Realtime Rsync Replicated File System
-------------------------------------------
-
-### Quick Demo
-
-* This demo starts 3 instances with id's as ```localhost_12001, localhost_12002, localhost_12003```
-* Each instance stores its files under ```/tmp/<id>/filestore```
-* ```localhost_12001``` is designated as the master, and ```localhost_12002``` and ```localhost_12003``` are the slaves
-* Files written to the master are replicated to the slaves automatically. In this demo, a.txt and b.txt are written to ```/tmp/localhost_12001/filestore``` and they get replicated to other folders.
-* When the master is stopped, ```localhost_12002``` is promoted to master.
-* The other slave ```localhost_12003``` stops replicating from ```localhost_12001``` and starts replicating from new master ```localhost_12002```
-* Files written to new master ```localhost_12002``` are replicated to ```localhost_12003```
-* In the end state of this quick demo, ```localhost_12002``` is the master and ```localhost_12003``` is the slave. Manually create files under ```/tmp/localhost_12002/filestore``` and see that appear in ```/tmp/localhost_12003/filestore```
-* Ignore the interrupted exceptions on the console :-)
-
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-cd recipes/rsync-replicated-file-system/
-mvn clean install package -DskipTests
-cd target/rsync-replicated-file-system-pkg/bin
-chmod +x *
-./quickdemo
-
-```
-
-### Overview
-
-There are many applications that require storage for storing large number of relatively small data files. Examples include media stores to store small videos, images, mail attachments etc. Each of these objects is typically kilobytes, often no larger than a few megabytes. An additional distinguishing feature of these use cases is that files are typically only added or deleted, rarely updated. When there are updates, they do not have any concurrency requirements.
-
-These are much simpler requirements than what general purpose distributed file system have to satisfy; these would include concurrent access to files, random access for reads and updates, posix compliance, and others. To satisfy those requirements, general DFSs are also pretty complex that are expensive to build and maintain.
-
-A different implementation of a distributed file system includes HDFS which is inspired by Google's GFS. This is one of the most widely used distributed file system that forms the main data storage platform for Hadoop. HDFS is primary aimed at processing very large data sets and distributes files across a cluster of commodity servers by splitting up files in fixed size chunks. HDFS is not particularly well suited for storing a very large number of relatively tiny files.
-
-### File Store
-
-It's possible to build a vastly simpler system for the class of applications that have simpler requirements as we have pointed out.
-
-* Large number of files but each file is relatively small
-* Access is limited to create, delete and get entire files
-* No updates to files that are already created (or it's feasible to delete the old file and create a new one)
-
-
-We call this system a Partitioned File Store (PFS) to distinguish it from other distributed file systems. This system needs to provide the following features:
-
-* CRD access to large number of small files
-* Scalability: Files should be distributed across a large number of commodity servers based on the storage requirement
-* Fault-tolerance: Each file should be replicated on multiple servers so that individual server failures do not reduce availability
-* Elasticity: It should be possible to add capacity to the cluster easily
-
-
-Apache Helix is a generic cluster management framework that makes it very easy to provide scalability, fault-tolerance and elasticity features.
-rsync can be easily used as a replication channel between servers so that each file gets replicated on multiple servers.
-
-### Design
-
-#### High Level
-
-* Partition the file system based on the file name
-* At any time a single writer can write, we call this a master
-* For redundancy, we need to have additional replicas called slave. Slaves can optionally serve reads
-* Slave replicates data from the master
-* When a master fails, a slave gets promoted to master
-
-#### Transaction Log
-
-Every write on the master will result in creation/deletion of one or more files. In order to maintain timeline consistency slaves need to apply the changes in the same order
-To facilitate this, the master logs each transaction in a file and each transaction is associated with an 64 bit ID in which the 32 LSB represents a sequence number and MSB represents the generation number
-The sequence number gets incremented on every transaction and the generation is incremented when a new master is elected
-
-#### Replication
-
-Replication is required for slaves to keep up with changes on the master. Every time the slave applies a change it checkpoints the last applied transaction ID.
-During restarts, this allows the slave to pull changes from the last checkpointed ID. Similar to master, the slave logs each transaction to the transaction logs but instead of generating new transaction ID, it uses the same ID generated by the master.
-
-
-#### Failover
-
-When a master fails, a new slave will be promoted to master. If the previous master node is reachable, then the new master will flush all the
-changes from previous the master before taking up mastership. The new master will record the end transaction ID of the current generation and then start a new generation
-with sequence starting from 1. After this the master will begin accepting writes.
-
-
-
-
-
-### Rsync-based Solution
-
-
-
-
-This application demonstrates a file store that uses rsync as the replication mechanism. One can envision a similar system where instead of using rsync, one
-can implement a custom solution to notify the slave of the changes and also provide an api to pull the change files.
-
-#### Concepts
-* file_store_dir: Root directory for the actual data files
-* change_log_dir: The transaction logs are generated under this folder
-* check_point_dir: The slave stores the check points ( last processed transaction) here
-
-#### Master
-* File server: This component supports file uploads and downloads and writes the files to ```file_store_dir```. This is not included in this application. The idea is that most applications have different ways of implementing this component and have some associated business logic. It is not hard to come up with such a component if needed.
-* File store watcher: This component watches the ```file_store_dir``` directory on the local file system for any changes and notifies the registered listeners of the changes
-* Change log generator: This registers as a listener of the file store watcher and on each notification logs the changes into a file under ```change_log_dir```
-
-#### Slave
-* File server: This component on the slave will only support reads
-* Cluster state observer: Slave observes the cluster state and is able to know who is the current master
-* Replicator: This has two subcomponents
- - Periodic rsync of change log: This is a background process that periodically rsyncs the ```change_log_dir``` of the master to its local directory
- - Change Log Watcher: This watches the ```change_log_dir``` for changes and notifies the registered listeners of the change
- - On demand rsync invoker: This is registered as a listener to change log watcher and on every change invokes rsync to sync only the changed file
-
-#### Coordination
-
-The coordination between nodes is done by Helix. Helix does the partition management and assigns the partition to multiple nodes based on the replication factor. It elects one the nodes as master and designates others as slaves.
-It provides notifications to each node in the form of state transitions (Offline to Slave, Slave to Master). It also provides notifications when there is change is cluster state.
-This allows the slave to stop replicating from current master and start replicating from new master.
-
-In this application, we have only one partition but its very easy to extend it to support multiple partitions. By partitioning the file store, one can add new nodes and Helix will automatically
-re-distribute partitions among the nodes. To summarize, Helix provides partition management, fault tolerance and facilitates automated cluster expansion.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/website/0.8.0/src/site/markdown/recipes/service_discovery.md b/website/0.8.0/src/site/markdown/recipes/service_discovery.md
deleted file mode 100644
index 634c682..0000000
--- a/website/0.8.0/src/site/markdown/recipes/service_discovery.md
+++ /dev/null
@@ -1,184 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-Service Discovery
------------------
-
-One of the common usage of ZooKeeper is to enable service discovery.
-The basic idea is that when a server starts up it advertises its configuration/metadata such as its hostname and port on ZooKeeper.
-This allows clients to dynamically discover the servers that are currently active. One can think of this like a service registry to which a server registers when it starts and
-is automatically deregistered when it shutdowns or crashes. In many cases it serves as an alternative to VIPs.
-
-The core idea behind this is to use ZooKeeper ephemeral nodes. The ephemeral nodes are created when the server registers and all its metadata is put into a ZNode.
-When the server shutdowns, ZooKeeper automatically removes this ZNode.
-
-There are two ways the clients can dynamically discover the active servers:
-
-### ZooKeeper Watch
-
-Clients can set a child watch under specific path on ZooKeeper.
-When a new service is registered/deregistered, ZooKeeper notifies the client via a watch event and the client can read the list of services. Even though this looks trivial,
-there are lot of things one needs to keep in mind like ensuring that you first set the watch back on ZooKeeper before reading data.
-
-
-### Poll
-
-Another approach is for the client to periodically read the ZooKeeper path and get the list of services.
-
-Both approaches have pros and cons, for example setting a watch might trigger herd effect if there are large number of clients. This is problematic, especially when servers are starting up.
-But the advantage to setting watches is that clients are immediately notified of a change which is not true in case of polling.
-In some cases, having both watches and polls makes sense; watch allows one to get notifications as soon as possible while poll provides a safety net if a watch event is missed because of code bug or ZooKeeper fails to notify.
-
-### Other Developer Considerations
-* What happens when the ZooKeeper session expires? All the watches and ephemeral nodes previously added or created by this server are lost. One needs to add the watches again, recreate the ephemeral nodes, and so on.
-* Due to network issues or Java GC pauses session expiry might happen again and again; this phenomenon is known as flapping. It\'s important for the server to detect this and deregister itself.
-
-### Other Operational Considerations
-* What if the node is behaving badly? One might kill the server, but it will lose the ability to debug. It would be nice to have the ability to mark a server as disabled and clients know that a node is disabled and will not contact that node.
-
-### Configuration Ownership
-
-This is an important aspect that is often ignored in the initial stages of your development. Typically, the service discovery pattern means that servers start up with some configuration which it simply puts into ZooKeeper. While this works well in the beginning, configuration management becomes very difficult since the servers themselves are statically configured. Any change in server configuration implies restarting the server. Ideally, it will be nice to have the ability to change conf [...]
-
-Ideally you want a hybrid solution, a node starts with minimal configuration and gets the rest of configuration from ZooKeeper.
-
-### Using Helix for Service Discovery
-
-Even though Helix has a higher-level abstraction in terms of state machines, constraints and objectives, service discovery is one of things has been a prevalent use case from the start.
-The controller uses the exact mechanism we described above to discover when new servers join the cluster. We create these ZNodes under /CLUSTERNAME/LIVEINSTANCES.
-Since at any time there is only one controller, we use a ZK watch to track the liveness of a server.
-
-This recipe simply demonstrates how one can re-use that part for implementing service discovery. This demonstrates multiple modes of service discovery:
-
-* POLL: The client reads from zookeeper at regular intervals 30 seconds. Use this if you have 100's of clients
-* WATCH: The client sets up watcher and gets notified of the changes. Use this if you have 10's of clients
-* NONE: This does neither of the above, but reads directly from zookeeper when ever needed
-
-Helix provides these additional features compared to other implementations available elsewhere:
-
-* It has the concept of disabling a node which means that a badly behaving node can be disabled using the Helix admin API
-* It automatically detects if a node connects/disconnects from zookeeper repeatedly and disables the node
-* Configuration management
- * Allows one to set configuration via the admin API at various granulaties like cluster, instance, resource, partition
- * Configurations can be dynamically changed
- * The server is notified when configurations change
-
-
-### Checkout and Build
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-mvn clean install package -DskipTests
-cd recipes/service-discovery/target/service-discovery-pkg/bin
-chmod +x *
-```
-
-### Start ZooKeeper
-
-```
-./start-standalone-zookeeper 2199
-```
-
-### Run the Demo
-
-```
-./service-discovery-demo.sh
-```
-
-### Output
-
-```
-START:Service discovery demo mode:WATCH
- Registering service
- host.x.y.z_12000
- host.x.y.z_12001
- host.x.y.z_12002
- host.x.y.z_12003
- host.x.y.z_12004
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12002
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Deregistering service:
- host.x.y.z_12002
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Registering service:host.x.y.z_12002
-END:Service discovery demo mode:WATCH
-=============================================
-START:Service discovery demo mode:POLL
- Registering service
- host.x.y.z_12000
- host.x.y.z_12001
- host.x.y.z_12002
- host.x.y.z_12003
- host.x.y.z_12004
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12002
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Deregistering service:
- host.x.y.z_12002
- Sleeping for poll interval:30000
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Registering service:host.x.y.z_12002
-END:Service discovery demo mode:POLL
-=============================================
-START:Service discovery demo mode:NONE
- Registering service
- host.x.y.z_12000
- host.x.y.z_12001
- host.x.y.z_12002
- host.x.y.z_12003
- host.x.y.z_12004
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12002
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Deregistering service:
- host.x.y.z_12000
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12002
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Registering service:host.x.y.z_12000
-END:Service discovery demo mode:NONE
-=============================================
-```
diff --git a/website/0.8.0/src/site/markdown/recipes/task_dag_execution.md b/website/0.8.0/src/site/markdown/recipes/task_dag_execution.md
deleted file mode 100644
index a081fe1..0000000
--- a/website/0.8.0/src/site/markdown/recipes/task_dag_execution.md
+++ /dev/null
@@ -1,199 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-Distributed Task Execution
---------------------------
-
-This recipe is intended to demonstrate how task dependencies can be modeled using primitives provided by Helix. A given task can be run with the desired amount of parallelism and will start only when upstream dependencies are met. The demo executes the task DAG described below using 10 workers. Although the demo starts the workers as threads, there is no requirement that all the workers need to run in the same process. In reality, these workers run on many different boxes on a cluster. [...]
-
-Redis is used as a result store. Any other suitable implementation for TaskResultStore can be plugged in.
-
-### Workflow
-
-#### Input
-
-10000 impression events and around 100 click events are pre-populated in task result store (redis).
-
-* **ImpEvent**: format: id,isFraudulent,country,gender
-
-* **ClickEvent**: format: id,isFraudulent,impEventId
-
-#### Stages
-
-+ **FilterImps**: Filters impression where isFraudulent=true.
-
-+ **FilterClicks**: Filters clicks where isFraudulent=true
-
-+ **impCountsByGender**: Generates impression counts grouped by gender. It does this by incrementing the count for 'impression_gender_counts:<gender_value>' in the task result store (redis hash). Depends on: **FilterImps**
-
-+ **impCountsByCountry**: Generates impression counts grouped by country. It does this by incrementing the count for 'impression_country_counts:<country_value>' in the task result store (redis hash). Depends on: **FilterClicks**
-
-+ **impClickJoin**: Joins clicks with corresponding impression event using impEventId as the join key. Join is needed to pull dimensions not present in click event. Depends on: **FilterImps, FilterClicks**
-
-+ **clickCountsByGender**: Generates click counts grouped by gender. It does this by incrementing the count for click_gender_counts:<gender_value> in the task result store (redis hash). Depends on: **impClickJoin**
-
-+ **clickCountsByGender**: Generates click counts grouped by country. It does this by incrementing the count for click_country_counts:<country_value> in the task result store (redis hash). Depends on: **impClickJoin**
-
-+ **report**: Reads from all aggregates generated by previous stages and prints them. Depends on: **impCountsByGender, impCountsByCountry, clickCountsByGender,clickCountsByGender**
-
-
-### Creating a DAG
-
-Each stage is represented as a Node along with the upstream dependency and desired parallelism. Each stage is modeled as a resource in Helix using OnlineOffline state model. As part of an Offline to Online transition, we watch the external view of upstream resources and wait for them to transition to the online state. See Task.java for additional info.
-
-```
-Dag dag = new Dag();
-dag.addNode(new Node("filterImps", 10, ""));
-dag.addNode(new Node("filterClicks", 5, ""));
-dag.addNode(new Node("impClickJoin", 10, "filterImps,filterClicks"));
-dag.addNode(new Node("impCountsByGender", 10, "filterImps"));
-dag.addNode(new Node("impCountsByCountry", 10, "filterImps"));
-dag.addNode(new Node("clickCountsByGender", 5, "impClickJoin"));
-dag.addNode(new Node("clickCountsByCountry", 5, "impClickJoin"));
-dag.addNode(new Node("report",1,"impCountsByGender,impCountsByCountry,clickCountsByGender,clickCountsByCountry"));
-```
-
-### Demo
-
-In order to run the demo, use the following steps
-
-See http://redis.io/topics/quickstart on how to install redis server
-
-```
-Start redis e.g:
-./redis-server --port 6379
-
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout helix-0.8.0
-cd recipes/task-execution
-mvn clean install package -DskipTests
-cd target/task-execution-pkg/bin
-chmod +x task-execution-demo.sh
-./task-execution-demo.sh 2181 localhost 6379
-
-```
-
-Here\'s a visual representation of the DAG.
-
-```
-
-
-
-
-
- +-----------------+ +----------------+
- | filterImps | | filterClicks |
- | (parallelism=10)| | (parallelism=5)|
- +----------+-----++ +-------+--------+
- | | | |
- | | | |
- | | | |
- | | +------->--------v------------+
- +--------------<-+ +------v-------+ | impClickJoin |
- |impCountsByGender |impCountsByCountry | (parallelism=10) |
- |(parallelism=10) |(parallelism=10) ++-------------------+-+
- +-----------+--+ +---+----------+ | |
- | | | |
- | | | |
- | | +--------v---------+ +-v-------------------+
- | | |clickCountsByGender |clickCountsByCountry |
- | | |(parallelism=5) | |(parallelism=5) |
- | | +----+-------------+ +---------------------+
- | | | |
- | | | |
- | | | |
- +----->+-----+>-----------v----+<---------------+
- | report |
- |(parallelism=1) |
- +-----------------------+
-
-```
-
-(credit for above ascii art: http://www.asciiflow.com)
-
-#### Output
-
-```
-Done populating dummy data
-Executing filter task for filterImps_3 for impressions_demo
-Executing filter task for filterImps_2 for impressions_demo
-Executing filter task for filterImps_0 for impressions_demo
-Executing filter task for filterImps_1 for impressions_demo
-Executing filter task for filterImps_4 for impressions_demo
-Executing filter task for filterClicks_3 for clicks_demo
-Executing filter task for filterClicks_1 for clicks_demo
-Executing filter task for filterImps_8 for impressions_demo
-Executing filter task for filterImps_6 for impressions_demo
-Executing filter task for filterClicks_2 for clicks_demo
-Executing filter task for filterClicks_0 for clicks_demo
-Executing filter task for filterImps_7 for impressions_demo
-Executing filter task for filterImps_5 for impressions_demo
-Executing filter task for filterClicks_4 for clicks_demo
-Executing filter task for filterImps_9 for impressions_demo
-Running AggTask for impCountsByGender_3 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_2 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_0 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_9 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_1 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_4 for filtered_impressions_demo gender
-Running AggTask for impCountsByCountry_4 for filtered_impressions_demo country
-Running AggTask for impCountsByGender_5 for filtered_impressions_demo gender
-Executing JoinTask for impClickJoin_2
-Running AggTask for impCountsByCountry_3 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_1 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_0 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_2 for filtered_impressions_demo country
-Running AggTask for impCountsByGender_6 for filtered_impressions_demo gender
-Executing JoinTask for impClickJoin_1
-Executing JoinTask for impClickJoin_0
-Executing JoinTask for impClickJoin_3
-Running AggTask for impCountsByGender_8 for filtered_impressions_demo gender
-Executing JoinTask for impClickJoin_4
-Running AggTask for impCountsByGender_7 for filtered_impressions_demo gender
-Running AggTask for impCountsByCountry_5 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_6 for filtered_impressions_demo country
-Executing JoinTask for impClickJoin_9
-Running AggTask for impCountsByCountry_8 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_7 for filtered_impressions_demo country
-Executing JoinTask for impClickJoin_5
-Executing JoinTask for impClickJoin_6
-Running AggTask for impCountsByCountry_9 for filtered_impressions_demo country
-Executing JoinTask for impClickJoin_8
-Executing JoinTask for impClickJoin_7
-Running AggTask for clickCountsByCountry_1 for joined_clicks_demo country
-Running AggTask for clickCountsByCountry_0 for joined_clicks_demo country
-Running AggTask for clickCountsByCountry_2 for joined_clicks_demo country
-Running AggTask for clickCountsByCountry_3 for joined_clicks_demo country
-Running AggTask for clickCountsByGender_1 for joined_clicks_demo gender
-Running AggTask for clickCountsByCountry_4 for joined_clicks_demo country
-Running AggTask for clickCountsByGender_3 for joined_clicks_demo gender
-Running AggTask for clickCountsByGender_2 for joined_clicks_demo gender
-Running AggTask for clickCountsByGender_4 for joined_clicks_demo gender
-Running AggTask for clickCountsByGender_0 for joined_clicks_demo gender
-Running reports task
-Impression counts per country
-{CANADA=1940, US=1958, CHINA=2014, UNKNOWN=2022, UK=1946}
-Click counts per country
-{US=24, CANADA=14, CHINA=26, UNKNOWN=14, UK=22}
-Impression counts per gender
-{F=3325, UNKNOWN=3259, M=3296}
-Click counts per gender
-{F=33, UNKNOWN=32, M=35}
-```
diff --git a/website/0.8.0/src/site/markdown/tutorial_admin.md b/website/0.8.0/src/site/markdown/tutorial_admin.md
deleted file mode 100644
index 8f44074..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_admin.md
+++ /dev/null
@@ -1,408 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Admin Operations</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Admin Operations
-
-Helix provides a set of admin APIs for cluster management operations. They are supported via:
-
-* Java API
-* Command Line Interface
-* REST Interface via helix-admin-webapp
-
-### Java API
-See interface [_org.apache.helix.HelixAdmin_](http://helix.apache.org/javadocs/0.8.0/reference/org/apache/helix/HelixAdmin.html)
-
-### Command Line Interface
-The command line tool comes with helix-core package:
-
-Get the command line tool:
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-./build
-cd helix-core/target/helix-core-pkg/bin
-chmod +x *.sh
-```
-
-Get help:
-
-```
-./helix-admin.sh --help
-```
-
-All other commands have this form:
-
-```
-./helix-admin.sh --zkSvr <ZookeeperServerAddress> <command> <parameters>
-```
-
-#### Supported Commands
-
-| Command Syntax | Description |
-| -------------- | ----------- |
-| _\-\-activateCluster \<clusterName controllerCluster true/false\>_ | Enable/disable a cluster in distributed controller mode |
-| _\-\-addCluster \<clusterName\>_ | Add a new cluster |
-| _\-\-addIdealState \<clusterName resourceName fileName.json\>_ | Add an ideal state to a cluster |
-| _\-\-addInstanceTag \<clusterName instanceName tag\>_ | Add a tag to an instance |
-| _\-\-addNode \<clusterName instanceId\>_ | Add an instance to a cluster |
-| _\-\-addResource \<clusterName resourceName partitionNumber stateModelName\>_ | Add a new resource to a cluster |
-| _\-\-addResourceProperty \<clusterName resourceName propertyName propertyValue\>_ | Add a resource property |
-| _\-\-addStateModelDef \<clusterName fileName.json\>_ | Add a State model definition to a cluster |
-| _\-\-dropCluster \<clusterName\>_ | Delete a cluster |
-| _\-\-dropNode \<clusterName instanceId\>_ | Remove a node from a cluster |
-| _\-\-dropResource \<clusterName resourceName\>_ | Remove an existing resource from a cluster |
-| _\-\-enableCluster \<clusterName true/false\>_ | Enable/disable a cluster |
-| _\-\-enableInstance \<clusterName instanceId true/false\>_ | Enable/disable an instance |
-| _\-\-enablePartition \<true/false clusterName nodeId resourceName partitionName\>_ | Enable/disable a partition |
-| _\-\-getConfig \<configScope configScopeArgs configKeys\>_ | Get user configs |
-| _\-\-getConstraints \<clusterName constraintType\>_ | Get constraints |
-| _\-\-help_ | print help information |
-| _\-\-instanceGroupTag \<instanceTag\>_ | Specify instance group tag, used with rebalance command |
-| _\-\-listClusterInfo \<clusterName\>_ | Show information of a cluster |
-| _\-\-listClusters_ | List all clusters |
-| _\-\-listInstanceInfo \<clusterName instanceId\>_ | Show information of an instance |
-| _\-\-listInstances \<clusterName\>_ | List all instances in a cluster |
-| _\-\-listPartitionInfo \<clusterName resourceName partitionName\>_ | Show information of a partition |
-| _\-\-listResourceInfo \<clusterName resourceName\>_ | Show information of a resource |
-| _\-\-listResources \<clusterName\>_ | List all resources in a cluster |
-| _\-\-listStateModel \<clusterName stateModelName\>_ | Show information of a state model |
-| _\-\-listStateModels \<clusterName\>_ | List all state models in a cluster |
-| _\-\-maxPartitionsPerNode \<maxPartitionsPerNode\>_ | Specify the max partitions per instance, used with addResourceGroup command |
-| _\-\-rebalance \<clusterName resourceName replicas\>_ | Rebalance a resource |
-| _\-\-removeConfig \<configScope configScopeArgs configKeys\>_ | Remove user configs |
-| _\-\-removeConstraint \<clusterName constraintType constraintId\>_ | Remove a constraint |
-| _\-\-removeInstanceTag \<clusterName instanceId tag\>_ | Remove a tag from an instance |
-| _\-\-removeResourceProperty \<clusterName resourceName propertyName\>_ | Remove a resource property |
-| _\-\-resetInstance \<clusterName instanceId\>_ | Reset all erroneous partitions on an instance |
-| _\-\-resetPartition \<clusterName instanceId resourceName partitionName\>_ | Reset an erroneous partition |
-| _\-\-resetResource \<clusterName resourceName\>_ | Reset all erroneous partitions of a resource |
-| _\-\-setConfig \<configScope configScopeArgs configKeyValueMap\>_ | Set user configs |
-| _\-\-setConstraint \<clusterName constraintType constraintId constraintKeyValueMap\>_ | Set a constraint |
-| _\-\-swapInstance \<clusterName oldInstance newInstance\>_ | Swap an old instance with a new instance |
-| _\-\-zkSvr \<ZookeeperServerAddress\>_ | Provide zookeeper address |
-
-### REST Interface
-
-The REST interface comes wit helix-admin-webapp package:
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-./build
-cd helix-admin-webapp/target/helix-admin-webapp-pkg/bin
-chmod +x *.sh
-./run-rest-admin.sh --zkSvr <zookeeperAddress> --port <port> // make sure ZooKeeper is running
-```
-
-#### URL and support methods
-
-* _/clusters_
- * List all clusters
-
- ```
- curl http://localhost:8100/clusters
- ```
-
- * Add a cluster
-
- ```
- curl -d 'jsonParameters={"command":"addCluster","clusterName":"MyCluster"}' -H "Content-Type: application/json" http://localhost:8100/clusters
- ```
-
-* _/clusters/{clusterName}_
- * List cluster information
-
- ```
- curl http://localhost:8100/clusters/MyCluster
- ```
-
- * Enable/disable a cluster in distributed controller mode
-
- ```
- curl -d 'jsonParameters={"command":"activateCluster","grandCluster":"MyControllerCluster","enabled":"true"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster
- ```
-
- * Remove a cluster
-
- ```
- curl -X DELETE http://localhost:8100/clusters/MyCluster
- ```
-
-* _/clusters/{clusterName}/resourceGroups_
- * List all resources in a cluster
-
- ```
- curl http://localhost:8100/clusters/MyCluster/resourceGroups
- ```
-
- * Add a resource to cluster
-
- ```
- curl -d 'jsonParameters={"command":"addResource","resourceGroupName":"MyDB","partitions":"8","stateModelDefRef":"MasterSlave" }' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/resourceGroups
- ```
-
-* _/clusters/{clusterName}/resourceGroups/{resourceName}_
- * List resource information
-
- ```
- curl http://localhost:8100/clusters/MyCluster/resourceGroups/MyDB
- ```
-
- * Drop a resource
-
- ```
- curl -X DELETE http://localhost:8100/clusters/MyCluster/resourceGroups/MyDB
- ```
-
- * Reset all erroneous partitions of a resource
-
- ```
- curl -d 'jsonParameters={"command":"resetResource"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/resourceGroups/MyDB
- ```
-
-* _/clusters/{clusterName}/resourceGroups/{resourceName}/idealState_
- * Rebalance a resource
-
- ```
- curl -d 'jsonParameters={"command":"rebalance","replicas":"3"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/resourceGroups/MyDB/idealState
- ```
-
- * Add an ideal state
-
- ```
- echo jsonParameters={
- "command":"addIdealState"
- }&newIdealState={
- "id" : "MyDB",
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "NUM_PARTITIONS" : "8",
- "REBALANCE_MODE" : "SEMI_AUTO",
- "REPLICAS" : "0",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- "STATE_MODEL_FACTORY_NAME" : "DEFAULT"
- },
- "listFields" : {
- },
- "mapFields" : {
- "MyDB_0" : {
- "localhost_1001" : "MASTER",
- "localhost_1002" : "SLAVE"
- }
- }
- }
- > newIdealState.json
- curl -d @'./newIdealState.json' -H 'Content-Type: application/json' http://localhost:8100/clusters/MyCluster/resourceGroups/MyDB/idealState
- ```
-
- * Add resource property
-
- ```
- curl -d 'jsonParameters={"command":"addResourceProperty","REBALANCE_TIMER_PERIOD":"500"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/resourceGroups/MyDB/idealState
- ```
-
-* _/clusters/{clusterName}/resourceGroups/{resourceName}/externalView_
- * Show resource external view
-
- ```
- curl http://localhost:8100/clusters/MyCluster/resourceGroups/MyDB/externalView
- ```
-* _/clusters/{clusterName}/instances_
- * List all instances
-
- ```
- curl http://localhost:8100/clusters/MyCluster/instances
- ```
-
- * Add an instance
-
- ```
- curl -d 'jsonParameters={"command":"addInstance","instanceNames":"localhost_1001"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/instances
- ```
-
- * Swap an instance
-
- ```
- curl -d 'jsonParameters={"command":"swapInstance","oldInstance":"localhost_1001", "newInstance":"localhost_1002"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/instances
- ```
-* _/clusters/{clusterName}/instances/{instanceName}_
- * Show instance information
-
- ```
- curl http://localhost:8100/clusters/MyCluster/instances/localhost_1001
- ```
-
- * Enable/disable an instance
-
- ```
- curl -d 'jsonParameters={"command":"enableInstance","enabled":"false"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/instances/localhost_1001
- ```
-
- * Drop an instance
-
- ```
- curl -X DELETE http://localhost:8100/clusters/MyCluster/instances/localhost_1001
- ```
-
- * Disable/enable partitions on an instance
-
- ```
- curl -d 'jsonParameters={"command":"enablePartition","resource": "MyDB","partition":"MyDB_0", "enabled" : "false"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/instances/localhost_1001
- ```
-
- * Reset an erroneous partition on an instance
-
- ```
- curl -d 'jsonParameters={"command":"resetPartition","resource": "MyDB","partition":"MyDB_0"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/instances/localhost_1001
- ```
-
- * Reset all erroneous partitions on an instance
-
- ```
- curl -d 'jsonParameters={"command":"resetInstance"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/instances/localhost_1001
- ```
-
-* _/clusters/{clusterName}/configs_
- * Get user cluster level config
-
- ```
- curl http://localhost:8100/clusters/MyCluster/configs/cluster
- ```
-
- * Set user cluster level config
-
- ```
- curl -d 'jsonParameters={"command":"setConfig","configs":"key1=value1,key2=value2"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/configs/cluster
- ```
-
- * Remove user cluster level config
-
- ```
- curl -d 'jsonParameters={"command":"removeConfig","configs":"key1,key2"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/configs/cluster
- ```
-
- * Get/set/remove user participant level config
-
- ```
- curl -d 'jsonParameters={"command":"setConfig","configs":"key1=value1,key2=value2"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/configs/participant/localhost_1001
- ```
-
- * Get/set/remove resource level config
-
- ```
- curl -d 'jsonParameters={"command":"setConfig","configs":"key1=value1,key2=value2"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/configs/resource/MyDB
- ```
-
-* _/clusters/{clusterName}/controller_
- * Show controller information
-
- ```
- curl http://localhost:8100/clusters/MyCluster/Controller
- ```
-
- * Enable/disable cluster
-
- ```
- curl -d 'jsonParameters={"command":"enableCluster","enabled":"false"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/Controller
- ```
-
-* _/zkPath/{path}_
- * Get information for zookeeper path
-
- ```
- curl http://localhost:8100/zkPath/MyCluster
- ```
-
-* _/clusters/{clusterName}/StateModelDefs_
- * Show all state model definitions
-
- ```
- curl http://localhost:8100/clusters/MyCluster/StateModelDefs
- ```
-
- * Add a state mdoel definition
-
- ```
- echo jsonParameters={
- "command":"addStateModelDef"
- }&newStateModelDef={
- "id" : "OnlineOffline",
- "simpleFields" : {
- "INITIAL_STATE" : "OFFLINE"
- },
- "listFields" : {
- "STATE_PRIORITY_LIST" : [ "ONLINE", "OFFLINE", "DROPPED" ],
- "STATE_TRANSITION_PRIORITYLIST" : [ "OFFLINE-ONLINE", "ONLINE-OFFLINE", "OFFLINE-DROPPED" ]
- },
- "mapFields" : {
- "DROPPED.meta" : {
- "count" : "-1"
- },
- "OFFLINE.meta" : {
- "count" : "-1"
- },
- "OFFLINE.next" : {
- "DROPPED" : "DROPPED",
- "ONLINE" : "ONLINE"
- },
- "ONLINE.meta" : {
- "count" : "R"
- },
- "ONLINE.next" : {
- "DROPPED" : "OFFLINE",
- "OFFLINE" : "OFFLINE"
- }
- }
- }
- > newStateModelDef.json
- curl -d @'./untitled.txt' -H 'Content-Type: application/json' http://localhost:8100/clusters/MyCluster/StateModelDefs
- ```
-
-* _/clusters/{clusterName}/StateModelDefs/{stateModelDefName}_
- * Show a state model definition
-
- ```
- curl http://localhost:8100/clusters/MyCluster/StateModelDefs/OnlineOffline
- ```
-
-* _/clusters/{clusterName}/constraints/{constraintType}_
- * Show all contraints
-
- ```
- curl http://localhost:8100/clusters/MyCluster/constraints/MESSAGE_CONSTRAINT
- ```
-
- * Set a contraint
-
- ```
- curl -d 'jsonParameters={"constraintAttributes":"RESOURCE=MyDB,CONSTRAINT_VALUE=1"}' -H "Content-Type: application/json" http://localhost:8100/clusters/MyCluster/constraints/MESSAGE_CONSTRAINT/MyConstraint
- ```
-
- * Remove a constraint
-
- ```
- curl -X DELETE http://localhost:8100/clusters/MyCluster/constraints/MESSAGE_CONSTRAINT/MyConstraint
- ```
diff --git a/website/0.8.0/src/site/markdown/tutorial_agent.md b/website/0.8.0/src/site/markdown/tutorial_agent.md
deleted file mode 100644
index 235d71d..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_agent.md
+++ /dev/null
@@ -1,169 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Helix Agent</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Helix Agent (for non-JVM systems)
-
-Not every distributed system is written on the JVM, but many systems would benefit from the cluster management features that Helix provides. To make a non-JVM system work with Helix, you can use the Helix Agent module.
-
-### What is Helix Agent?
-
-Helix is built on the following assumption: if your distributed resource is modeled by a finite state machine, then Helix can tell participants when they should transition between states. In the Java API, this means implementing transition callbacks. In the Helix agent API, this means providing commands than can run for each transition.
-
-These commands could do anything behind the scenes; Helix only requires that they exit once the state transition is complete.
-
-### Configuring Transition Commands
-
-Here's how to tell Helix which commands to run on state transitions:
-
-#### Java
-
-Using the Java API, first get a configuration scope (the Helix agent supports both cluster and resource scopes, picking resource first if it is available):
-
-```
-// Cluster scope
-HelixConfigScope scope =
- new HelixConfigScopeBuilder(ConfigScopeProperty.CLUSTER).forCluster(clusterName).build();
-
-// Resource scope
-HelixConfigScope scope =
- new HelixConfigScopeBuilder(ConfigScopeProperty.RESOURCE).forCluster(clusterName).forResource(resourceName).build();
-```
-
-Then, specify the command to run for each state transition:
-
-```
-// Get the configuration accessor
-ConfigAccessor configAccessor = new ConfigAccessor(_gZkClient);
-
-// Specify the script for OFFLINE --> ONLINE
-CommandConfig.Builder builder = new CommandConfig.Builder();
-CommandConfig cmdConfig =
- builder.setTransition("OFFLINE", "ONLINE").setCommand("simpleHttpClient.py OFFLINE-ONLINE")
- .setCommandWorkingDir(workingDir)
- .setCommandTimeout("5000L") // optional: ms to wait before failing
- .setPidFile(pidFile) // optional: for daemon-like systems that will write the process id to a file
- .build();
-configAccessor.set(scope, cmdConfig.toKeyValueMap());
-
-// Specify the script for ONLINE --> OFFLINE
-builder = new CommandConfig.Builder();
-cmdConfig =
- builder.setTransition("ONLINE", "OFFLINE").setCommand("simpleHttpClient.py ONLINE-OFFLINE")
- .setCommandWorkingDir(workingDir)
- .build();
-configAccessor.set(scope, cmdConfig.toKeyValueMap());
-
-// Specify NOP for OFFLINE --> DROPPED
-builder = new CommandConfig.Builder();
-cmdConfig =
- builder.setTransition("OFFLINE", "DROPPED")
- .setCommand(CommandAttribute.NOP.getName())
- .build();
-configAccessor.set(scope, cmdConfig.toKeyValueMap());
-```
-
-In this example, we have a program called simpleHttpClient.py that we call for all transitions, only changing the arguments that are passed in. However, there is no requirement that each transition invoke the same program; this API allows running arbitrary commands in arbitrary directories with arbitrary arguments.
-
-Notice that that for the OFFLINE \-\-\> DROPPED transition, we do not run any command (specifically, we specify the NOP command). This just tells Helix that the system doesn't care about when things are dropped, and it can consider the transition already done.
-
-#### Command Line
-
-It is also possible to configure everything directly from the command line. Here's how that would look for cluster-wide configuration:
-
-```
-# Specify the script for OFFLINE --> ONLINE
-/helix-admin.sh --zkSvr localhost:2181 --setConfig CLUSTER clusterName OFFLINE-ONLINE.command="simpleHttpClient.py OFFLINE-ONLINE",OFFLINE-ONLINE.workingDir="/path/to/script", OFFLINE-ONLINE.command.pidfile="/path/to/pidfile"
-
-# Specify the script for ONLINE --> OFFLINE
-/helix-admin.sh --zkSvr localhost:2181 --setConfig CLUSTER clusterName ONLINE-OFFLINE.command="simpleHttpClient.py ONLINE-OFFLINE",ONLINE-OFFLINE.workingDir="/path/to/script", OFFLINE-ONLINE.command.pidfile="/path/to/pidfile"
-
-# Specify NOP for OFFLINE --> DROPPED
-/helix-admin.sh --zkSvr localhost:2181 --setConfig CLUSTER clusterName ONLINE-OFFLINE.command="nop"
-```
-
-Like in the Java configuration, it is also possible to specify a resource scope instead of a cluster scope:
-
-```
-# Specify the script for OFFLINE --> ONLINE
-/helix-admin.sh --zkSvr localhost:2181 --setConfig RESOURCE clusterName,resourceName OFFLINE-ONLINE.command="simpleHttpClient.py OFFLINE-ONLINE",OFFLINE-ONLINE.workingDir="/path/to/script", OFFLINE-ONLINE.command.pidfile="/path/to/pidfile"
-```
-
-### Starting the Agent
-
-There should be an agent running for every participant you have running. Ideally, its lifecycle should match that of the participant. Here, we have a simple long-running participant called simpleHttpServer.py. Its only purpose is to record state transitions.
-
-Here are some ways that you can start the Helix agent:
-
-#### Java
-
-```
-// Start your application process
-ExternalCommand serverCmd = ExternalCommand.start(workingDir + "/simpleHttpServer.py");
-
-// Start the agent
-Thread agentThread = new Thread() {
- @Override
- public void run() {
- while(!isInterrupted()) {
- try {
- HelixAgentMain.main(new String[] {
- "--zkSvr", zkAddr, "--cluster", clusterName, "--instanceName", instanceName,
- "--stateModel", "OnlineOffline"
- });
- } catch (InterruptedException e) {
- LOG.info("Agent thread interrupted", e);
- interrupt();
- } catch (Exception e) {
- LOG.error("Exception start helix-agent", e);
- }
- }
- }
-};
-agentThread.start();
-
-// Wait for the process to terminate (either intentionally or unintentionally)
-serverCmd.waitFor();
-
-// Kill the agent
-agentThread.interrupt();
-```
-
-#### Command Line
-
-```
-# Build Helix and start the agent
-mvn clean install -DskipTests
-chmod +x helix-agent/target/helix-agent-pkg/bin/*
-helix-agent/target/helix-agent-pkg/bin/start-helix-agent.sh --zkSvr zkAddr1,zkAddr2 --cluster clusterName --instanceName instanceName --stateModel OnlineOffline
-
-# Here, you can define your own logic to terminate this agent when your process terminates
-...
-```
-
-### Example
-
-[Here](https://git-wip-us.apache.org/repos/asf?p=helix.git;a=blob;f=helix-agent/src/test/java/org/apache/helix/agent/TestHelixAgent.java;h=ccf64ce5544207c7e48261682ea69945b71da7f1;hb=refs/heads/master) is a basic system that uses the Helix agent package.
-
-### Notes
-
-As you may have noticed from the examples, the participant program and the state transition program are two different programs. The former is a _long-running_ process that is directly tied to the Helix agent. The latter is a process that only exists while a state transition is underway. Despite this, these two processes should be intertwined. The transition command will need to communicate to the participant to actually complete the state transition and the participant will need to commu [...]
\ No newline at end of file
diff --git a/website/0.8.0/src/site/markdown/tutorial_controller.md b/website/0.8.0/src/site/markdown/tutorial_controller.md
deleted file mode 100644
index d3c5526..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_controller.md
+++ /dev/null
@@ -1,153 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Controller</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Controller
-
-Next, let\'s implement the controller. This is the brain of the cluster. Helix makes sure there is exactly one active controller running the cluster.
-
-### Start a Connection
-
-The Helix manager requires the following parameters:
-
-* clusterName: A logical name to represent the group of nodes
-* instanceName: A logical name of the process creating the manager instance. Generally this is host:port
-* instanceType: Type of the process. This can be one of the following types, in this case use CONTROLLER:
- * CONTROLLER: Process that controls the cluster, any number of controllers can be started but only one will be active at any given time
- * PARTICIPANT: Process that performs the actual task in the distributed system
- * SPECTATOR: Process that observes the changes in the cluster
- * ADMIN: To carry out system admin actions
-* zkConnectString: Connection string to ZooKeeper. This is of the form host1:port1,host2:port2,host3:port3
-
-```
-manager = HelixManagerFactory.getZKHelixManager(clusterName,
- instanceName,
- instanceType,
- zkConnectString);
-```
-
-### Controller Code
-
-The Controller needs to know about all changes in the cluster. Helix takes care of this with the default implementation.
-If you need additional functionality, see GenericHelixController on how to configure the pipeline.
-
-```
-manager = HelixManagerFactory.getZKHelixManager(clusterName,
- instanceName,
- InstanceType.CONTROLLER,
- zkConnectString);
-manager.connect();
-```
-The snippet above shows how the controller is started. You can also start the controller using command line interface.
-
-```
-cd helix/helix-core/target/helix-core-pkg/bin
-./run-helix-controller.sh --zkSvr <Zookeeper ServerAddress (Required)> --cluster <Cluster name (Required)>
-```
-
-### Controller Deployment Modes
-
-Helix provides multiple options to deploy the controller.
-
-#### STANDALONE
-
-The Controller can be started as a separate process to manage a cluster. This is the recommended approach. However, since one controller can be a single point of failure, multiple controller processes are required for reliability. Even if multiple controllers are running, only one will be actively managing the cluster at any time and is decided by a leader-election process. If the leader fails, another leader will take over managing the cluster.
-
-Even though we recommend this method of deployment, it has the drawback of having to manage an additional service for each cluster. See the Controller as a Service option.
-
-#### EMBEDDED
-
-If setting up a separate controller process is not viable, then it is possible to embed the controller as a library in each of the participants.
-
-#### CONTROLLER AS A SERVICE
-
-One of the cool features we added in Helix was to use a set of controllers to manage a large number of clusters.
-
-For example if you have X clusters to be managed, instead of deploying X*3 (3 controllers for fault tolerance) controllers for each cluster, one can deploy just 3 controllers. Each controller can manage X/3 clusters. If any controller fails, the remaining two will manage X/2 clusters.
-
-Next, let\'s implement the controller. This is the brain of the cluster. Helix makes sure there is exactly one active controller running the cluster.
-
-### Start the Helix agent
-
-
-It requires the following parameters:
-
-* clusterName: A logical name to represent the group of nodes
-* instanceName: A logical name of the process creating the manager instance. Generally this is host:port.
-* instanceType: Type of the process. This can be one of the following types, in this case use CONTROLLER:
- * CONTROLLER: Process that controls the cluster, any number of controllers can be started but only one will be active at any given time.
- * PARTICIPANT: Process that performs the actual task in the distributed system.
- * SPECTATOR: Process that observes the changes in the cluster.
- * ADMIN: To carry out system admin actions.
-* zkConnectString: Connection string to Zookeeper. This is of the form host1:port1,host2:port2,host3:port3.
-
-```
- manager = HelixManagerFactory.getZKHelixManager(clusterName,
- instanceName,
- instanceType,
- zkConnectString);
-```
-
-### Controller Code
-
-The Controller needs to know about all changes in the cluster. Helix takes care of this with the default implementation.
-If you need additional functionality, see GenericHelixController on how to configure the pipeline.
-
-```
- manager = HelixManagerFactory.getZKHelixManager(clusterName,
- instanceName,
- InstanceType.CONTROLLER,
- zkConnectString);
- manager.connect();
- GenericHelixController controller = new GenericHelixController();
- manager.addConfigChangeListener(controller);
- manager.addLiveInstanceChangeListener(controller);
- manager.addIdealStateChangeListener(controller);
- manager.addExternalViewChangeListener(controller);
- manager.addControllerListener(controller);
-```
-The snippet above shows how the controller is started. You can also start the controller using command line interface.
-
-```
-cd helix/helix-core/target/helix-core-pkg/bin
-./run-helix-controller.sh --zkSvr <Zookeeper ServerAddress (Required)> --cluster <Cluster name (Required)>
-```
-
-### Controller Deployment Modes
-
-Helix provides multiple options to deploy the controller.
-
-#### STANDALONE
-
-The Controller can be started as a separate process to manage a cluster. This is the recommended approach. However, since one controller can be a single point of failure, multiple controller processes are required for reliability. Even if multiple controllers are running, only one will be actively managing the cluster at any time and is decided by a leader-election process. If the leader fails, another leader will take over managing the cluster.
-
-Even though we recommend this method of deployment, it has the drawback of having to manage an additional service for each cluster. See Controller As a Service option.
-
-#### EMBEDDED
-
-If setting up a separate controller process is not viable, then it is possible to embed the controller as a library in each of the participants.
-
-#### CONTROLLER AS A SERVICE
-
-One of the cool features we added in Helix is to use a set of controllers to manage a large number of clusters.
-
-For example if you have X clusters to be managed, instead of deploying X*3 (3 controllers for fault tolerance) controllers for each cluster, one can deploy just 3 controllers. Each controller can manage X/3 clusters. If any controller fails, the remaining two will manage X/2 clusters.
diff --git a/website/0.8.0/src/site/markdown/tutorial_health.md b/website/0.8.0/src/site/markdown/tutorial_health.md
deleted file mode 100644
index 03b1dcc..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_health.md
+++ /dev/null
@@ -1,46 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Customizing Heath Checks</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Customizing Health Checks
-
-In this chapter, we\'ll learn how to customize health checks based on metrics of your distributed system.
-
-### Health Checks
-
-Note: _this in currently in development mode, not yet ready for production._
-
-Helix provides the ability for each node in the system to report health metrics on a periodic basis.
-
-Helix supports multiple ways to aggregate these metrics:
-
-* SUM
-* AVG
-* EXPONENTIAL DECAY
-* WINDOW
-
-Helix persists the aggregated value only.
-
-Applications can define a threshold on the aggregate values according to the SLAs, and when the SLA is violated Helix will fire an alert.
-Currently Helix only fires an alert, but in a future release we plan to use these metrics to either mark the node dead or load balance the partitions.
-This feature will be valuable for distributed systems that support multi-tenancy and have a large variation in work load patterns. In addition, this can be used to detect skewed partitions (hotspots) and rebalance the cluster.
-
diff --git a/website/0.8.0/src/site/markdown/tutorial_messaging.md b/website/0.8.0/src/site/markdown/tutorial_messaging.md
deleted file mode 100644
index ae5d0f8..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_messaging.md
+++ /dev/null
@@ -1,70 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Messaging</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Messaging
-
-In this chapter, we\'ll learn about messaging, a convenient feature in Helix for sending messages between nodes of a cluster. This is an interesting feature that is quite useful in practice. It is common that nodes in a distributed system require a mechanism to interact with each other.
-
-### Example: Bootstrapping a Replica
-
-Consider a search system where the index replica starts up and it does not have an index. A typical solution is to get the index from a common location, or to copy the index from another replica.
-
-Helix provides a messaging API for intra-cluster communication between nodes in the system. This API provides a mechanism to specify the message recipient in terms of resource, partition, and state rather than specifying hostnames. Helix ensures that the message is delivered to all of the required recipients. In this particular use case, the instance can specify the recipient criteria as all replicas of the desired partition to bootstrap.
-Since Helix is aware of the global state of the system, it can send the message to the appropriate nodes. Once the nodes respond, Helix provides the bootstrapping replica with all the responses.
-
-This is a very generic API and can also be used to schedule various periodic tasks in the cluster, such as data backups, log cleanup, etc.
-System Admins can also perform ad-hoc tasks, such as on-demand backups or a system command (such as rm -rf ;) across all nodes of the cluster
-
-```
-ClusterMessagingService messagingService = manager.getMessagingService();
-
-// Construct the Message
-Message requestBackupUriRequest = new Message(
- MessageType.USER_DEFINE_MSG, UUID.randomUUID().toString());
-requestBackupUriRequest
- .setMsgSubType(BootstrapProcess.REQUEST_BOOTSTRAP_URL);
-requestBackupUriRequest.setMsgState(MessageState.NEW);
-
-// Set the Recipient criteria: all nodes that satisfy the criteria will receive the message
-Criteria recipientCriteria = new Criteria();
-recipientCriteria.setInstanceName("%");
-recipientCriteria.setRecipientInstanceType(InstanceType.PARTICIPANT);
-recipientCriteria.setResource("MyDB");
-recipientCriteria.setPartition("");
-
-// Should be processed only by process(es) that are active at the time of sending the message
-// This means if the recipient is restarted after message is sent, it will not be processe.
-recipientCriteria.setSessionSpecific(true);
-
-// wait for 30 seconds
-int timeout = 30000;
-
-// the handler that will be invoked when any recipient responds to the message.
-BootstrapReplyHandler responseHandler = new BootstrapReplyHandler();
-
-// this will return only after all recipients respond or after timeout
-int sentMessageCount = messagingService.sendAndWait(recipientCriteria,
- requestBackupUriRequest, responseHandler, timeout);
-```
-
-See HelixManager.DefaultMessagingService in the [Javadocs](http://helix.apache.org/javadocs/0.8.0/reference/org/apache/helix/messaging/DefaultMessagingService.html) for more information.
diff --git a/website/0.8.0/src/site/markdown/tutorial_participant.md b/website/0.8.0/src/site/markdown/tutorial_participant.md
deleted file mode 100644
index cb38e45..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_participant.md
+++ /dev/null
@@ -1,102 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Participant</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Participant
-
-In this chapter, we\'ll learn how to implement a __Participant__, which is a primary functional component of a distributed system.
-
-
-### Start a Connection
-
-The Helix manager is a common component that connects each system component with the controller.
-
-It requires the following parameters:
-
-* clusterName: A logical name to represent the group of nodes
-* instanceName: A logical name of the process creating the manager instance. Generally this is host:port
-* instanceType: Type of the process. This can be one of the following types, in this case, use PARTICIPANT
- * CONTROLLER: Process that controls the cluster, any number of controllers can be started but only one will be active at any given time
- * PARTICIPANT: Process that performs the actual task in the distributed system
- * SPECTATOR: Process that observes the changes in the cluster
- * ADMIN: To carry out system admin actions
-* zkConnectString: Connection string to ZooKeeper. This is of the form host1:port1,host2:port2,host3:port3
-
-After the Helix manager instance is created, the only thing that needs to be registered is the state model factory.
-The methods of the state model will be called when controller sends transitions to the participant. In this example, we'll use the OnlineOffline factory. Other options include:
-
-* MasterSlaveStateModelFactory
-* LeaderStandbyStateModelFactory
-* BootstrapHandler
-
-
-```
-manager = HelixManagerFactory.getZKHelixManager(clusterName,
- instanceName,
- InstanceType.PARTICIPANT,
- zkConnectString);
-StateMachineEngine stateMach = manager.getStateMachineEngine();
-
-//create a stateModelFactory that returns a statemodel object for each partition.
-stateModelFactory = new OnlineOfflineStateModelFactory();
-stateMach.registerStateModelFactory(stateModelType, stateModelFactory);
-manager.connect();
-```
-
-### Example State Model Factory
-
-Helix doesn\'t know what it means to change from OFFLINE\-\-\>ONLINE or ONLINE\-\-\>OFFLINE. The following code snippet shows where you insert your system logic for these two state transitions.
-
-```
-public class OnlineOfflineStateModelFactory extends
- StateModelFactory<StateModel> {
- @Override
- public StateModel createNewStateModel(String stateUnitKey) {
- OnlineOfflineStateModel stateModel = new OnlineOfflineStateModel();
- return stateModel;
- }
- @StateModelInfo(states = "{'OFFLINE','ONLINE'}", initialState = "OFFINE")
- public static class OnlineOfflineStateModel extends StateModel {
- @Transition(from = "OFFLINE", to = "ONLINE")
- public void onBecomeOnlineFromOffline(Message message,
- NotificationContext context) {
- System.out.println("OnlineOfflineStateModel.onBecomeOnlineFromOffline()");
-
- ////////////////////////////////////////////////////////////////////////////////////////////////
- // Application logic to handle transition //
- // For example, you might start a service, run initialization, etc //
- ////////////////////////////////////////////////////////////////////////////////////////////////
- }
-
- @Transition(from = "ONLINE", to = "OFFLINE")
- public void onBecomeOfflineFromOnline(Message message,
- NotificationContext context) {
- System.out.println("OnlineOfflineStateModel.onBecomeOfflineFromOnline()");
-
- ////////////////////////////////////////////////////////////////////////////////////////////////
- // Application logic to handle transition //
- // For example, you might shutdown a service, log this event, or change monitoring settings //
- ////////////////////////////////////////////////////////////////////////////////////////////////
- }
- }
-}
-```
diff --git a/website/0.8.0/src/site/markdown/tutorial_propstore.md b/website/0.8.0/src/site/markdown/tutorial_propstore.md
deleted file mode 100644
index 6639cf1..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_propstore.md
+++ /dev/null
@@ -1,34 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Application Property Store</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Application Property Store
-
-In this chapter, we\'ll learn how to use the application property store.
-
-### Property Store
-
-It is common that an application needs support for distributed, shared data structures. Helix uses ZooKeeper to store the application data and hence provides notifications when the data changes.
-
-While you could use ZooKeeper directly, Helix supports caching the data with a write-through cache. This is far more efficient than reading from ZooKeeper for every access.
-
-See [HelixManager.getHelixPropertyStore](http://helix.apache.org/javadocs/0.8.0/reference/org/apache/helix/store/package-summary.html) for details.
diff --git a/website/0.8.0/src/site/markdown/tutorial_rebalance.md b/website/0.8.0/src/site/markdown/tutorial_rebalance.md
deleted file mode 100644
index 2e1a79b..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_rebalance.md
+++ /dev/null
@@ -1,181 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Rebalancing Algorithms</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Rebalancing Algorithms
-
-The placement of partitions in a distributed system is essential for the reliability and scalability of the system. For example, when a node fails, it is important that the partitions hosted on that node are reallocated evenly among the remaining nodes. Consistent hashing is one such algorithm that can satisfy this guarantee. Helix provides a variant of consistent hashing based on the RUSH algorithm, among others.
-
-This means given a number of partitions, replicas and number of nodes, Helix does the automatic assignment of partition to nodes such that:
-
-* Each node has the same number of partitions
-* Replicas of the same partition do not stay on the same node
-* When a node fails, the partitions will be equally distributed among the remaining nodes
-* When new nodes are added, the number of partitions moved will be minimized along with satisfying the above criteria
-
-Helix employs a rebalancing algorithm to compute the _ideal state_ of the system. When the _current state_ differs from the _ideal state_, Helix uses it as the target state of the system and computes the appropriate transitions needed to bring it to the _ideal state_.
-
-Helix makes it easy to perform this operation, while giving you control over the algorithm. In this section, we\'ll see how to implement the desired behavior.
-
-Helix has four options for rebalancing, in increasing order of customization by the system builder:
-
-* FULL_AUTO
-* SEMI_AUTO
-* CUSTOMIZED
-* USER_DEFINED
-
-```
- |FULL_AUTO | SEMI_AUTO | CUSTOMIZED| USER_DEFINED |
- ---------------------------------------------------------|
- LOCATION | HELIX | APP | APP | APP |
- ---------------------------------------------------------|
- STATE | HELIX | HELIX | APP | APP |
- ----------------------------------------------------------
-```
-
-
-### FULL_AUTO
-
-When the rebalance mode is set to FULL_AUTO, Helix controls both the location of the replica along with the state. This option is useful for applications where creation of a replica is not expensive.
-
-For example, consider this system that uses a MasterSlave state model, with 3 partitions and 2 replicas in the ideal state.
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "REBALANCE_MODE" : "FULL_AUTO",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- }
- "listFields" : {
- "MyResource_0" : [],
- "MyResource_1" : [],
- "MyResource_2" : []
- },
- "mapFields" : {
- }
-}
-```
-
-If there are 3 nodes in the cluster, then Helix will balance the masters and slaves equally. The ideal state is therefore:
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- },
- "mapFields" : {
- "MyResource_0" : {
- "N1" : "MASTER",
- "N2" : "SLAVE",
- },
- "MyResource_1" : {
- "N2" : "MASTER",
- "N3" : "SLAVE",
- },
- "MyResource_2" : {
- "N3" : "MASTER",
- "N1" : "SLAVE",
- }
- }
-}
-```
-
-Another typical example is evenly distributing a group of tasks among the currently healthy processes. For example, if there are 60 tasks and 4 nodes, Helix assigns 15 tasks to each node.
-When one node fails, Helix redistributes its 15 tasks to the remaining 3 nodes, resulting in a balanced 20 tasks per node. Similarly, if a node is added, Helix re-allocates 3 tasks from each of the 4 nodes to the 5th node, resulting in a balanced distribution of 12 tasks per node..
-
-### SEMI_AUTO
-
-When the application needs to control the placement of the replicas, use the SEMI_AUTO rebalance mode.
-
-Example: In the ideal state below, the partition \'MyResource_0\' is constrained to be placed only on node1 or node2. The choice of _state_ is still controlled by Helix. That means MyResource_0.MASTER could be on node1 and MyResource_0.SLAVE on node2, or vice-versa but neither would be placed on node3.
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "REBALANCE_MODE" : "SEMI_AUTO",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- }
- "listFields" : {
- "MyResource_0" : [node1, node2],
- "MyResource_1" : [node2, node3],
- "MyResource_2" : [node3, node1]
- },
- "mapFields" : {
- }
-}
-```
-
-The MasterSlave state model requires that a partition has exactly one MASTER at all times, and the other replicas should be SLAVEs. In this simple example with 2 replicas per partition, there would be one MASTER and one SLAVE. Upon failover, a SLAVE has to assume mastership, and a new SLAVE will be generated.
-
-In this mode when node1 fails, unlike in FULL_AUTO mode the partition is _not_ moved from node1 to node3. Instead, Helix will decide to change the state of MyResource_0 on node2 from SLAVE to MASTER, based on the system constraints.
-
-### CUSTOMIZED
-
-Helix offers a third mode called CUSTOMIZED, in which the application controls the placement _and_ state of each replica. The application needs to implement a callback interface that Helix invokes when the cluster state changes.
-Within this callback, the application can recompute the idealstate. Helix will then issue appropriate transitions such that _Idealstate_ and _Currentstate_ converges.
-
-Here\'s an example, again with 3 partitions, 2 replicas per partition, and the MasterSlave state model:
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "REBALANCE_MODE" : "CUSTOMIZED",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- },
- "mapFields" : {
- "MyResource_0" : {
- "N1" : "MASTER",
- "N2" : "SLAVE",
- },
- "MyResource_1" : {
- "N2" : "MASTER",
- "N3" : "SLAVE",
- },
- "MyResource_2" : {
- "N3" : "MASTER",
- "N1" : "SLAVE",
- }
- }
-}
-```
-
-Suppose the current state of the system is 'MyResource_0' \-\> {N1:MASTER, N2:SLAVE} and the application changes the ideal state to 'MyResource_0' \-\> {N1:SLAVE,N2:MASTER}. While the application decides which node is MASTER and which is SLAVE, Helix will not blindly issue MASTER\-\-\>SLAVE to N1 and SLAVE\-\-\>MASTER to N2 in parallel, since that might result in a transient state where both N1 and N2 are masters, which violates the MasterSlave constraint that there is exactly one MASTER [...]
-
-### USER_DEFINED
-
-For maximum flexibility, Helix exposes an interface that can allow applications to plug in custom rebalancing logic. By providing the name of a class that implements the Rebalancer interface, Helix will automatically call the contained method whenever there is a change to the live participants in the cluster. For more, see [User-Defined Rebalancer](./tutorial_user_def_rebalancer.html).
-
-### Backwards Compatibility
-
-In previous versions, FULL_AUTO was called AUTO_REBALANCE and SEMI_AUTO was called AUTO. Furthermore, they were presented as the IDEAL_STATE_MODE. Helix supports both IDEAL_STATE_MODE and REBALANCE_MODE, but IDEAL_STATE_MODE is now deprecated and may be phased out in future versions.
diff --git a/website/0.8.0/src/site/markdown/tutorial_rest_service.md b/website/0.8.0/src/site/markdown/tutorial_rest_service.md
deleted file mode 100644
index 111b5f2..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_rest_service.md
+++ /dev/null
@@ -1,951 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - REST Service 2.0</title>
-</head>
-
-
-
-## [Helix Tutorial](./Tutorial.html): REST Service 2.0
-
-New Helix REST service supported features:
-
-* Expose all admin operations via restful API.
- * All of Helix admin operations, include these defined in HelixAdmin.java and ConfigAccessor.java, etc, are exposed via rest API.
-* Support all task framework API via restful.Current task framework operations are supported from rest API too.
-* More standard Restful API
- * Use the standard HTTP methods if possible, GET, POST, PUT, DELETE, instead of customized command as it today.
- * Customized command will be used if there is no corresponding HTTP methods, for example, rebalance a resource, disable an instance, etc.
-* Make Helix restful service an separately deployable service.
-* Enable Access/Audit log for all write access.
-
-### Installation
-The command line tool comes with helix-core package:
-
-Get the command line tool:
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.0
-./build
-cd helix-rest/target/helix-rest-pkg/bin
-chmod +x *.sh
-```
-
-Get help:
-
-```
-./run-rest-admin.sh --help
-```
-
-Start the REST server
-
-```
-./run-rest-admin.sh --port 1234 --zkSvr localhost:2121
-```
-
-### Helix REST 2.0 Endpoint
-
-Helix REST 2.0 endpoint will start with /admin/v2 prefix, and the rest will mostly follow the current URL convention. This allows us to support v2.0 endpoint at the same time with the current Helix web interface. Some sample v2.0 endpoints would look like the following:
-
-```
-curl -X GET http://localhost:12345/admin/v2/clusters
-curl -X POST http://localhost:12345/admin/v2/clusters/myCluster
-curl -X POST http://localhost:12345/admin/v2/clusters/myCluster?command=activate&supercluster=controler_cluster
-curl http://localhost:12345/admin/v2/clusters/myCluster/resources/myResource/IdealState
-```
-### REST Endpoints and Supported Operations
-#### Operations on Helix Cluster
-
-* **"/clusters"**
- * Represents all helix managed clusters connected to given zookeeper
- * **GET** -- List all Helix managed clusters. Example: curl http://localhost:1234/admin/v2/clusters
-
- ```
- $curl http://localhost:1234/admin/v2/clusters
- {
- "clusters" : [ "cluster1", "cluster2", "cluster3"]
- }
- ```
-
-
-* **"/clusters/{clusterName}"**
- * Represents a helix cluster with name {clusterName}
- * **GET** -- return the cluster info. Example: curl http://localhost:1234/admin/v2/clusters/myCluster
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster
- {
- "id" : "myCluster",
- "paused" : true,
- "disabled" : true,
- "controller" : "helix.apache.org:1234",
- "instances" : [ "aaa.helix.apache.org:1234", "bbb.helix.apache.org:1234" ],
- "liveInstances" : ["aaa.helix.apache.org:1234"],
- "resources" : [ "resource1", "resource2", "resource3" ],
- "stateModelDefs" : [ "MasterSlave", "LeaderStandby", "OnlineOffline" ]
- }
- ```
-
- * **PUT** – create a new cluster with {clusterName}, it returns 200 if the cluster already exists. Example: curl -X PUT http://localhost:1234/admin/v2/clusters/myCluster
- * **DELETE** – delete this cluster.
- Example: curl -X DELETE http://localhost:1234/admin/v2/clusters/myCluster
- * **activate** -- Link this cluster to a Helix super (controller) cluster, i.e, add the cluster as a resource to the super cluster.
- Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster?command=activate&superCluster=myCluster
- * **expand** -- In the case that a set of new node is added in the cluster, use this command to balance the resources on the existing instances to new added instances.
- Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster?command=expand
- * **enable** – enable/resume the cluster.
- Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster?command=enable
- * **disable** – disable/pause the cluster.
- Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster?command=disable
-
-* **"/clusters/{clusterName}/configs"**
- * Represents cluster level configs for cluster with {clusterName}
- * **GET**: get all configs.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/configs
- {
- "id" : "myCluster",
- "simpleFields" : {
- "PERSIST_BEST_POSSIBLE_ASSIGNMENT" : "true"
- },
- "listFields" : {
- },
- "mapFields" : {
- }
- }
- ```
-
- * **POST**: update or delete one/some config entries.
- update -- Update the entries included in the input.
-
- ```
- $curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/configs?command=update -d '
- {
- "id" : "myCluster",
- "simpleFields" : {
- "PERSIST_BEST_POSSIBLE_ASSIGNMENT" : "true"
- },
- "listFields" : {
- "disabledPartition" : ["p1", "p2", "p3"]
- },
- "mapFields" : {
- }
- }'
- ```
-
- delete -- Remove the entries included in the input from current config.
-
- ```
- $curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/configs?command=update -d '
- {
- "id" : "myCluster",
- "simpleFields" : {
- },
- "listFields" : {
- "disabledPartition" : ["p1", "p3"]
- },
- "mapFields" : {
- }
- }'
- ```
-
-* **"/clusters/{clusterName}/controller"**
- * Represents the controller for cluster {clusterName}.
- * **GET** – return controller information
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/controller
- {
- "id" : "myCluster",
- "controller" : "test.helix.apache.org:1234",
- "HELIX_VERSION":"0.8.0",
- "LIVE_INSTANCE":"16261@test.helix.apache.org:1234",
- "SESSION_ID":"35ab496aba54c99"
- }
- ```
-
-* **"/clusters/{clusterName}/controller/errors"**
- * Represents error information for the controller of cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** – get all error information.
- * **DELETE** – clean up all error logs.
-
-
-* **"/clusters/{clusterName}/controller/history"**
- * Represents the change history of leader controller of cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** – get the leader controller history.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/controller/history
- {
- "id" : "myCluster",
- "history" [
- "{DATE=2017-03-21-16:57:14, CONTROLLER=test1.helix.apache.org:1234, TIME=1490115434248}",
- "{DATE=2017-03-27-22:35:16, CONTROLLER=test3.helix.apache.org:1234, TIME=1490654116484}",
- "{DATE=2017-03-27-22:35:24, CONTROLLER=test2.helix.apache.org:1234, TIME=1490654124926}"
- ]
- }
- ```
-
-* **/clusters/{clusterName}/controller/messages"**
- * Represents all uncompleted messages currently received by the controller of cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** – list all uncompleted messages received by the controller.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/controller/messages
- {
- "id" : "myCluster",
- "count" : 5,
- "messages" [
- "0b8df4f2-776c-4325-96e7-8fad07bd9048",
- "13a8c0af-b77e-4f5c-81a9-24fedb62cf58"
- ]
- }
- ```
-
-* **"/clusters/{clusterName}/controller/messages/{messageId}"**
- * Represents the messages currently received by the controller of cluster {clusterName} with id {messageId}. This is new endpoint in v2.0.
- * **GET** - get the message with {messageId} received by the controller.
- * **DELETE** - delete the message with {messageId}
-
-
-* **"/clusters/{clusterName}/statemodeldefs/"**
- * Represents all the state model definitions defined in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - get all the state model definition in the cluster.
-
- ```
- $curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/statemodeldefs
- {
- "id" : "myCluster",
- "stateModelDefs" : [ "MasterSlave", "LeaderStandby", "OnlineOffline" ]
- }
- ```
-
-* **"/clusters/{clusterName}/statemodeldefs/{statemodeldef}"**
- * Represents the state model definition {statemodeldef} defined in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - get the state model definition
-
- ```
- $curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/statemodeldefs/MasterSlave
- {
- "id" : "MasterSlave",
- "simpleFields" : {
- "INITIAL_STATE" : "OFFLINE"
- },
- "mapFields" : {
- "DROPPED.meta" : {
- "count" : "-1"
- },
- "ERROR.meta" : {
- "count" : "-1"
- },
- "ERROR.next" : {
- "DROPPED" : "DROPPED",
- "OFFLINE" : "OFFLINE"
- },
- "MASTER.meta" : {
- "count" : "1"
- },
- "MASTER.next" : {
- "SLAVE" : "SLAVE",
- "DROPPED" : "SLAVE",
- "OFFLINE" : "SLAVE"
- },
- "OFFLINE.meta" : {
- "count" : "-1"
- },
- "OFFLINE.next" : {
- "SLAVE" : "SLAVE",
- "MASTER" : "SLAVE",
- "DROPPED" : "DROPPED"
- },
- "SLAVE.meta" : {
- "count" : "R"
- },
- "SLAVE.next" : {
- "MASTER" : "MASTER",
- "DROPPED" : "OFFLINE",
- "OFFLINE" : "OFFLINE"
- }
- },
- "listFields" : {
- "STATE_PRIORITY_LIST" : [ "MASTER", "SLAVE", "OFFLINE", "DROPPED", "ERROR" ],
- "STATE_TRANSITION_PRIORITYLIST" : [ "MASTER-SLAVE", "SLAVE-MASTER", "OFFLINE-SLAVE", "SLAVE-OFFLINE", "OFFLINE-DROPPED" ]
- }
- }
- ```
-
- * **POST** - add a new state model definition with {statemodeldef}
- * **DELETE** - delete the state model definition
-
-
-#### Helix "Resource" and its sub-resources
-
-* **"/clusters/{clusterName}/resources"**
- * Represents all resources in a cluster.
- * **GET** - list all resources with their IdealStates and ExternViews.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/resources
- {
- "id" : "myCluster",
- "idealstates" : [ "idealstate1", "idealstate2", "idealstate3" ],
- "externalviews" : [ "idealstate1", "idealstate3" ]
- }
- ```
-
-* **"/clusters/{clusterName}/resources/{resourceName}"**
- * Represents a resource in cluster {clusterName} with name {resourceName}
- * **GET** - get resource info
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/resources/resource1
- {
- "id" : "resource1",
- "resourceConfig" : {},
- "idealState" : {},
- "externalView" : {}
- }
- ```
-
- * **PUT** - add a resource with {resourceName}
-
- ```
- $curl -X PUT -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/resources/myResource -d '
- {
- "id":"myResource",
- "simpleFields":{
- "STATE_MODEL_FACTORY_NAME":"DEFAULT"
- ,"EXTERNAL_VIEW_DISABLED":"true"
- ,"NUM_PARTITIONS":"1"
- ,"REBALANCE_MODE":"TASK"
- ,"REPLICAS":"1"
- ,"IDEAL_STATE_MODE":"AUTO"
- ,"STATE_MODEL_DEF_REF":"Task"
- ,"REBALANCER_CLASS_NAME":"org.apache.helix.task.WorkflowRebalancer"
- }
- }'
- ```
-
- * **DELETE** - delete a resource. Example: curl -X DELETE http://localhost:1234/admin/v2/clusters/myCluster/resources/myResource
- * **enable** enable the resource. Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster/resources/myResource?command=enable
- * **disable** - disable the resource. Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster/resources/myResource?command=disable
- * **rebalance** - rebalance the resource. Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster/resources/myResource?command=rebalance
-
-* **"/clusters/{clusterName}/resources/{resourceName}/idealState"**
- * Represents the ideal state of a resource with name {resourceName} in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - get idealstate.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/resources/myResource/idealState
- {
- "id":"myResource"
- ,"simpleFields":{
- "IDEAL_STATE_MODE":"AUTO"
- ,"NUM_PARTITIONS":"2"
- ,"REBALANCE_MODE":"SEMI_AUTO"
- ,"REPLICAS":"2"
- ,"STATE_MODEL_DEF_REF":"MasterSlave"
- }
- ,"listFields":{
- "myResource_0":["host1", "host2"]
- ,"myResource_1":["host2", "host1"]
- }
- ,"mapFields":{
- "myResource_0":{
- "host1":"MASTER"
- ,"host2":"SLAVE"
- }
- ,"myResource_1":{
- "host1":"SLAVE"
- ,"host2":"MASTER"
- }
- }
- }
- ```
-
-* **"/clusters/{clusterName}/resources/{resourceName}/externalView"**
- * Represents the external view of a resource with name {resourceName} in cluster {clusterName}
- * **GET** - get the externview
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/resources/myResource/externalView
- {
- "id":"myResource"
- ,"simpleFields":{
- "IDEAL_STATE_MODE":"AUTO"
- ,"NUM_PARTITIONS":"2"
- ,"REBALANCE_MODE":"SEMI_AUTO"
- ,"REPLICAS":"2"
- ,"STATE_MODEL_DEF_REF":"MasterSlave"
- }
- ,"listFields":{
- "myResource_0":["host1", "host2"]
- ,"myResource_1":["host2", "host1"]
- }
- ,"mapFields":{
- "myResource_0":{
- "host1":"MASTER"
- ,"host2":"OFFLINE"
- }
- ,"myResource_1":{
- "host1":"SLAVE"
- ,"host2":"MASTER"
- }
- }
- }
- ```
-
-* **"/clusters/{clusterName}/resources/{resourceName}/configs"**
- * Represents resource level of configs for resource with name {resourceName} in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - get resource configs.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/resources/myResource/configs
- {
- "id":"myDB"
- "UserDefinedProperty" : "property"
- }
- ```
-
-#### Helix Instance and its sub-resources
-
-* **"/clusters/{clusterName}/instances"**
- * Represents all instances in a cluster {clusterName}
- * **GET** - list all instances in this cluster.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances
- {
- "id" : "myCluster",
- "instances" : [ "host1", "host2", "host3", "host4"],
- "online" : ["host1", "host4"],
- "disabled" : ["host2"]
- }
- ```
-
- * **POST** - enable/disable instances.
-
- ```
- $curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/instances/command=enable -d
- {
- "instances" : [ "host1", "host3" ]
- }
- $curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/instances/command=disable -d
- {
- "instances" : [ "host2", "host4" ]
- }
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}"**
- * Represents a instance in cluster {clusterName} with name {instanceName}
- * **GET** - get instance information.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234
- {
- "id" : "host_1234",
- "configs" : {
- "HELIX_ENABLED" : "true",
- "HELIX_HOST" : "host",
- "HELIX_PORT" : "1234",
- "HELIX_DISABLED_PARTITION" : [ ]
- }
- "liveInstance" : {
- "HELIX_VERSION":"0.6.6.3",
- "LIVE_INSTANCE":"4526@host",
- "SESSION_ID":"359619c2d7efc14"
- }
- }
- ```
-
- * **PUT** - add a new instance with {instanceName}
-
- ```
- $curl -X PUT -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234 -d '
- {
- "id" : "host_1234",
- "simpleFields" : {
- "HELIX_ENABLED" : "true",
- "HELIX_HOST" : "host",
- "HELIX_PORT" : "1234",
- }
- }'
- ```
-
- There's one important restriction for this operation: the {instanceName} should match exactly HELIX_HOST + "_" + HELIX_PORT. For example, if host is localhost, and port is 1234, the instance name should be localhost_1234. Otherwise, the response won't contain any error but the configurations are not able to be filled in.
-
- * **DELETE** - delete the instance. Example: curl -X DELETE http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234
- * **enable** - enable the instance. Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234?command=enable
- * **disable** - disable the instance. Example: curl -X POST http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234?command=disable
-
- * **addInstanceTag** - add tags to this instance.
-
- ```
- $curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234?command=addInstanceTag -d '
- {
- "id" : "host_1234",
- "instanceTags" : [ "tag_1", "tag_2, "tag_3" ]
- }'
- ```
-
- * **removeInstanceTag** - remove a tag from this instance.
-
- ```
- $curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234?command=removeInstanceTag -d '
- {
- "id" : "host_1234",
- "instanceTags" : [ "tag_1", "tag_2, "tag_3" ]
- }'
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}/resources"**
- * Represents all resources and their partitions locating on the instance in cluster {clusterName} with name {instanceName}. This is new endpoint in v2.0.
- * **GET** - return all resources that have partitions in the instance.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/resources
- {
- "id" : "host_1234",
- "resources" [ "myResource1", "myResource2", "myResource3"]
- }
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}/resources/{resource}"**
- * Represents all partitions of the {resource} locating on the instance in cluster {clusterName} with name {instanceName}. This is new endpoint in v2.0.
- * **GET** - return all partitions of the resource in the instance.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/localhost_1234/resources/myResource1
- {
- "id":"myResource1"
- ,"simpleFields":{
- "STATE_MODEL_DEF":"MasterSlave"
- ,"STATE_MODEL_FACTORY_NAME":"DEFAULT"
- ,"BUCKET_SIZE":"0"
- ,"SESSION_ID":"359619c2d7f109b"
- }
- ,"listFields":{
- }
- ,"mapFields":{
- "myResource1_2":{
- "CURRENT_STATE":"SLAVE"
- ,"INFO":""
- }
- ,"myResource1_3":{
- "CURRENT_STATE":"MASTER"
- ,"INFO":""
- }
- ,"myResource1_0":{
- "CURRENT_STATE":"MASTER"
- ,"INFO":""
- }
- ,"myResource1_1":{
- "CURRENT_STATE":"SLAVE"
- ,"INFO":""
- }
- }
- }
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}/configs"**
- * Represents instance configs in cluster {clusterName} with name {instanceName}. This is new endpoint in v2.0.
- * **GET** - return configs for the instance.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/configs
- {
- "id":"host_1234"
- "configs" : {
- "HELIX_ENABLED" : "true",
- "HELIX_HOST" : "host"
- "HELIX_PORT" : "1234",
- "HELIX_DISABLED_PARTITION" : [ ]
- }
- ```
-
- * **PUT** - PLEASE NOTE THAT THIS PUT IS FULLY OVERRIDE THE INSTANCE CONFIG
-
- ```
- $curl -X PUT -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/configs
- {
- "id":"host_1234"
- "configs" : {
- "HELIX_ENABLED" : "true",
- "HELIX_HOST" : "host"
- "HELIX_PORT" : "1234",
- "HELIX_DISABLED_PARTITION" : [ ]
- }
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}/errors"**
- * List all the mapping of sessionId to partitions of resources. This is new endpoint in v2.0.
- * **GET** - get mapping
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/errors
- {
- "id":"host_1234"
- "errors":{
- "35sfgewngwese":{
- "resource1":["p1","p2","p5"],
- "resource2":["p2","p7"]
- }
- }
- }
- ```
-
- * **DELETE** - clean up all error information from Helix.
-
-* **"/clusters/{clusterName}/instances/{instanceName}/errors/{sessionId}/{resourceName}/{partitionName}"**
- * Represents error information for the partition {partitionName} of the resource {resourceName} under session {sessionId} in instance with {instanceName} in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - get all error information.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/errors/35sfgewngwese/resource1/p1
- {
- "id":"35sfgewngwese_resource1"
- ,"simpleFields":{
- }
- ,"listFields":{
- }
- ,"mapFields":{
- "HELIX_ERROR 20170521-070822.000561 STATE_TRANSITION b819a34d-41b5-4b42-b497-1577501eeecb":{
- "AdditionalInfo":"Exception while executing a state transition task ..."
- ,"MSG_ID":"4af79e51-5f83-4892-a271-cfadacb0906f"
- ,"Message state":"READ"
- }
- }
- }
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}/history"**
- * Represents instance session change history for the instance with {instanceName} in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - get the instance change history.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/history
- {
- "id": "host_1234",
- "LAST_OFFLINE_TIME": "183948792",
- "HISTORY": [
- "{DATE=2017-03-02T19:25:18:915, SESSION=459014c82ef3f5b, TIME=1488482718915}",
- "{DATE=2017-03-10T22:24:53:246, SESSION=15982390e5d5c91, TIME=1489184693246}",
- "{DATE=2017-03-11T02:03:52:776, SESSION=15982390e5d5d85, TIME=1489197832776}",
- "{DATE=2017-03-13T18:15:00:778, SESSION=15982390e5d678d, TIME=1489428900778}",
- "{DATE=2017-03-21T02:47:57:281, SESSION=459014c82effa82, TIME=1490064477281}",
- "{DATE=2017-03-27T14:51:06:802, SESSION=459014c82f01a07, TIME=1490626266802}",
- "{DATE=2017-03-30T00:05:08:321, SESSION=5590151804e2c78, TIME=1490832308321}",
- "{DATE=2017-03-30T01:17:34:339, SESSION=2591d53b0421864, TIME=1490836654339}",
- "{DATE=2017-03-30T17:31:09:880, SESSION=2591d53b0421b2a, TIME=1490895069880}",
- "{DATE=2017-03-30T18:05:38:220, SESSION=359619c2d7f109b, TIME=1490897138220}"
- ]
- }
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}/messages"**
- * Represents all uncompleted messages currently received by the instance. This is new endpoint in v2.0.
- * **GET** - list all uncompleted messages received by the controller.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/messages
- {
- "id": "host_1234",
- "new_messages": ["0b8df4f2-776c-4325-96e7-8fad07bd9048", "13a8c0af-b77e-4f5c-81a9-24fedb62cf58"],
- "read_messages": ["19887b07-e9b8-4fa6-8369-64146226c454"]
- "total_message_count" : 100,
- "read_message_count" : 50
- }
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}/messages/{messageId}**
- * Represents the messages currently received by by the instance with message given message id. This is new endpoint in v2.0.
- * **GET** - get the message content with {messageId} received by the instance.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/localhost_1234/messages/0b8df4f2-776c-4325-96e7-8fad07bd9048
- {
- "id": "0b8df4f2-776c-4325-96e7-8fad07bd9048",
- "CREATE_TIMESTAMP":"1489997469400",
- "ClusterEventName":"messageChange",
- "FROM_STATE":"OFFLINE",
- "MSG_ID":"0b8df4f2-776c-4325-96e7-8fad07bd9048",
- "MSG_STATE":"new",
- "MSG_TYPE":"STATE_TRANSITION",
- "PARTITION_NAME":"Resource1_243",
- "RESOURCE_NAME":"Resource1",
- "SRC_NAME":"controller_1234",
- "SRC_SESSION_ID":"15982390e5d5a76",
- "STATE_MODEL_DEF":"LeaderStandby",
- "STATE_MODEL_FACTORY_NAME":"myFactory",
- "TGT_NAME":"host_1234",
- "TGT_SESSION_ID":"459014c82efed9b",
- "TO_STATE":"DROPPED"
- }
- ```
-
- * **DELETE** - delete the message with {messageId}. Example: $curl -X DELETE http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/messages/0b8df4f2-776c-4325-96e7-8fad07bd9048
-
-* **"/clusters/{clusterName}/instances/{instanceName}/healthreports"**
- * Represents all health reports in the instance in cluster {clusterName} with name {instanceName}. This is new endpoint in v2.0.
- * **GET** - return the name of health reports collected from the instance.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/healthreports
- {
- "id" : "host_1234",
- "healthreports" [ "report1", "report2", "report3" ]
- }
- ```
-
-* **"/clusters/{clusterName}/instances/{instanceName}/healthreports/{reportName}"**
- * Represents the health report with {reportName} in the instance in cluster {clusterName} with name {instanceName}. This is new endpoint in v2.0.
- * **GET** - return the content of health report collected from the instance.
-
- ```
- $curl http://localhost:1234/admin/v2/clusters/myCluster/instances/host_1234/healthreports/ClusterStateStats
- {
- "id":"ClusterStateStats"
- ,"simpleFields":{
- "CREATE_TIMESTAMP":"1466753504476"
- ,"TimeStamp":"1466753504476"
- }
- ,"listFields":{
- }
- ,"mapFields":{
- "UserDefinedData":{
- "Data1":"0"
- ,"Data2":"0.0"
- }
- }
- }
- ```
-
-
-#### Helix Workflow and its sub-resources
-
-* **"/clusters/{clusterName}/workflows"**
- * Represents all workflows in cluster {clusterName}
- * **GET** - list all workflows in this cluster. Example : curl http://localhost:1234/admin/v2/clusters/TestCluster/workflows
-
- ```
- {
- "Workflows" : [ "Workflow1", "Workflow2" ]
- }
- ```
-
-* **"/clusters/{clusterName}/workflows/{workflowName}"**
- * Represents workflow with name {workflowName} in cluster {clusterName}
- * **GET** - return workflow information. Example : curl http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1
-
- ```
- {
- "id" : "Workflow1",
- "WorkflowConfig" : {
- "Expiry" : "43200000",
- "FailureThreshold" : "0",
- "IsJobQueue" : "true",
- "LAST_PURGE_TIME" : "1490820801831",
- "LAST_SCHEDULED_WORKFLOW" : "Workflow1_20170329T000000",
- "ParallelJobs" : "1",
- "RecurrenceInterval" : "1",
- "RecurrenceUnit" : "DAYS",
- "START_TIME" : "1482176880535",
- "STATE" : "STOPPED",
- "StartTime" : "12-19-2016 00:00:00",
- "TargetState" : "START",
- "Terminable" : "false",
- "capacity" : "500"
- },
- "WorkflowContext" : {
- "JOB_STATES": {
- "Job1": "COMPLETED",
- "Job2": "COMPLETED"
- },
- "StartTime": {
- "Job1": "1490741582339",
- "Job2": "1490741580204"
- },
- "FINISH_TIME": "1490741659135",
- "START_TIME": "1490741580196",
- "STATE": "COMPLETED"
- },
- "Jobs" : ["Job1","Job2","Job3"],
- "ParentJobs" : {
- "Job1":["Job2", "Job3"],
- "Job2":["Job3"]
- }
- }
- ```
-
- * **PUT** - create a workflow with {workflowName}. Example : curl -X PUT -H "Content-Type: application/json" -d [WorkflowExample.json](./WorkflowExample.json) http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1
- * **DELETE** - delete the workflow. Example : curl -X DELETE http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1
- * **start** - start the workflow. Example : curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1?command=start
- * **stop** - pause the workflow. Example : curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1?command=stop
- * **resume** - resume the workflow. Example : curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1?command=resume
- * **cleanup** - cleanup all expired jobs in the workflow, this operation is only allowed if the workflow is a JobQueue. Example : curl -X POST -H "Content-Type: application/json" http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1?command=clean
-
-* **"/clusters/{clusterName}/workflows/{workflowName}/configs"**
- * Represents workflow config with name {workflowName} in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - return workflow configs. Example : curl http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1/configs
-
- ```
- {
- "id": "Workflow1",
- "Expiry" : "43200000",
- "FailureThreshold" : "0",
- "IsJobQueue" : "true",
- "START_TIME" : "1482176880535",
- "StartTime" : "12-19-2016 00:00:00",
- "TargetState" : "START",
- "Terminable" : "false",
- "capacity" : "500"
- }
- ```
-
-* **"/clusters/{clusterName}/workflows/{workflowName}/context"**
- * Represents workflow runtime information with name {workflowName} in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - return workflow runtime information. Example : curl http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1/context
-
- ```
- {
- "id": "WorkflowContext",
- "JOB_STATES": {
- "Job1": "COMPLETED",
- "Job2": "COMPLETED"
- },
- "StartTime": {
- "Job1": "1490741582339",
- "Job2": "1490741580204"
- },
- "FINISH_TIME": "1490741659135",
- "START_TIME": "1490741580196",
- "STATE": "COMPLETED"
- }
- ```
-
-
-#### Helix Job and its sub-resources
-
-* **"/clusters/{clusterName}/workflows/{workflowName}/jobs"**
- * Represents all jobs in workflow {workflowName} in cluster {clusterName}
- * **GET** return all job names in this workflow. Example : curl http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1/jobs
-
- ```
- {
- "id":"Jobs"
- "Jobs":["Job1","Job2","Job3"]
- }
- ```
-
-* **"/clusters/{clusterName}/workflows/{workflowName}/jobs/{jobName}"**
- * Represents job with {jobName} within {workflowName} in cluster {clusterName}
- * **GET** return job information. Example : curl http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1/jobs/Job1
-
- ```
- {
- "id":"Job1"
- "JobConfig":{
- "WorkflowID":"Workflow1",
- "IgnoreDependentJobFailure":"false",
- "MaxForcedReassignmentsPerTask":"3"
- },
- "JobContext":{
- "START_TIME":"1491005863291",
- "FINISH_TIME":"1491005902612",
- "Tasks":[
- {
- "id":"0",
- "ASSIGNED_PARTICIPANT":"P1",
- "FINISH_TIME":"1491005898905"
- "INFO":""
- "NUM_ATTEMPTS":"1"
- "START_TIME":"1491005863307"
- "STATE":"COMPLETED"
- "TARGET":"DB_0"
- },
- {
- "id":"1",
- "ASSIGNED_PARTICIPANT":"P5",
- "FINISH_TIME":"1491005895443"
- "INFO":""
- "NUM_ATTEMPTS":"1"
- "START_TIME":"1491005863307"
- "STATE":"COMPLETED"
- "TARGET":"DB_1"
- }
- ]
- }
- }
- ```
-
- * **PUT** - insert a job with {jobName} into the workflow, this operation is only allowed if the workflow is a JobQueue.
- Example : curl -X PUT -H "Content-Type: application/json" -d [JobExample.json](./JobExample.json) http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1/jobs/Job1
- * **DELETE** - delete the job from the workflow, this operation is only allowed if the workflow is a JobQueue.
- Example : curl -X DELETE http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1/jobs/Job1
-
-* **"/clusters/{clusterName}/workflows/{workflowName}/jobs/{jobName}/configs"**
- * Represents job config for {jobName} within workflow {workflowName} in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - return job config. Example : curl http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1/jobs/Job1/configs
-
- ```
- {
- "id":"JobConfig"
- "WorkflowID":"Workflow1",
- "IgnoreDependentJobFailure":"false",
- "MaxForcedReassignmentsPerTask":"3"
- }
- ```
-
-* **"/clusters/{clusterName}/workflows/{workflowName}/jobs/{jobName}/context"**
- * Represents job runtime information with {jobName} in {workflowName} in cluster {clusterName}. This is new endpoint in v2.0.
- * **GET** - return job runtime information. Example : curl http://localhost:1234/admin/v2/clusters/TestCluster/workflows/Workflow1/jobs/Job1/context
-
- ```
- {
- "id":"JobContext":
- "START_TIME":"1491005863291",
- "FINISH_TIME":"1491005902612",
- "Tasks":[
- {
- "id":"0",
- "ASSIGNED_PARTICIPANT":"P1",
- "FINISH_TIME":"1491005898905"
- "INFO":""
- "NUM_ATTEMPTS":"1"
- "START_TIME":"1491005863307"
- "STATE":"COMPLETED"
- "TARGET":"DB_0"
- },
- {
- "id":"1",
- "ASSIGNED_PARTICIPANT":"P5",
- "FINISH_TIME":"1491005895443"
- "INFO":""
- "NUM_ATTEMPTS":"1"
- "START_TIME":"1491005863307"
- "STATE":"COMPLETED"
- "TARGET":"DB_1"
- }
- ]
- }
- ```
\ No newline at end of file
diff --git a/website/0.8.0/src/site/markdown/tutorial_spectator.md b/website/0.8.0/src/site/markdown/tutorial_spectator.md
deleted file mode 100644
index e43cd6b..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_spectator.md
+++ /dev/null
@@ -1,75 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Spectator</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Spectator
-
-Next, we\'ll learn how to implement a __spectator__. Typically, a spectator needs to react to changes within the distributed system. Examples: a client that needs to know where to send a request, a topic consumer in a consumer group. The spectator is automatically informed of changes in the _external state_ of the cluster, but it does not have to add any code to keep track of other components in the system.
-
-### Start a Connection
-
-Same as for a participant, The Helix manager is the common component that connects each system component with the cluster.
-
-It requires the following parameters:
-
-* clusterName: A logical name to represent the group of nodes
-* instanceName: A logical name of the process creating the manager instance. Generally this is host:port
-* instanceType: Type of the process. This can be one of the following types, in this case, use SPECTATOR:
- * CONTROLLER: Process that controls the cluster, any number of controllers can be started but only one will be active at any given time
- * PARTICIPANT: Process that performs the actual task in the distributed system
- * SPECTATOR: Process that observes the changes in the cluster
- * ADMIN: To carry out system admin actions
-* zkConnectString: Connection string to ZooKeeper. This is of the form host1:port1,host2:port2,host3:port3
-
-After the Helix manager instance is created, the only thing that needs to be registered is the listener. When the ExternalView changes, the listener is notified.
-
-A spectator observes the cluster and is notified when the state of the system changes. Helix consolidates the state of entire cluster in one Znode called ExternalView.
-Helix provides a default implementation RoutingTableProvider that caches the cluster state and updates it when there is a change in the cluster.
-
-```
-manager = HelixManagerFactory.getZKHelixManager(clusterName,
- instanceName,
- InstanceType.SPECTATOR,
- zkConnectString);
-manager.connect();
-RoutingTableProvider routingTableProvider = new RoutingTableProvider();
-manager.addExternalViewChangeListener(routingTableProvider);
-```
-
-### Spectator Code
-
-In the following code snippet, the application sends the request to a valid instance by interrogating the external view. Suppose the desired resource for this request is in the partition myDB_1.
-
-```
-// instances = routingTableProvider.getInstances(, "PARTITION_NAME", "PARTITION_STATE");
-instances = routingTableProvider.getInstances("myDB", "myDB_1", "ONLINE");
-
-////////////////////////////////////////////////////////////////////////////////////////////////
-// Application-specific code to send a request to one of the instances //
-////////////////////////////////////////////////////////////////////////////////////////////////
-
-theInstance = instances.get(0); // should choose an instance and throw an exception if none are available
-result = theInstance.sendRequest(yourApplicationRequest, responseObject);
-
-```
-
-When the external view changes, the application needs to react by sending requests to a different instance.
diff --git a/website/0.8.0/src/site/markdown/tutorial_state.md b/website/0.8.0/src/site/markdown/tutorial_state.md
deleted file mode 100644
index 856b8b3..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_state.md
+++ /dev/null
@@ -1,131 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - State Machine Configuration</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): State Machine Configuration
-
-In this chapter, we\'ll learn about the state models provided by Helix, and how to create your own custom state model.
-
-### State Models
-
-Helix comes with 3 default state models that are commonly used. It is possible to have multiple state models in a cluster.
-Every resource that is added should be configured to use a state model that govern its _ideal state_.
-
-#### MASTER-SLAVE
-
-* 3 states: OFFLINE, SLAVE, MASTER
-* Maximum number of masters: 1
-* Slaves are based on the replication factor. The replication factor can be specified while adding the resource.
-
-
-#### ONLINE-OFFLINE
-
-* Has 2 states: OFFLINE and ONLINE. This simple state model is a good starting point for most applications.
-
-#### LEADER-STANDBY
-
-* 1 Leader and multiple stand-bys. The idea is that exactly one leader accomplishes a designated task, the stand-bys are ready to take over if the leader fails.
-
-### Constraints
-
-In addition to the state machine configuration, one can specify the constraints of states and transitions.
-
-For example, one can say:
-
-* MASTER:1
-<br/>Maximum number of replicas in MASTER state at any time is 1
-
-* OFFLINE-SLAVE:5
-<br/>Maximum number of OFFLINE-SLAVE transitions that can happen concurrently in the system is 5 in this example.
-
-#### Dynamic State Constraints
-
-We also support two dynamic upper bounds for the number of replicas in each state:
-
-* N: The number of replicas in the state is at most the number of live participants in the cluster
-* R: The number of replicas in the state is at most the specified replica count for the partition
-
-#### State Priority
-
-Helix uses a greedy approach to satisfy the state constraints. For example, if the state machine configuration says it needs 1 MASTER and 2 SLAVES, but only 1 node is active, Helix must promote it to MASTER. This behavior is achieved by providing the state priority list as \[MASTER, SLAVE\].
-
-#### State Transition Priority
-
-Helix tries to fire as many transitions as possible in parallel to reach the stable state without violating constraints. By default, Helix simply sorts the transitions alphabetically and fires as many as it can without violating the constraints. You can control this by overriding the priority order.
-
-### Special States
-
-There are a few Helix-defined states that are important to be aware of.
-
-#### DROPPED
-
-The DROPPED state is used to signify a replica that was served by a given participant, but is no longer served. This allows Helix and its participants to effectively clean up. There are two requirements that every new state model should follow with respect to the DROPPED state:
-
-* The DROPPED state must be defined
-* There must be a path to DROPPED for every state in the model
-
-#### ERROR
-
-The ERROR state is used whenever the participant serving a partition encountered an error and cannot continue to serve the partition. HelixAdmin has \"reset\" functionality to allow for participants to recover from the ERROR state.
-
-### Annotated Example
-
-Below is a complete definition of a Master-Slave state model. Notice the fields marked REQUIRED; these are essential for any state model definition.
-
-```
-StateModelDefinition stateModel = new StateModelDefinition.Builder("MasterSlave")
- // OFFLINE is the state that the system starts in (initial state is REQUIRED)
- .initialState("OFFLINE")
-
- // Lowest number here indicates highest priority, no value indicates lowest priority
- .addState("MASTER", 1)
- .addState("SLAVE", 2)
- .addState("OFFLINE")
-
- // Note the special inclusion of the DROPPED state (REQUIRED)
- .addState(HelixDefinedState.DROPPED.toString())
-
- // No more than one master allowed
- .upperBound("MASTER", 1)
-
- // R indicates an upper bound of number of replicas for each partition
- .dynamicUpperBound("SLAVE", "R")
-
- // Add some high-priority transitions
- .addTransition("SLAVE", "MASTER", 1)
- .addTransition("OFFLINE", "SLAVE", 2)
-
- // Using the same priority value indicates that these transitions can fire in any order
- .addTransition("MASTER", "SLAVE", 3)
- .addTransition("SLAVE", "OFFLINE", 3)
-
- // Not specifying a value defaults to lowest priority
- // Notice the inclusion of the OFFLINE to DROPPED transition
- // Since every state has a path to OFFLINE, they each now have a path to DROPPED (REQUIRED)
- .addTransition("OFFLINE", HelixDefinedState.DROPPED.toString())
-
- // Create the StateModelDefinition instance
- .build();
-
- // Use the isValid() function to make sure the StateModelDefinition will work without issues
- Assert.assertTrue(stateModel.isValid());
-```
diff --git a/website/0.8.0/src/site/markdown/tutorial_task_framework.md b/website/0.8.0/src/site/markdown/tutorial_task_framework.md
deleted file mode 100644
index 9659ada..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_task_framework.md
+++ /dev/null
@@ -1,382 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Task Framework</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Task Framework
-
-Task framework, in Helix, provides executable task scheduling and workflow management. In Helix, three layers of task abstraction have been offered to user for defining their logics of dependencies. The graph shows the relationships between three layers. Workflow can contain multiple jobs. One job can depend on other one. Multiple tasks, including same task different partition and different task different partition, can be added in one job.
-Task framework not only can abstract three layers task logics but also helps doing task assignment and rebalancing. User can create a workflow (or a job queue) at first beginning. Then jobs can be added into workflow. Those jobs contain the executable tasks implemented by user. Once workflow is completed, Helix will schedule the works based on the condition user provided.
-
-
-
-### Key Concepts
-* Task is the basic unit in Helix task framework. It can represents the a single runnable logics that user prefer to execute for each partition (distributed units).
-* Job defines one time operation across all the partitions. It contains multiple Tasks and configuration of tasks, such as how many tasks, timeout per task and so on.
-* Workflow is directed acyclic graph represents the relationships and running orders of Jobs. In addition, a workflow can also provide customized configuration, for example, Job dependencies.
-* JobQueue is another type of Workflow. Different from normal one, JobQueue is not terminated until user kill it. Also JobQueue can keep accepting newly coming jobs.
-
-### Implement Your Task
-
-#### [Task Interface](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/Task.java)
-
-The task interface contains two methods: run and cancel. User can implement his or her own logic in run function and cancel / roll back logic in cancel function.
-
-```
-public class MyTask implements Task {
- @Override
- TaskResult run() {
- // Task logic
- }
-
- @Override
- void cancel() {
- // Cancel logic
- }
-}
-```
-
-#### [TaskConfig](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/TaskConfig.java)
-
-In helix, usually an object config represents the abstraction of that object, such as TaskConfig, JobConfig and WorkflowConfig. TaskConfig contains configurable task conditions. TaskConfig does not require to have any input to create a new object:
-
-```
-TaskConfig taskConfig = new TaskConfig(null, null, null, null);
-```
-
-For these four fields:
-* Command: The task command, will use Job command if this is null
-* ID: Task unique id, will generate a new ID for this task if input is null
-* TaskTargetPartition: Target partition of a target. Could be null
-* ConfigMap: Task property key-value map containing all other property stated above, such as command, ID.
-
-#### Share Content Across Tasks and Jobs
-
-Task framework also provides a feature that user can store the key-value data per task, job and workflow. The content stored at workflow layer can shared by different jobs belong to this workflow. Similarly content persisted at job layer can shared by different tasks nested in this job. Currently, user can extend the abstract class [UserContentStore](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/UserContentStore.java) and use two methods [...]
-
-```
-public class MyTask extends UserContentStore implements Task {
- @Override
- TaskResult run() {
- putUserContent("KEY", "WORKFLOWVALUE", SCOPE.WORKFLOW);
- putUserContent("KEY", "JOBVALUE", SCOPE.JOB);
- putUserContent("KEY", "TASKVALUE", SCOPE.TASK);
- String taskValue = getUserContent("KEY", SCOPE.TASK);
- }
- ...
-}
-```
-
-#### Return [Task Results](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/TaskResult.java)
-
-User can define the TaskResult for a task once it is at final stage (complete or failed). The TaskResult contains two fields: status and info. Status is current Task Status including COMPLETED, CANCELLED, FAILED and FATAL_FAILED. The difference between FAILED and FATAL_FAILED is that once the task defined as FATAL_FAILED, helix will not do the retry for this task and abort it. The other field is information, which is a String type. User can pass any information including error message, d [...]
-
-```
-TaskResult run() {
- ....
- return new TaskResult(TaskResult.Status.FAILED, "ERROR MESSAGE OR OTHER INFORMATION");
-}
-```
-
-#### Task Retry and Abort
-
-Helix provides retry logics to users. User can specify the how many times allowed to tolerant failure of tasks under a job. It is a method will be introduced in Following Job Section. Another choice offered to user that if user thinks a task is very critical and do not want to do the retry once it is failed, user can return a TaskResult stated above with FATAL_FAILED status. Then Helix will not do the retry for that task.
-
-```
-return new TaskResult(TaskResult.Status.FATAL_FAILED, "DO NOT WANT TO RETRY, ERROR MESSAGE");
-```
-
-#### [TaskDriver](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/TaskDriver.java)
-
-All the control operation related to workflow and job are based on TaskDriver object. TaskDriver offers several APIs to controller, modify and track the tasks. Those APIs will be introduced in each section when they are necessary. TaskDriver object can be created either by [HelixManager](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/HelixManager.java) or [ZkClient](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/a [...]
-
-```
-HelixManager manager = new ZKHelixManager(CLUSTER_NAME, INSTANCE_NAME, InstanceType.PARTICIPANT, ZK_ADDRESS);
-TaskDriver taskDriver1 = new TaskDriver(manager);
-
-TaskDriver taskDriver2 = new TaskDriver(zkclient, CLUSTER_NAME);
-```
-
-#### Propagate Task Error Message to Helix
-
-When task encounter an error, it could be returned by TaskResult. Unfortunately, user can not get this TaskResult object directly. But Helix provides error messages persistent. Thus user can fetch the error messages from Helix via TaskDriver, which introduced above. The error messages will be stored in Info field per Job. Thus user have to get JobContext, which is the job status and result object.
-
-```
-taskDriver.getJobContext("JOBNAME").getInfo();
-```
-
-### Creating a Workflow
-
-#### One-time Workflow
-
-As common use, one-time workflow will be the default workflow as user created. The first step is to create a WorkflowConfig.Builder object with workflow name. Then all configs can be set in WorkflowConfig.Builder. Once the configuration is done, [WorkflowConfig](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/WorkflowConfig.java) object can be got from WorkflowConfig.Builder object.
-We have two rules to validate the Workflow configuration:
-* Expiry time should not be less than 0
-* Schedule config should be valid either one-time or a positive interval magnitude (Recurrent workflow)
-Example:
-
-```
-Workflow.Builder myWorkflowBuilder = new Workflow.Builder("MyWorkflow");
-myWorkflowBuilder.setExpiry(5000L);
-Workflow myWorkflow = myWorkflowBuilder.build();
-```
-
-#### Recurrent Workflow
-
-Recurrent workflow is the workflow scheduled periodically. The only config different from One-time workflow is to set a recurrent [ScheduleConfig](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/ScheduleConfig.java). There two methods in ScheduleConfig can help you to create a ScheduleConfig object: recurringFromNow and recurringFromDate. Both of them needs recurUnit (time unit for recurrent) and recurInteval (magnitude of recurrent interva [...]
-
-```
-ScheduleConfig myConfig1 = ScheduleConfig.recurringFFromNow(TimeUnit.MINUTES, 5L);
-ScheduleConfig myConfig2 = ScheduleConfig.recurringFFromDate(Calendar.getInstance.getTime, TimeUnit.HOURS, 10L);
-```
-
-Once this schedule config is created. It could be set in the workflow config:
-
-```
-Workflow.Builder myWorkflowBuilder = new Workflow.Builder("MyWorkflow");
-myWorkflowBuilder.setExpiry(2000L)
- .setScheduleConfig(ScheduleConfig.recurringFromNow(TimeUnit.DAYS, 5));
-Workflow myWorkflow = myWorkflowBuilder.build();
-```
-
-#### Start a Workflow
-
-Start a workflow is just using taskdrive to start it. Since this is an async call, after start the workflow, user can keep doing actions.
-
-```
-taskDriver.start(myWorkflow);
-```
-
-#### Stop a Workflow
-
-Stop workflow can be executed via TaskDriver:
-
-```
-taskDriver.stop(myWorkflow);
-```
-
-#### Resume a Workflow
-
-Once the workflow is stopped, it does not mean the workflow is gone. Thus user can resume the workflow that has been stopped. Using TaskDriver resume the workflow:
-
-```
-taskDriver.resume(myWorkflow);
-```
-
-#### Delete a Workflow
-
-Similar to start, stop and resume, delete operation is supported by TaskDriver.
-
-```
-taskDriver.delete(myWorkflow);
-```
-
-#### Add a Job
-
-WARNING: Job can only be added to WorkflowConfig.Builder. Once WorkflowConfig built, no job can be added! For creating a Job, please refering following section (Create a Job)
-
-```
-myWorkflowBuilder.addJob("JobName", jobConfigBuilder);
-```
-
-#### Add a Job dependency
-
-Jobs can have dependencies. If one job2 depends job1, job2 will not be scheduled until job1 finished.
-
-```
-myWorkflowBuilder.addParentChildDependency(ParentJobName, ChildJobName);
-```
-
-#### Schedule a workflow for executing in a future time
-
-Application can create a workflow with a ScheduleConfig so as to schedule it to be executed in a future time.
-
-```
-myWorkflowBuilder.setScheduleConfig(ScheduleConfig.oneTimeDelayedStart(new Date(inFiveSeconds)));
-```
-
-#### Additional Workflow Options
-
-| Additional Config Options | Detail |
-| ------------------------- | ------ |
-| _setJobDag(JobDag v)_ | If user already defined the job DAG, it could be set with this method. |
-| _setExpiry(long v, TimeUnit unit)_ | Set the expiration time for this workflow. |
-| _setFailureThreshold(int failureThreshold)_ | Set the failure threshold for this workflow, once job failures reach this number, the workflow will be failed. |
-| _setWorkflowType(String workflowType)_ | Set the user defined workflowType for this workflow. |
-| _setTerminable(boolean isTerminable)_ | Set the whether this workflow is terminable or not. |
-| _setCapacity(int capacity)_ | Set the number of jobs that workflow can hold before reject further jobs. Only used when workflow is not terminable. |
-| _setTargetState(TargetState v)_ | Set the final state of this workflow. |
-
-### Creating a Queue
-
-[Job queue](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/JobQueue.java) is another shape of workflow. Here listed different between a job queue and workflow:
-
-| Property | Workflow | Job Queue |
-| -------- | -------- | --------- |
-| Existing time | Workflow will be deleted after it is done. | Job queue will be there until user delete it. |
-| Add jobs | Once workflow is build, no job can be added. | Job queue can keep accepting jobs. |
-| Parallel run | Allows parallel run for jobs without dependencies | No parallel run allowed except setting _ParallelJobs_ |
-
-For creating a job queue, user have to provide queue name and workflow config (please refer above Create a Workflow). Similar to other task object, create a JobQueue.Builder first. Then JobQueue can be validated and generated via build function.
-
-```
-WorkflowConfig.Builder myWorkflowCfgBuilder = new WorkflowConfig.Builder().setWorkFlowType("MyType");
-JobQueue jobQueue = new JobQueue.Builder("MyQueueName").setWorkflowConfig(myWorkflowCfgBuilder.build()).build();
-```
-
-####Append Job to Queue
-
-WARNING:Different from normal workflow, job for JobQueue can be append even in anytime. Similar to workflow add a job, job can be appended via enqueueJob function via TaskDriver.
-
-```
-jobQueueBuilder.enqueueJob("JobName", jobConfigBuilder);
-```
-
-####Delete Job from Queue
-
-Helix allowed user to delete a job from existing queue. We offers delete API in TaskDriver to do this. Delete job from queue and this queue has to be stopped. Then user can resume the job once delete success.
-
-```
-taskDriver.stop("QueueName");
-taskDriver.deleteJob("QueueName", "JobName");
-taskDriver.resume("QueueName");
-```
-
-####Additional Option for JobQueue
-
-_setParallelJobs(int parallelJobs)_ : Set the how many jobs can parallel running, except there is any dependencies.
-
-###Create a Job
-
-Before generate a [JobConfig](https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/task/JobConfig.java) object, user still have to use JobConfig.Builder to build JobConfig.
-
-```
-JobConfig.Builder myJobCfgBuilder = new JobConfig.Builder();
-JobConfig myJobCfg = myJobCfgBuilder.build();
-```
-
-Helix has couple rules to validate a job:
-* Each job must at least have one task to execute. For adding tasks and task rules please refer following section Add Tasks.
-* Task timeout should not less than zero.
-* Number of concurrent tasks per instances should not less than one.
-* Maximum attempts per task should not less than one
-* There must be a workflow name
-
-#### Add Tasks
-
-There are two ways of adding tasks:
-* Add by TaskConfig. Tasks can be added via adding TaskConfigs. User can create a List of TaskConfigs or add TaskConfigMap, which is a task id to TaskConfig mapping.
-
-```
-TaskConfig taskCfg = new TaskConfig(null, null, null, null);
-List<TaskConfig> taskCfgs = new ArrayList<TaskConfig>();
-myJobCfg.addTaskConfigs(taskCfgs);
-
-Map<String, TaskConfig> taskCfgMap = new HashMap<String, TaskConfig>();
-taskCfgMap.put(taskCfg.getId(), taskCfg);
-myJobCfg.addTaskConfigMap(taskCfgMap);
-```
-
-* Add by Job command. If user does not want to specify each TaskConfig, we can create identical tasks based on Job command with number of tasks.
-
-```
-myJobCfg.setCommand("JobCommand").setNumberOfTasks(10);
-```
-WARNING: Either user provides TaskConfigs / TaskConfigMap or both of Job command and number tasks (except Targeted Job, refer following section) . Otherwise, validation will be failed.
-
-#### Generic Job
-
-Generic Job is the default job created. It does not have targeted resource. Thus this generic job could be assigned to one of eligble instances.
-
-#### Targeted Job
-
-Targeted Job has set up the target resource. For this kind of job, Job command is necessary, but number of tasks is not. The tasks will depends on the partion number of targeted resource. To set target resource, just put target resource name to JobConfig.Builder.
-
-```
-myJobCfgBuilder.setTargetResource("TargetResourceName");
-```
-
-In addition, user can specify the instance target state. For example, if user want to run the Task on "Master" state instance, setTargetPartitionState method can help to set the partition to assign to specific instance.
-
-```
-myJobCfgBuilder.setTargetPartitionState(Arrays.asList(new String[]{"Master", "Slave"}));
-```
-
-#### Instance Group
-
-Grouping jobs with targeted group of instances feature has been supported. User firstly have to define the instance group tag for instances, which means label some instances with specific tag. Then user can put those tags to a job that only would like to assigned to those instances. For example, customer data only available on instance 1, 2, 3. These three instances can be tagged as "CUSTOMER" and customer data related jobs can set the instance group tag "CUSTOMER". Thus customer data [...]
-To add instance group tag, just set it in JobConfig.Builder:
-
-```
-jobCfg.setInstanceGroupTag("INSTANCEGROUPTAG");
-```
-
-#### Delayed scheduling job
-
-Set up a schedule plan for the job.
-If both items are set, Helix will calculate and use the later one.
-
-```
-myJobCfgBuilder.setExecutionDelay(delayMs);
-myJobCfgBuilder.setExecutionStart(startTimeMs);
-```
-
-Note that the scheduled job needs to be runnable first. Then Helix will start checking it's configuration for scheduling.
-If any parent jobs are not finished, the job won't be scheduled even the scheduled timestamp has already passed.
-
-#### Additional Job Options
-
-| Operation | Detail |
-| --------- | ------ |
-| _setWorkflow(String workflowName)_ | Set the workflow that this job belongs to |
-| _setTargetPartions(List\<String\> targetPartionNames)_ | Set list of partition names |
-| _setTargetPartionStates(Set\<String\>)_ | Set the partition states |
-| _setCommand(String command)_ | Set the job command |
-| _setJobCommandConfigMap(Map\<String, String\> v)_ | Set the job command config maps |
-| _setTimeoutPerTask(long v)_ | Set the timeout for each task |
-| _setNumConcurrentTasksPerInstance(int v)_ | Set number of tasks can concurrent run on same instance |
-| _setMaxAttemptsPerTask(int v)_ | Set times of retry for a task |
-| _setFailureThreshold(int v)_ | Set failure tolerance of tasks for this job |
-| _setTaskRetryDelay(long v)_ | Set the delay time before a task retry |
-| _setIgnoreDependentJobFailure(boolean ignoreDependentJobFailure)_ | Set whether ignore the job failure of parent job of this job |
-| _setJobType(String jobType)_ | Set the job type of this job |
-| _setExecutionDelay(String delay)_ | Set the delay time to schedule job execution |
-| _setExecutionStart(String start)_ | Set the start time to schedule job execution |
-
-### Monitor the status of your job
-As we introduced the excellent util TaskDriver in Workflow Section, we have extra more functionality that provided to user. The user can synchronized wait Job or Workflow until it reaches certain STATES. The function Helix have API pollForJobState and pollForWorkflowState. For pollForJobState, it accepts arguments:
-* Workflow name, required
-* Job name, required
-* Timeout, not required, will be three minutes if user choose function without timeout argument. Time unit is milisecond.
-* TaskStates, at least one state. This function can accept multiple TaskState, will end function until one of those TaskState reaches.
-For example:
-
-```
-taskDriver.pollForJobState("MyWorkflowName", "MyJobName", 180000L, TaskState.FAILED, TaskState.FATAL_FAILED);
-taskDriver.pollForJobState("MyWorkflowName", "MyJobName", TaskState.COMPLETED);
-```
-
-For pollForWorkflowState, it accepts similar arguments except Job name. For example:
-
-```
-taskDriver.pollForWorkflowState("MyWorkflowName", 180000L, TaskState.FAILED, TaskState.FATAL_FAILED);
-taskDriver.pollForWorkflowState("MyWorkflowName", TaskState.COMPLETED);
-```
diff --git a/website/0.8.0/src/site/markdown/tutorial_task_throttling.md b/website/0.8.0/src/site/markdown/tutorial_task_throttling.md
deleted file mode 100644
index e9029d9..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_task_throttling.md
+++ /dev/null
@@ -1,41 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Task Throttling</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Task Throttling
-
-In this chapter, we\'ll learn how to control the parallel execution of tasks in the task framework.
-
-### Task Throttling Configuration
-
-Helix can control the number of tasks that are executed in parallel according to multiple thresholds.
-Applications can set these thresholds in the following configuration items:
-
-* JobConfig.ConcurrentTasksPerInstance The number of concurrent tasks in this job that are allowed to run on an instance.
-* InstanceConfig.MAX_CONCURRENT_TASK The number of total concurrent tasks that are allowed to run on an instance.
-
-Also see [WorkflowConfig.ParallelJobs](./tutorial_task_framework.html).
-
-### Job Priority for Task Throttling
-
-Whenever there are too many tasks to be scheduled according to the threshold, Helix will prioritize the older jobs.
-The age of a job is calculated based on the job start time.
diff --git a/website/0.8.0/src/site/markdown/tutorial_throttling.md b/website/0.8.0/src/site/markdown/tutorial_throttling.md
deleted file mode 100644
index 16a6f81..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_throttling.md
+++ /dev/null
@@ -1,39 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Throttling</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Throttling
-
-In this chapter, we\'ll learn how to control the parallel execution of cluster tasks. Only a centralized cluster manager with global knowledge (i.e. Helix) is capable of coordinating this decision.
-
-### Throttling
-
-Since all state changes in the system are triggered through transitions, Helix can control the number of transitions that can happen in parallel. Some of the transitions may be lightweight, but some might involve moving data, which is quite expensive from a network and IOPS perspective.
-
-Helix allows applications to set a threshold on transitions. The threshold can be set at multiple scopes:
-
-* MessageType e.g STATE_TRANSITION
-* TransitionType e.g SLAVE-MASTER
-* Resource e.g database
-* Node i.e per-node maximum transitions in parallel
-
-
diff --git a/website/0.8.0/src/site/markdown/tutorial_ui.md b/website/0.8.0/src/site/markdown/tutorial_ui.md
deleted file mode 100644
index da6c361..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_ui.md
+++ /dev/null
@@ -1,118 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - Helix UI Setup</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): Helix UI Setup
-
-Helix now provides a modern web user interface for users to manage Helix clusters in a more convenient way (aka Helix UI). Currently the following features are supported via Helix UI:
-
-* View all Helix clusters exposed by Helix REST service
-* View detailed cluster information
-* View resources / instances in a Helix cluster
-* View partition placement and health status in a resource
-* Create new Helix clusters
-* Enable / Disable a cluster / resource / instance
-* Add an instance into a Helix cluster
-
-### Prerequisites
-
-Since Helix UI is talking with Helix REST service to manage Helix clusters, a well deployed Helix REST service is required and necessary. Please refer to this tutorial to setup a functional Helix REST service: [Helix REST Service 2.0](./tutorial_rest_service.html).
-
-### Installation
-
-To get and run Helix UI locally, simply use the following command lines:
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix/helix-front
-git checkout tags/helix-0.8.0
-../build
-cd target/helix-front-pkg/bin
-chmod +x *.sh
-```
-
-### Configuration
-
-Helix UI does not need any configuration if you have started Helix REST service without specifying a port ( Helix REST service will be serving through http://localhost:8100/admin/v2 ). If you have specified a customized port or you need to wire in additional REST services, please navigate to `../dist/server/config.js` and edit the following section accordingly:
-
-```
-...
-exports.HELIX_ENDPOINTS = {
- <service nickname>: [
- {
- <nickname of REST endpoint>: '<REST endpoint url>'
- }
- ]
-};
-...
-```
-
-For example, if you have multiple Helix REST services deployed (all listening on port 12345), and you want to divide them into two services, and each service will contain two groups (e.g. staging and production), and each group will contain two fabrics as well, you may configure the above section like this:
-
-```
-...
-exports.HELIX_ENDPOINTS = {
- service1: [
- {
- staging1: 'http://staging1.service1.com:12345/admin/v2',
- staging2: 'http://staging2.service1.com:12345/admin/v2'
- },
- {
- production1: 'http://production1.service1.com:12345/admin/v2',
- production2: 'http://production2.service1.com:12345/admin/v2'
- }
- ],
- service2: [
- {
- staging1: 'http://staging1.service2.com:12345/admin/v2',
- staging2: 'http://staging2.service2.com:12345/admin/v2'
- },
- {
- production1: 'http://production1.service2.com:12345/admin/v2',
- production2: 'http://production2.service2.com:12345/admin/v2'
- }
- ]
-};
-...
-
-```
-
-
-### Launch Helix UI
-
-```
-./start-helix-ui.sh
-```
-
-Helix UI will be listening on your port `3000` by default. Just use any browser to navigate to http://localhost:3000 to get started.
-
-### Introduction
-
-The primary UI will look like this:
-
-
-
-The left side is the cluster list, and the right side is the detailed cluster view if you click one on the left. You will find resource list, workflow list and instance list of the cluster as well as the cluster configurations.
-
-When navigating into a single resource, Helix UI will show the partition placement with comparison of idealStates and externalViews like this:
-
-
diff --git a/website/0.8.0/src/site/markdown/tutorial_user_content_store.md b/website/0.8.0/src/site/markdown/tutorial_user_content_store.md
deleted file mode 100644
index 81c502b..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_user_content_store.md
+++ /dev/null
@@ -1,67 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - User Defined Content Store for Tasks</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): User Defined Content Store for Tasks
-
-The purpose of user defined content store is to provide an easy use feature for some task dedicated meta temporary store.
-In this chapter, we\'ll learn how to implement and use content store in the user defined tasks.
-
-### Content Store Implementation
-
-Extends abstract class UserContentStore.
-
- private static class ContentStoreTask extends UserContentStore implements Task {
- @Override public TaskResult run() {
- ...
- }
- @Override public void cancel() {
- ...
- }
- }
-
-The default methods support 3 types of scopes:
-1. WORKFLOW: Define the content store in workflow level
-2. JOB: Define the content store in job level
-3. TASK: Define the content store in task level
-
-### Content Store Usage
-
-Access content store in Task.run() method.
-
- private static class ContentStoreTask extends UserContentStore implements Task {
- @Override public TaskResult run() {
- // put values into the store
- putUserContent("ContentTest", "Value1", Scope.JOB);
- putUserContent("ContentTest", "Value2", Scope.WORKFLOW);
- putUserContent("ContentTest", "Value3", Scope.TASK);
-
- // get the values with the same key in the different scopes
- if (!getUserContent("ContentTest", Scope.JOB).equals("Value1") ||
- !getUserContent("ContentTest", Scope.WORKFLOW).equals("Value2") ||
- !getUserContent("ContentTest", Scope.TASK).equals("Value3")) {
- return new TaskResult(TaskResult.Status.FAILED, null);
- }
-
- return new TaskResult(TaskResult.Status.COMPLETED, null);
- }
- }
diff --git a/website/0.8.0/src/site/markdown/tutorial_user_def_rebalancer.md b/website/0.8.0/src/site/markdown/tutorial_user_def_rebalancer.md
deleted file mode 100644
index 2149739..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_user_def_rebalancer.md
+++ /dev/null
@@ -1,172 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - User-Defined Rebalancing</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): User-Defined Rebalancing
-
-Even though Helix can compute both the location and the state of replicas internally using a default fully-automatic rebalancer, specific applications may require rebalancing strategies that optimize for different requirements. Thus, Helix allows applications to plug in arbitrary rebalancer algorithms that implement a provided interface. One of the main design goals of Helix is to provide maximum flexibility to any distributed application. Thus, it allows applications to fully implement [...]
-
-Whenever the state of the cluster changes, as is the case when participants join or leave the cluster, Helix automatically calls the rebalancer to compute a new mapping of all the replicas in the resource. When using a pluggable rebalancer, the only required step is to register it with Helix. Subsequently, no additional bootstrapping steps are necessary. Helix uses reflection to look up and load the class dynamically at runtime. As a result, it is also technically possible to change the [...]
-
-The Rebalancer interface is as follows:
-
-```
-void init(HelixManager manager);
-
-IdealState computeNewIdealState(String resourceName, IdealState currentIdealState,
- final CurrentStateOutput currentStateOutput, final ClusterDataCache clusterData);
-```
-The first parameter is the resource to rebalance, the second is pre-existing ideal mappings, the third is a snapshot of the actual placements and state assignments, and the fourth is a full cache of all of the cluster data available to Helix. Internally, Helix implements the same interface for its own rebalancing routines, so a user-defined rebalancer will be cognizant of the same information about the cluster as an internal implementation. Helix strives to provide applications the abili [...]
-
-An IdealState is a full representation of the location of each replica of each partition of a given resource. This is a simple representation of the placement that the algorithm believes is the best possible. If the placement meets all defined constraints, this is what will become the actual state of the distributed system.
-
-### Specifying a Rebalancer
-For implementations that set up the cluster through existing code, the following HelixAdmin calls will update the Rebalancer class:
-
-```
-IdealState idealState = helixAdmin.getResourceIdealState(clusterName, resourceName);
-idealState.setRebalanceMode(RebalanceMode.USER_DEFINED);
-idealState.setRebalancerClassName(className);
-helixAdmin.setResourceIdealState(clusterName, resourceName, idealState);
-```
-
-There are two key fields to set to specify that a pluggable rebalancer should be used. First, the rebalance mode should be set to USER_DEFINED, and second the rebalancer class name should be set to a class that implements Rebalancer and is within the scope of the project. The class name is a fully-qualified class name consisting of its package and its name. Without specification of the USER_DEFINED mode, the user-defined rebalancer class will not be used even if specified. Furthermore, H [...]
-
-### Example
-
-In the next release (0.7.0), we will provide a full recipe of a user-defined rebalancer in action.
-
-Consider the case where partitions are locks in a lock manager and 6 locks are to be distributed evenly to a set of participants, and only one participant can hold each lock. We can define a rebalancing algorithm that simply takes the modulus of the lock number and the number of participants to evenly distribute the locks across participants. Helix allows capping the number of partitions a participant can accept, but since locks are lightweight, we do not need to define a restriction in [...]
-
-```
-@Override
-IdealState computeNewIdealState(String resourceName, IdealState currentIdealState,
- final CurrentStateOutput currentStateOutput, final ClusterDataCache clusterData) {
- // Get the list of live participants in the cluster
- List<String> liveParticipants = new ArrayList<String>(clusterData.getLiveInstances().keySet());
-
- // Count the number of participants allowed to lock each lock (in this example, this is 1)
- int lockHolders = Integer.parseInt(currentIdealState.getReplicas());
-
- // Fairly assign the lock state to the participants using a simple mod-based sequential
- // assignment. For instance, if each lock can be held by 3 participants, lock 0 would be held
- // by participants (0, 1, 2), lock 1 would be held by (1, 2, 3), and so on, wrapping around the
- // number of participants as necessary.
- int i = 0;
- for (String partition : currentIdealState.getPartitionSet()) {
- List<String> preferenceList = new ArrayList<String>();
- for (int j = i; j < i + lockHolders; j++) {
- int participantIndex = j % liveParticipants.size();
- String participant = liveParticipants.get(participantIndex);
- // enforce that a participant can only have one instance of a given lock
- if (!preferenceList.contains(participant)) {
- preferenceList.add(participant);
- }
- }
- currentIdealState.setPreferenceList(partition, preferenceList);
- i++;
- }
- return assignment;
-}
-```
-
-Here are the IdealState preference lists emitted by the user-defined rebalancer for a 3-participant system whenever there is a change to the set of participants.
-
-* Participant_A joins
-
-```
-{
- "lock_0": ["Participant_A"],
- "lock_1": ["Participant_A"],
- "lock_2": ["Participant_A"],
- "lock_3": ["Participant_A"],
- "lock_4": ["Participant_A"],
- "lock_5": ["Participant_A"],
-}
-```
-
-A preference list is a mapping for each resource of partition to the participants serving each replica. The state model is a simple LOCKED/RELEASED model, so participant A holds all lock partitions in the LOCKED state.
-
-* Participant_B joins
-
-```
-{
- "lock_0": ["Participant_A"],
- "lock_1": ["Participant_B"],
- "lock_2": ["Participant_A"],
- "lock_3": ["Participant_B"],
- "lock_4": ["Participant_A"],
- "lock_5": ["Participant_B"],
-}
-```
-
-Now that there are two participants, the simple mod-based function assigns every other lock to the second participant. On any system change, the rebalancer is invoked so that the application can define how to redistribute its resources.
-
-* Participant_C joins (steady state)
-
-```
-{
- "lock_0": ["Participant_A"],
- "lock_1": ["Participant_B"],
- "lock_2": ["Participant_C"],
- "lock_3": ["Participant_A"],
- "lock_4": ["Participant_B"],
- "lock_5": ["Participant_C"],
-}
-```
-
-This is the steady state of the system. Notice that four of the six locks now have a different owner. That is because of the naïve modulus-based assignmemt approach used by the user-defined rebalancer. However, the interface is flexible enough to allow you to employ consistent hashing or any other scheme if minimal movement is a system requirement.
-
-* Participant_B fails
-
-```
-{
- "lock_0": ["Participant_A"],
- "lock_1": ["Participant_C"],
- "lock_2": ["Participant_A"],
- "lock_3": ["Participant_C"],
- "lock_4": ["Participant_A"],
- "lock_5": ["Participant_C"],
-}
-```
-
-On any node failure, as in the case of node addition, the rebalancer is invoked automatically so that it can generate a new mapping as a response to the change. Helix ensures that the Rebalancer has the opportunity to reassign locks as required by the application.
-
-* Participant_B (or the replacement for the original Participant_B) rejoins
-
-```
-{
- "lock_0": ["Participant_A"],
- "lock_1": ["Participant_B"],
- "lock_2": ["Participant_C"],
- "lock_3": ["Participant_A"],
- "lock_4": ["Participant_B"],
- "lock_5": ["Participant_C"],
-}
-```
-
-The rebalancer was invoked once again and the resulting IdealState preference lists reflect the steady state.
-
-### Caveats
-- The rebalancer class must be available at runtime, or else Helix will not attempt to rebalance at all
-- The Helix controller will only take into account the preference lists in the new IdealState for this release. In 0.7.0, Helix rebalancers will be able to compute the full resource assignment, including the states.
-- Helix does not currently persist the new IdealState computed by the user-defined rebalancer. However, the Helix property store is available for saving any computed state. In 0.7.0, Helix will persist the result of running the rebalancer.
diff --git a/website/0.8.0/src/site/markdown/tutorial_yaml.md b/website/0.8.0/src/site/markdown/tutorial_yaml.md
deleted file mode 100644
index 1e4772e..0000000
--- a/website/0.8.0/src/site/markdown/tutorial_yaml.md
+++ /dev/null
@@ -1,102 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial - YAML Cluster Setup</title>
-</head>
-
-## [Helix Tutorial](./Tutorial.html): YAML Cluster Setup
-
-As an alternative to using Helix Admin to set up the cluster, its resources, constraints, and the state model, Helix supports bootstrapping a cluster configuration based on a YAML file. Below is an annotated example of such a file for a simple distributed lock manager where a lock can only be LOCKED or RELEASED, and each lock only allows a single participant to hold it in the LOCKED state.
-
-```
-clusterName: lock-manager-custom-rebalancer # unique name for the cluster (required)
-resources:
- - name: lock-group # unique resource name (required)
- rebalancer: # required
- mode: USER_DEFINED # required - USER_DEFINED means we will provide our own rebalancer
- class: org.apache.helix.userdefinedrebalancer.LockManagerRebalancer # required for USER_DEFINED
- partitions:
- count: 12 # number of partitions for the resource (default is 1)
- replicas: 1 # number of replicas per partition (default is 1)
- stateModel:
- name: lock-unlock # model name (required)
- states: [LOCKED, RELEASED, DROPPED] # the list of possible states (required if model not built-in)
- transitions: # the list of possible transitions (required if model not built-in)
- - name: Unlock
- from: LOCKED
- to: RELEASED
- - name: Lock
- from: RELEASED
- to: LOCKED
- - name: DropLock
- from: LOCKED
- to: DROPPED
- - name: DropUnlock
- from: RELEASED
- to: DROPPED
- - name: Undrop
- from: DROPPED
- to: RELEASED
- initialState: RELEASED # (required if model not built-in)
- constraints:
- state:
- counts: # maximum number of replicas of a partition that can be in each state (required if model not built-in)
- - name: LOCKED
- count: "1"
- - name: RELEASED
- count: "-1"
- - name: DROPPED
- count: "-1"
- priorityList: [LOCKED, RELEASED, DROPPED] # states in order of priority (all priorities equal if not specified)
- transition: # transitions priority to enforce order that transitions occur
- priorityList: [Unlock, Lock, Undrop, DropUnlock, DropLock] # all priorities equal if not specified
-participants: # list of nodes that can serve replicas (optional if dynamic joining is active, required otherwise)
- - name: localhost_12001
- host: localhost
- port: 12001
- - name: localhost_12002
- host: localhost
- port: 12002
- - name: localhost_12003
- host: localhost
- port: 12003
-```
-
-Using a file like the one above, the cluster can be set up either with the command line:
-
-```
-helix/helix-core/target/helix-core/pkg/bin/YAMLClusterSetup.sh localhost:2199 lock-manager-config.yaml
-```
-
-or with code:
-
-```
-YAMLClusterSetup setup = new YAMLClusterSetup(zkAddress);
-InputStream input =
- Thread.currentThread().getContextClassLoader()
- .getResourceAsStream("lock-manager-config.yaml");
-YAMLClusterSetup.YAMLClusterConfig config = setup.setupCluster(input);
-```
-
-Some notes:
-
-- A rebalancer class is only required for the USER_DEFINED mode. It is ignored otherwise.
-
-- Built-in state models, like OnlineOffline, LeaderStandby, and MasterSlave, or state models that have already been added only require a name for stateModel. If partition and/or replica counts are not provided, a value of 1 is assumed.
diff --git a/website/0.8.0/src/site/resources/.htaccess b/website/0.8.0/src/site/resources/.htaccess
deleted file mode 100644
index d5c7bf3..0000000
--- a/website/0.8.0/src/site/resources/.htaccess
+++ /dev/null
@@ -1,20 +0,0 @@
-#
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements. See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership. The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License. You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "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.
-#
-
-Redirect /download.html /download.cgi
diff --git a/website/0.8.0/src/site/resources/JobExample.json b/website/0.8.0/src/site/resources/JobExample.json
deleted file mode 100644
index 113a691..0000000
--- a/website/0.8.0/src/site/resources/JobExample.json
+++ /dev/null
@@ -1,19 +0,0 @@
-{
- "id" : "TestJob",
- "simpleFields": {
- "JobID":"Job2",
- "WorkflowID":"Workflow1"
- },
- "mapFields":{
- "Task1" : {
- "TASK_ID":"Task1",
- "TASK_COMMAND":"Backup",
- "TASK_TARGET_PARTITION":"p1"
- },
- "Task2" : {
- "TASK_ID":"Task2",
- "TASK_COMMAND":"ReIndex",
- }
- },
- "listFields":{}
-}
diff --git a/website/0.8.0/src/site/resources/WorkflowExample.json b/website/0.8.0/src/site/resources/WorkflowExample.json
deleted file mode 100644
index 1f2578f..0000000
--- a/website/0.8.0/src/site/resources/WorkflowExample.json
+++ /dev/null
@@ -1,46 +0,0 @@
-{"id":"Workflow1",
- "WorkflowConfig":{
- "id":"Workflow1",
- "Expiry":"43200000",
- "FailureThreshold":"0",
- "IsJobQueue":"true",
- "TargetState":"START",
- "Terminable":"false",
- "capacity":"500"
- },
- "Jobs":[
- {
- "id" : "Job1",
- "simpleFields": {
- "JobID":"Job1",
- "WorkflowID" : "Workflow1"
- },
- "mapFields":{
- "Task1" : {
- "TASK_ID" : "Task1",
- "TASK_COMMAND" : "Backup",
- "TASK_TARGET_PARTITION" : "p1"
- },
- "Task2" : {
- "TASK_ID" : "Task2",
- "TASK_COMMAND" : "ReIndex"
- }
- },
- "listFields":{}
- },
- {
- "id":"Job2",
- "Command":"Cleanup",
- "TargetResource":"DB2"
- },
- {
- "id":"Job3",
- "Command":"Backup",
- "TargetResource":"DB3"
- }
- ],
- "ParentJobs":{
- "Job1":["Job2","Job3],
- "Job2":["Job3"]
- }
-}
\ No newline at end of file
diff --git a/website/0.8.0/src/site/resources/css/bootstrap-responsive.min.css b/website/0.8.0/src/site/resources/css/bootstrap-responsive.min.css
deleted file mode 100644
index 5cb833f..0000000
--- a/website/0.8.0/src/site/resources/css/bootstrap-responsive.min.css
+++ /dev/null
@@ -1,9 +0,0 @@
-/*!
- * Bootstrap Responsive v2.2.2
- *
- * Copyright 2012 Twitter, Inc
- * Licensed under the Apache License v2.0
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Designed and built with all the love in the world @twitter by @mdo and @fat.
- */@-ms-viewport{width:device-width}.clearfix{*zoom:1}.clearfix:before,.clearfix:after{display:table;line-height:0;content:""}.clearfix:after{clear:both}.hide-text{font:0/0 a;color:transparent;text-shadow:none;background-color:transparent;border:0}.input-block-level{display:block;width:100%;min-height:30px;-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box}.hidden{display:none;visibility:hidden}.visible-phone{display:none!important}.visible-tablet{display:none [...]
diff --git a/website/0.8.0/src/site/resources/css/bootstrap.min.css b/website/0.8.0/src/site/resources/css/bootstrap.min.css
deleted file mode 100644
index 140f731..0000000
--- a/website/0.8.0/src/site/resources/css/bootstrap.min.css
+++ /dev/null
@@ -1,9 +0,0 @@
-/*!
- * Bootstrap v2.2.2
- *
- * Copyright 2012 Twitter, Inc
- * Licensed under the Apache License v2.0
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Designed and built with all the love in the world @twitter by @mdo and @fat.
- */article,aside,details,figcaption,figure,footer,header,hgroup,nav,section{display:block}audio,canvas,video{display:inline-block;*display:inline;*zoom:1}audio:not([controls]){display:none}html{font-size:100%;-webkit-text-size-adjust:100%;-ms-text-size-adjust:100%}a:focus{outline:thin dotted #333;outline:5px auto -webkit-focus-ring-color;outline-offset:-2px}a:hover,a:active{outline:0}sub,sup{position:relative;font-size:75%;line-height:0;vertical-align:baseline}sup{top:-0.5em}sub{bottom:- [...]
diff --git a/website/0.8.0/src/site/resources/download.cgi b/website/0.8.0/src/site/resources/download.cgi
deleted file mode 100755
index f9a0e30..0000000
--- a/website/0.8.0/src/site/resources/download.cgi
+++ /dev/null
@@ -1,22 +0,0 @@
-#!/bin/sh
-# Just call the standard mirrors.cgi script. It will use download.html
-# as the input template.
-#
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements. See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership. The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License. You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "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.
-#
-exec /www/www.apache.org/dyn/mirrors/mirrors.cgi $*
diff --git a/website/0.8.0/src/site/resources/images/PFS-Generic.png b/website/0.8.0/src/site/resources/images/PFS-Generic.png
deleted file mode 100644
index 7eea3a0..0000000
Binary files a/website/0.8.0/src/site/resources/images/PFS-Generic.png and /dev/null differ
diff --git a/website/0.8.0/src/site/resources/images/RSYNC_BASED_PFS.png b/website/0.8.0/src/site/resources/images/RSYNC_BASED_PFS.png
deleted file mode 100644
index 0cc55ae..0000000
Binary files a/website/0.8.0/src/site/resources/images/RSYNC_BASED_PFS.png and /dev/null differ
diff --git a/website/0.8.0/src/site/resources/images/TaskFrameworkLayers.png b/website/0.8.0/src/site/resources/images/TaskFrameworkLayers.png
deleted file mode 100644
index 4ee24a8..0000000
Binary files a/website/0.8.0/src/site/resources/images/TaskFrameworkLayers.png and /dev/null differ
diff --git a/website/0.8.0/src/site/resources/images/UIScreenshot.png b/website/0.8.0/src/site/resources/images/UIScreenshot.png
deleted file mode 100644
index 2ea08b9..0000000
Binary files a/website/0.8.0/src/site/resources/images/UIScreenshot.png and /dev/null differ
diff --git a/website/0.8.0/src/site/resources/images/UIScreenshot2.png b/website/0.8.0/src/site/resources/images/UIScreenshot2.png
deleted file mode 100644
index 6c0a89e..0000000
Binary files a/website/0.8.0/src/site/resources/images/UIScreenshot2.png and /dev/null differ
diff --git a/website/0.8.0/src/site/resources/js/bootstrap.min.js b/website/0.8.0/src/site/resources/js/bootstrap.min.js
deleted file mode 100644
index 6eeb15c..0000000
--- a/website/0.8.0/src/site/resources/js/bootstrap.min.js
+++ /dev/null
@@ -1,6 +0,0 @@
-/*!
-* Bootstrap.js by @fat & @mdo
-* Copyright 2012 Twitter, Inc.
-* http://www.apache.org/licenses/LICENSE-2.0.txt
-*/
-!function($){"use strict";$(function(){$.support.transition=function(){var transitionEnd=function(){var name,el=document.createElement("bootstrap"),transEndEventNames={WebkitTransition:"webkitTransitionEnd",MozTransition:"transitionend",OTransition:"oTransitionEnd otransitionend",transition:"transitionend"};for(name in transEndEventNames)if(void 0!==el.style[name])return transEndEventNames[name]}();return transitionEnd&&{end:transitionEnd}}()})}(window.jQuery),!function($){"use strict";v [...]
\ No newline at end of file
diff --git a/website/0.8.0/src/site/resources/js/jquery.min.js b/website/0.8.0/src/site/resources/js/jquery.min.js
deleted file mode 100644
index 3883779..0000000
--- a/website/0.8.0/src/site/resources/js/jquery.min.js
+++ /dev/null
@@ -1,2 +0,0 @@
-/*! jQuery v1.8.3 jquery.com | jquery.org/license */
-(function(e,t){function _(e){var t=M[e]={};return v.each(e.split(y),function(e,n){t[n]=!0}),t}function H(e,n,r){if(r===t&&e.nodeType===1){var i="data-"+n.replace(P,"-$1").toLowerCase();r=e.getAttribute(i);if(typeof r=="string"){try{r=r==="true"?!0:r==="false"?!1:r==="null"?null:+r+""===r?+r:D.test(r)?v.parseJSON(r):r}catch(s){}v.data(e,n,r)}else r=t}return r}function B(e){var t;for(t in e){if(t==="data"&&v.isEmptyObject(e[t]))continue;if(t!=="toJSON")return!1}return!0}function et(){retur [...]
\ No newline at end of file
diff --git a/website/0.8.0/src/site/site.xml b/website/0.8.0/src/site/site.xml
deleted file mode 100644
index bcf0b8a..0000000
--- a/website/0.8.0/src/site/site.xml
+++ /dev/null
@@ -1,143 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- ~ Licensed to the Apache Software Foundation (ASF) under one
- ~ or more contributor license agreements. See the NOTICE file
- ~ distributed with this work for additional information
- ~ regarding copyright ownership. The ASF licenses this file
- ~ to you under the Apache License, Version 2.0 (the
- ~ "License"); you may not use this file except in compliance
- ~ with the License. You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "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.
- -->
-<project name="Apache Helix">
- <bannerLeft>
- <src>../images/helix-logo.jpg</src>
- <href>http://helix.apache.org/</href>
- </bannerLeft>
- <bannerRight>
- <src>../images/feather_small.gif</src>
- <href>http://www.apache.org/</href>
- </bannerRight>
- <version position="none"/>
-
- <publishDate position="right"/>
-
- <skin>
- <groupId>lt.velykis.maven.skins</groupId>
- <artifactId>reflow-maven-skin</artifactId>
- <version>1.0.0</version>
- </skin>
-
- <body>
-
- <head><![CDATA[
- <script type="text/javascript">
-
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-3211522-12']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
-
- </script>
-
- ]]></head>
-
- <breadcrumbs position="left">
- <item name="Apache Helix" href="http://helix.apache.org/"/>
- <item name="Release 0.8.0" href="http://helix.apache.org/0.8.0-docs/"/>
- </breadcrumbs>
-
- <links>
- <item name="Helix 0.8.0" href="./index.html"/>
- </links>
-
- <menu name="Get Helix">
- <item name="Download" href="./download.html"/>
- <item name="Building" href="./Building.html"/>
- <item name="Release Notes" href="./releasenotes/release-0.8.0.html"/>
- </menu>
-
- <menu name="Hands-On">
- <item name="Quick Start" href="./Quickstart.html"/>
- <item name="Tutorial" href="./Tutorial.html"/>
- <item name="Javadocs" href="http://helix.apache.org/javadocs/0.8.0"/>
- </menu>
-
- <menu name="Recipes">
- <item name="Distributed lock manager" href="./recipes/lock_manager.html"/>
- <item name="Rabbit MQ consumer group" href="./recipes/rabbitmq_consumer_group.html"/>
- <item name="Rsync replicated file store" href="./recipes/rsync_replicated_file_store.html"/>
- <item name="Service discovery" href="./recipes/service_discovery.html"/>
- <item name="Distributed task DAG execution" href="./recipes/task_dag_execution.html"/>
- </menu>
-<!--
- <menu ref="reports" inherit="bottom"/>
- <menu ref="modules" inherit="bottom"/>
-
-
- <menu name="ASF">
- <item name="How Apache Works" href="http://www.apache.org/foundation/how-it-works.html"/>
- <item name="Foundation" href="http://www.apache.org/foundation/"/>
- <item name="Sponsoring Apache" href="http://www.apache.org/foundation/sponsorship.html"/>
- <item name="Thanks" href="http://www.apache.org/foundation/thanks.html"/>
- </menu>
--->
- <footer><![CDATA[
- <div class="row span16"><div>Apache Helix, Apache, the Apache feather logo, and the Apache Helix project logos are trademarks of The Apache Software Foundation.
- All other marks mentioned may be trademarks or registered trademarks of their respective owners.</div>
- <a href="${project.url}/privacy-policy.html">Privacy Policy</a>
- </div>
- ]]></footer>
-
-
- </body>
-
- <custom>
- <reflowSkin>
- <theme>site</theme>
- <localResources>true</localResources>
- <highlightJs>false</highlightJs>
- <brand>
- <name>Apache Helix</name>
- <href>http://helix.apache.org</href>
- </brand>
- <slogan>A cluster management framework for partitioned and replicated distributed resources</slogan>
- <bottomNav>
- <column>Get Helix</column>
- <column>Hands-On</column>
- <column>Recipes</column>
- </bottomNav>
- <pages>
- <index>
- <sections>
- <columns>3</columns>
- </sections>
- </index>
- </pages>
- </reflowSkin>
- <!--fluidoSkin>
- <topBarEnabled>true</topBarEnabled>
- <sideBarEnabled>true</sideBarEnabled>
- <googleSearch></googleSearch>
- <twitter>
- <user>ApacheHelix</user>
- <showUser>true</showUser>
- <showFollowers>false</showFollowers>
- </twitter>
- </fluidoSkin-->
- </custom>
-
-</project>
diff --git a/website/0.8.0/src/site/xdoc/download.xml.vm b/website/0.8.0/src/site/xdoc/download.xml.vm
deleted file mode 100644
index 5d808be..0000000
--- a/website/0.8.0/src/site/xdoc/download.xml.vm
+++ /dev/null
@@ -1,214 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
-
--->
-#set( $releaseName = "0.8.0" )
-#set( $releaseDate = "01/15/2018" )
-<document xmlns="http://maven.apache.org/XDOC/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd">
-
- <properties>
- <title>Apache Helix Downloads</title>
- <author email="dev@helix.apache.org">Apache Helix Documentation Team</author>
- </properties>
-
- <body>
- <div class="toc_container">
- <macro name="toc">
- <param name="class" value="toc"/>
- </macro>
- </div>
-
- <section name="Introduction">
- <p>Apache Helix artifacts are distributed in source and binary form under the terms of the
- <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
- See the included <tt>LICENSE</tt> and <tt>NOTICE</tt> files included in each artifact for additional license
- information.
- </p>
- <p>Use the links below to download a source distribution of Apache Helix.
- It is good practice to <a href="#Verifying_Releases">verify the integrity</a> of the distribution files.</p>
- </section>
-
- <section name="Release">
- <p>Release date: ${releaseDate} </p>
- <p><a href="releasenotes/release-${releaseName}.html">${releaseName} Release notes</a></p>
- <a name="mirror"/>
- <subsection name="Mirror">
-
- <p>
- [if-any logo]
- <a href="[link]">
- <img align="right" src="[logo]" border="0"
- alt="logo"/>
- </a>
- [end]
- The currently selected mirror is
- <b>[preferred]</b>.
- If you encounter a problem with this mirror,
- please select another mirror.
- If all mirrors are failing, there are
- <i>backup</i>
- mirrors
- (at the end of the mirrors list) that should be available.
- </p>
-
- <form action="[location]" method="get" id="SelectMirror" class="form-inline">
- Other mirrors:
- <select name="Preferred" class="input-xlarge">
- [if-any http]
- [for http]
- <option value="[http]">[http]</option>
- [end]
- [end]
- [if-any ftp]
- [for ftp]
- <option value="[ftp]">[ftp]</option>
- [end]
- [end]
- [if-any backup]
- [for backup]
- <option value="[backup]">[backup] (backup)</option>
- [end]
- [end]
- </select>
- <input type="submit" value="Change" class="btn"/>
- </form>
-
- <p>
- You may also consult the
- <a href="http://www.apache.org/mirrors/">complete list of mirrors.</a>
- </p>
-
- </subsection>
- <subsection name="${releaseName} Sources">
- <table>
- <thead>
- <tr>
- <th>Artifact</th>
- <th>Signatures</th>
- <th>Hashes</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- <a href="[preferred]helix/${releaseName}/src/helix-${releaseName}-src.zip">helix-${releaseName}-src.zip</a>
- </td>
- <td>
- <a href="http://www.apache.org/dist/helix/${releaseName}/src/helix-${releaseName}-src.zip.asc">asc</a>
- </td>
- <td>
- <a href="http://www.apache.org/dist/helix/${releaseName}/src/helix-${releaseName}-src.zip.md5">md5</a>
- <a href="http://www.apache.org/dist/helix/${releaseName}/src/helix-${releaseName}-src.zip.sha1">sha1</a>
- </td>
- </tr>
- </tbody>
- </table>
- </subsection>
- <subsection name="${releaseName} Binaries">
- <table>
- <thead>
- <tr>
- <th>Artifact</th>
- <th>Signatures</th>
- <th>Hashes</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- <a href="[preferred]helix/${releaseName}/binaries/helix-core-${releaseName}-pkg.tar">helix-core-${releaseName}-pkg.tar</a>
- </td>
- <td>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-core-${releaseName}-pkg.tar.asc">asc</a>
- </td>
- <td>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-core-${releaseName}-pkg.tar.md5">md5</a>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-core-${releaseName}-pkg.tar.sha1">sha1</a>
- </td>
- </tr>
- <tr>
- <td>
- <a href="[preferred]helix/${releaseName}/binaries/helix-admin-webapp-${releaseName}-pkg.tar">helix-admin-webapp-${releaseName}-pkg.tar</a>
- </td>
- <td>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-admin-webapp-${releaseName}-pkg.tar.asc">asc</a>
- </td>
- <td>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-admin-webapp-${releaseName}-pkg.tar.md5">md5</a>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-admin-webapp-${releaseName}-pkg.tar.sha1">sha1</a>
- </td>
- </tr>
- <tr>
- <td>
- <a href="[preferred]helix/${releaseName}/binaries/helix-agent-${releaseName}-pkg.tar">helix-agent-${releaseName}-pkg.tar</a>
- </td>
- <td>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-agent-${releaseName}-pkg.tar.asc">asc</a>
- </td>
- <td>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-agent-${releaseName}-pkg.tar.md5">md5</a>
- <a href="http://www.apache.org/dist/helix/${releaseName}/binaries/helix-agent-${releaseName}-pkg.tar.sha1">sha1</a>
- </td>
- </tr>
- </tbody>
- </table>
- </subsection>
- </section>
-
-<!-- <section name="Older Releases">
- </section>-->
-
- <section name="Verifying Releases">
- <p>It is essential that you verify the integrity of the downloaded file using the PGP signature (<tt>.asc</tt> file) or a hash (<tt>.md5</tt> or <tt>.sha1</tt> file). Please read <a href="http://www.apache.org/info/verification.html">Verifying Apache Software Foundation Releases</a> for more information on why you should verify our releases.</p>
- <p>The PGP signature can be verified using <a href="http://www.pgpi.org/">PGP</a> or <a href="http://www.gnupg.org/">GPG</a>. First download the <a href="http://www.apache.org/dist/helix/KEYS">KEYS</a> as well as the <tt>*.asc</tt> signature files for the relevant distribution. Make sure you get these files from the main distribution site, rather than from a mirror. Then verify the signatures using one of the following sets of commands:
-
- <source>% pgpk -a KEYS
-% pgpv downloaded_file.asc</source>
-
- or<br/>
-
- <source>% pgp -ka KEYS
-% pgp downloaded_file.asc</source>
-
- or<br/>
-
- <source>% gpg --import KEYS
-% gpg --verify downloaded_file.asc</source>
- </p>
- <p>Alternatively, you can verify the MD5 signature on the files. A Unix/Linux program called
- <code>md5</code> or
- <code>md5sum</code> is included in most distributions. It is also available as part of
- <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>.
- Windows users can get binary md5 programs from these (and likely other) places:
- <ul>
- <li>
- <a href="http://www.md5summer.org/">http://www.md5summer.org/</a>
- </li>
- <li>
- <a href="http://www.fourmilab.ch/md5/">http://www.fourmilab.ch/md5/</a>
- </li>
- <li>
- <a href="http://www.pc-tools.net/win32/md5sums/">http://www.pc-tools.net/win32/md5sums/</a>
- </li>
- </ul>
- </p>
- </section>
- </body>
-</document>
diff --git a/website/0.8.0/src/test/conf/testng.xml b/website/0.8.0/src/test/conf/testng.xml
deleted file mode 100644
index 4d58316..0000000
--- a/website/0.8.0/src/test/conf/testng.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- ~ Licensed to the Apache Software Foundation (ASF) under one
- ~ or more contributor license agreements. See the NOTICE file
- ~ distributed with this work for additional information
- ~ regarding copyright ownership. The ASF licenses this file
- ~ to you under the Apache License, Version 2.0 (the
- ~ "License"); you may not use this file except in compliance
- ~ with the License. You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "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.
- -->
-<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
-<suite name="Suite" parallel="none">
- <test name="Test" preserve-order="false">
- <packages>
- <package name="org.apache.helix"/>
- </packages>
- </test>
-</suite>
diff --git a/website/0.8.1/pom.xml b/website/0.8.1/pom.xml
deleted file mode 100644
index 7434308..0000000
--- a/website/0.8.1/pom.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" ?>
-<!--
- ~ Licensed to the Apache Software Foundation (ASF) under one
- ~ or more contributor license agreements. See the NOTICE file
- ~ distributed with this work for additional information
- ~ regarding copyright ownership. The ASF licenses this file
- ~ to you under the Apache License, Version 2.0 (the
- ~ "License"); you may not use this file except in compliance
- ~ with the License. You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "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.
- -->
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
- <modelVersion>4.0.0</modelVersion>
-
- <parent>
- <groupId>org.apache.helix</groupId>
- <artifactId>website</artifactId>
- <version>1.0.3-SNAPSHOT</version>
- </parent>
-
- <artifactId>0.8.1-docs</artifactId>
- <packaging>bundle</packaging>
- <name>Apache Helix :: Website :: 0.8.1</name>
-
- <properties>
- </properties>
-
- <dependencies>
- <dependency>
- <groupId>org.testng</groupId>
- <artifactId>testng</artifactId>
- <version>6.0.1</version>
- </dependency>
- </dependencies>
- <build>
- <pluginManagement>
- <plugins>
- </plugins>
- </pluginManagement>
- <plugins>
- </plugins>
- </build>
-</project>
diff --git a/website/0.8.1/src/site/apt/privacy-policy.apt b/website/0.8.1/src/site/apt/privacy-policy.apt
deleted file mode 100644
index ada9363..0000000
--- a/website/0.8.1/src/site/apt/privacy-policy.apt
+++ /dev/null
@@ -1,52 +0,0 @@
- ----
- Privacy Policy
- -----
- Olivier Lamy
- -----
- 2013-02-04
- -----
-
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "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.
-
-Privacy Policy
-
- Information about your use of this website is collected using server access logs and a tracking cookie. The
- collected information consists of the following:
-
- [[1]] The IP address from which you access the website;
-
- [[2]] The type of browser and operating system you use to access our site;
-
- [[3]] The date and time you access our site;
-
- [[4]] The pages you visit; and
-
- [[5]] The addresses of pages from where you followed a link to our site.
-
- []
-
- Part of this information is gathered using a tracking cookie set by the
- {{{http://www.google.com/analytics/}Google Analytics}} service and handled by Google as described in their
- {{{http://www.google.com/privacy.html}privacy policy}}. See your browser documentation for instructions on how to
- disable the cookie if you prefer not to share this data with Google.
-
- We use the gathered information to help us make our site more useful to visitors and to better understand how and
- when our site is used. We do not track or collect personally identifiable information or associate gathered data
- with any personally identifying information from other sources.
-
- By using this website, you consent to the collection of this data in the manner and for the purpose described above.
diff --git a/website/0.8.1/src/site/apt/releasenotes/release-0.8.1.apt b/website/0.8.1/src/site/apt/releasenotes/release-0.8.1.apt
deleted file mode 100644
index 793b683..0000000
--- a/website/0.8.1/src/site/apt/releasenotes/release-0.8.1.apt
+++ /dev/null
@@ -1,135 +0,0 @@
- -----
- Release Notes for Apache Helix 0.8.1
- -----
-
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "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.
-
-~~ NOTE: For help with the syntax of this file, see:
-~~ http://maven.apache.org/guides/mini/guide-apt-format.html
-
-Release Notes for Apache Helix 0.8.1
-
- The Apache Helix team would like to announce the release of Apache Helix 0.8.1.
-
- This is the thirteenth release under the Apache umbrella, and the ninth as a top-level project.
-
- Helix is a generic cluster management framework used for the automatic management of partitioned, replicated and distributed resources hosted on a cluster of nodes.
-
- In this release, Helix provides several performance improvements for rebalance pipeline:
-
-[]
-
-* Key Note for Helix Release
-
-** Selective Update for IdealState and CurrentState.
-
- Existing rebalance cluster data cache reload all the idealstates and current states, whichever has been changed or not. This improvement reduced the number of unnecessary read from Zookeeper and accelerated the process speed for data refresh.
-
-** Helix Callback Handling
-
- * Improve CallbackHandler by avoiding redundant re-subscription for data change event. Resubscribe to Zookeeeper changes only happened when there is any child got changed.
-
- * Add new config name for batch callback handling in CallbackHandler
-
- * Support configurable data prefetch in ZkClient during subscribe event change.
-
-** Improve rebalance pipeline computation
-
- * All the ExternalViews are produced by Helix Controller. In this case, there is no need to read these ExternalViews back from Zookeeper as Helix Controller has the latest information. One of the improvement is trying to avoid read data back from Zookeeper but cache it locally.
-
- * Anoher improvement is precomputing disabled instance set + disabled partition for instance set instead of deriving data when it is required.
-
-[]
-
-* Detailed Changes
-
-** New Features
-
- * [HELIX-684] Add health status API in ResourceAccessor
-
- * [HELIX-687] Add synchronized delete for workflows
-
- * [HELIX-688] Add method that returns start time of the most recent task scheduled
-
- * Support RoutingTableProvider for TargetExternalView
-
- * Allow to get all resources from RoutingTableProvider class
-
- * Add RoutingTableSnapshot class to hold a snapshot of routing table information and provide API to return RoutingTableSnapshot from RoutingTableProvider
-
- * Support RoutingTableChangeListener in RoutingTableProvider
-
- * Support Workflow level timeout feature
-
- * Support new API for getProperty and get that option to throw exception if one of batched get operation is failed.
-
-** Bug Fixes
-
- * [HELIX-676] Fix the issue that the controller keep updating idealstates when there is no real diff
-
- * [HELIX-681] don't fail state transition task if we fail to remove message or send out relay message
-
- * Fix issue in reporting MissingMinActiveReplicaPartitionGauge metric in ResourceMonitor when there is no IdealMapping persisted in IdealState
-
- * Fix the job parents listing logic in REST
-
- * Fix Job level timeout not timeout jobs and refactor logics
-
- * Fix allowed down instance number set to 0 does not trigger Controller entering maintenance mode
-
- * Fix a bug in AutoRebalancer that it fails to compute ideal mapping if "ANY_LIVEINSTANCE" is specified as the replica
-
- * Fix a bug when controller handles relay message timeout, and print out log when controller ignores some relay messages
-
- * Fix NPE for RoutingTableProvider listener
-
- * Fix Timeout scheduling issue.
-
-
-** Improvements
-
- * [HELIX-678] Clear controller event queue when it is shutdown or no longer the leader
-
- * [HELIX-679] consolidate semantics of recursively delete path in ZkClient
-
- * [HELIX-682] controller should delete obsolete messages with timeout to unblock state transition
-
- * [HELIX-685] Set job state to NOT_STARTED at job creation in WorkflowRebalancer
-
- * Avoid redundant calculation for disabled instances
-
- * Change RoutingTableProvider to support direct aggregating routing information from CurrentStates in each liveinstance
-
- * Retrieve cached idealMappings for all Rebalancers (AutoRebalancer, DelayedRebalancer and CustomRebalancer) for any rebalance strategies
-
- * Persist preferenceLists into TargetExternalView
-
- * Including version number in Participant and Controller history, and add additional logs
-
- * CallbackHandler to use either java config property or class annotation to enable batch callback handling
-
- * Remove empty resource entry if there is no partition disabled for this instance
-
- * Fail rebalance pipeline and retry if the data load from zookeeper fails in any read/batch-read calls.
-
-
-[]
-
-Cheers,
---
-The Apache Helix Team
diff --git a/website/0.8.1/src/site/markdown/Building.md b/website/0.8.1/src/site/markdown/Building.md
deleted file mode 100644
index d40063d..0000000
--- a/website/0.8.1/src/site/markdown/Building.md
+++ /dev/null
@@ -1,42 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-Build Instructions
-------------------
-
-### From Source
-
-Requirements: JDK 1.6+, Maven 2.0.8+
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.1
-mvn install package -DskipTests
-```
-
-### Maven Dependency
-
-```
-<dependency>
- <groupId>org.apache.helix</groupId>
- <artifactId>helix-core</artifactId>
- <version>0.8.1</version>
-</dependency>
-```
diff --git a/website/0.8.1/src/site/markdown/Features.md b/website/0.8.1/src/site/markdown/Features.md
deleted file mode 100644
index ba9d0e7..0000000
--- a/website/0.8.1/src/site/markdown/Features.md
+++ /dev/null
@@ -1,313 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Features</title>
-</head>
-
-Features
-----------------------------
-
-
-### CONFIGURING IDEALSTATE
-
-
-Read concepts page for definition of Idealstate.
-
-The placement of partitions in a DDS is very critical for reliability and scalability of the system.
-For example, when a node fails, it is important that the partitions hosted on that node are reallocated evenly among the remaining nodes. Consistent hashing is one such algorithm that can guarantee this.
-Helix by default comes with a variant of consistent hashing based of the RUSH algorithm.
-
-This means given a number of partitions, replicas and number of nodes Helix does the automatic assignment of partition to nodes such that
-
-* Each node has the same number of partitions and replicas of the same partition do not stay on the same node.
-* When a node fails, the partitions will be equally distributed among the remaining nodes
-* When new nodes are added, the number of partitions moved will be minimized along with satisfying the above two criteria.
-
-
-Helix provides multiple ways to control the placement and state of a replica.
-
-```
-
- |AUTO REBALANCE| AUTO | CUSTOM |
- -----------------------------------------
- LOCATION | HELIX | APP | APP |
- -----------------------------------------
- STATE | HELIX | HELIX | APP |
- -----------------------------------------
-```
-
-#### HELIX EXECUTION MODE
-
-
-Idealstate is defined as the state of the DDS when all nodes are up and running and healthy.
-Helix uses this as the target state of the system and computes the appropriate transitions needed in the system to bring it to a stable state.
-
-Helix supports 3 different execution modes which allows application to explicitly control the placement and state of the replica.
-
-##### AUTO_REBALANCE
-
-When the idealstate mode is set to AUTO_REBALANCE, Helix controls both the location of the replica along with the state. This option is useful for applications where creation of a replica is not expensive. Example
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO_REBALANCE",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- }
- "listFields" : {
- "MyResource_0" : [],
- "MyResource_1" : [],
- "MyResource_2" : []
- },
- "mapFields" : {
- }
-}
-```
-
-If there are 3 nodes in the cluster, then Helix will internally compute the ideal state as
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- },
- "mapFields" : {
- "MyResource_0" : {
- "N1" : "MASTER",
- "N2" : "SLAVE",
- },
- "MyResource_1" : {
- "N2" : "MASTER",
- "N3" : "SLAVE",
- },
- "MyResource_2" : {
- "N3" : "MASTER",
- "N1" : "SLAVE",
- }
- }
-}
-```
-
-Another typical example is evenly distributing a group of tasks among the currently alive processes. For example, if there are 60 tasks and 4 nodes, Helix assigns 15 tasks to each node.
-When one node fails Helix redistributes its 15 tasks to the remaining 3 nodes. Similarly, if a node is added, Helix re-allocates 3 tasks from each of the 4 nodes to the 5th node.
-
-#### AUTO
-
-When the idealstate mode is set to AUTO, Helix only controls STATE of the replicas where as the location of the partition is controlled by application. Example: The below idealstate indicates thats 'MyResource_0' must be only on node1 and node2. But gives the control of assigning the STATE to Helix.
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- }
- "listFields" : {
- "MyResource_0" : [node1, node2],
- "MyResource_1" : [node2, node3],
- "MyResource_2" : [node3, node1]
- },
- "mapFields" : {
- }
-}
-```
-In this mode when node1 fails, unlike in AUTO-REBALANCE mode the partition is not moved from node1 to others nodes in the cluster. Instead, Helix will decide to change the state of MyResource_0 in N2 based on the system constraints. For example, if a system constraint specified that there should be 1 Master and if the Master failed, then node2 will be made the new master.
-
-#### CUSTOM
-
-Helix offers a third mode called CUSTOM, in which application can completely control the placement and state of each replica. Applications will have to implement an interface that Helix will invoke when the cluster state changes.
-Within this callback, the application can recompute the idealstate. Helix will then issue appropriate transitions such that Idealstate and Currentstate converges.
-
-```
-{
- "id" : "MyResource",
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "CUSTOM",
- "NUM_PARTITIONS" : "3",
- "REPLICAS" : "2",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- },
- "mapFields" : {
- "MyResource_0" : {
- "N1" : "MASTER",
- "N2" : "SLAVE",
- },
- "MyResource_1" : {
- "N2" : "MASTER",
- "N3" : "SLAVE",
- },
- "MyResource_2" : {
- "N3" : "MASTER",
- "N1" : "SLAVE",
- }
- }
-}
-```
-
-For example, the current state of the system might be 'MyResource_0' -> {N1:MASTER,N2:SLAVE} and the application changes the ideal state to 'MyResource_0' -> {N1:SLAVE,N2:MASTER}. Helix will not blindly issue MASTER-->SLAVE to N1 and SLAVE-->MASTER to N2 in parallel since it might result in a transient state where both N1 and N2 are masters.
-Helix will first issue MASTER-->SLAVE to N1 and after its completed it will issue SLAVE-->MASTER to N2.
-
-
-### State Machine Configuration
-
-Helix comes with 3 default state models that are most commonly used. Its possible to have multiple state models in a cluster.
-Every resource that is added should have a reference to the state model.
-
-* MASTER-SLAVE: Has 3 states OFFLINE,SLAVE,MASTER. Max masters is 1. Slaves will be based on the replication factor. Replication factor can be specified while adding the resource
-* ONLINE-OFFLINE: Has 2 states OFFLINE and ONLINE. Very simple state model and most applications start off with this state model.
-* LEADER-STANDBY:1 Leader and many stand bys. In general the standby's are idle.
-
-Apart from providing the state machine configuration, one can specify the constraints of states and transitions.
-
-For example one can say
-Master:1. Max number of replicas in Master state at any time is 1.
-OFFLINE-SLAVE:5 Max number of Offline-Slave transitions that can happen concurrently in the system
-
-STATE PRIORITY
-Helix uses greedy approach to satisfy the state constraints. For example if the state machine configuration says it needs 1 master and 2 slaves but only 1 node is active, Helix must promote it to master. This behavior is achieved by providing the state priority list as MASTER,SLAVE.
-
-STATE TRANSITION PRIORITY
-Helix tries to fire as many transitions as possible in parallel to reach the stable state without violating constraints. By default Helix simply sorts the transitions alphabetically and fires as many as it can without violating the constraints.
-One can control this by overriding the priority order.
-
-### Config management
-
-Helix allows applications to store application specific properties. The configuration can have different scopes.
-
-* Cluster
-* Node specific
-* Resource specific
-* Partition specific
-
-Helix also provides notifications when any configs are changed. This allows applications to support dynamic configuration changes.
-
-See HelixManager.getConfigAccessor for more info
-
-### Intra cluster messaging api
-
-This is an interesting feature which is quite useful in practice. Often times, nodes in DDS requires a mechanism to interact with each other. One such requirement is a process of bootstrapping a replica.
-
-Consider a search system use case where the index replica starts up and it does not have an index. One of the commonly used solutions is to get the index from a common location or to copy the index from another replica.
-Helix provides a messaging api, that can be used to talk to other nodes in the system. The value added that Helix provides here is, message recipient can be specified in terms of resource,
-partition, state and Helix ensures that the message is delivered to all of the required recipients. In this particular use case, the instance can specify the recipient criteria as all replicas of P1.
-Since Helix is aware of the global state of the system, it can send the message to appropriate nodes. Once the nodes respond Helix provides the bootstrapping replica with all the responses.
-
-This is a very generic api and can also be used to schedule various periodic tasks in the cluster like data backups etc.
-System Admins can also perform adhoc tasks like on demand backup or execute a system command(like rm -rf ;-)) across all nodes.
-
-```
- ClusterMessagingService messagingService = manager.getMessagingService();
- //CONSTRUCT THE MESSAGE
- Message requestBackupUriRequest = new Message(
- MessageType.USER_DEFINE_MSG, UUID.randomUUID().toString());
- requestBackupUriRequest
- .setMsgSubType(BootstrapProcess.REQUEST_BOOTSTRAP_URL);
- requestBackupUriRequest.setMsgState(MessageState.NEW);
- //SET THE RECIPIENT CRITERIA, All nodes that satisfy the criteria will receive the message
- Criteria recipientCriteria = new Criteria();
- recipientCriteria.setInstanceName("%");
- recipientCriteria.setRecipientInstanceType(InstanceType.PARTICIPANT);
- recipientCriteria.setResource("MyDB");
- recipientCriteria.setPartition("");
- //Should be processed only the process that is active at the time of sending the message.
- //This means if the recipient is restarted after message is sent, it will not be processed.
- recipientCriteria.setSessionSpecific(true);
- // wait for 30 seconds
- int timeout = 30000;
- //The handler that will be invoked when any recipient responds to the message.
- BootstrapReplyHandler responseHandler = new BootstrapReplyHandler();
- //This will return only after all recipients respond or after timeout.
- int sentMessageCount = messagingService.sendAndWait(recipientCriteria,
- requestBackupUriRequest, responseHandler, timeout);
-```
-
-See HelixManager.getMessagingService for more info.
-
-
-### Application specific property storage
-
-There are several usecases where applications needs support for distributed data structures. Helix uses Zookeeper to store the application data and hence provides notifications when the data changes.
-One value add Helix provides is the ability to specify cache the data and also write through cache. This is more efficient than reading from ZK every time.
-
-See HelixManager.getHelixPropertyStore
-
-### Throttling
-
-Since all state changes in the system are triggered through transitions, Helix can control the number of transitions that can happen in parallel. Some of the transitions may be light weight but some might involve moving data around which is quite expensive.
-Helix allows applications to set threshold on transitions. The threshold can be set at the multiple scopes.
-
-* MessageType e.g STATE_TRANSITION
-* TransitionType e.g SLAVE-MASTER
-* Resource e.g database
-* Node i.e per node max transitions in parallel.
-
-See HelixManager.getHelixAdmin.addMessageConstraint()
-
-### Health monitoring and alerting
-
-This in currently in development mode, not yet productionized.
-
-Helix provides ability for each node in the system to report health metrics on a periodic basis.
-Helix supports multiple ways to aggregate these metrics like simple SUM, AVG, EXPONENTIAL DECAY, WINDOW. Helix will only persist the aggregated value.
-Applications can define threshold on the aggregate values according to the SLA's and when the SLA is violated Helix will fire an alert.
-Currently Helix only fires an alert but eventually we plan to use this metrics to either mark the node dead or load balance the partitions.
-This feature will be valuable in for distributed systems that support multi-tenancy and have huge variation in work load patterns. Another place this can be used is to detect skewed partitions and rebalance the cluster.
-
-This feature is not yet stable and do not recommend to be used in production.
-
-
-### Controller deployment modes
-
-Read Architecture wiki for more details on the Role of a controller. In simple words, it basically controls the participants in the cluster by issuing transitions.
-
-Helix provides multiple options to deploy the controller.
-
-#### STANDALONE
-
-Controller can be started as a separate process to manage a cluster. This is the recommended approach. How ever since one controller can be a single point of failure, multiple controller processes are required for reliability.
-Even if multiple controllers are running only one will be actively managing the cluster at any time and is decided by a leader election process. If the leader fails, another leader will resume managing the cluster.
-
-Even though we recommend this method of deployment, it has the drawback of having to manage an additional service for each cluster. See Controller As a Service option.
-
-#### EMBEDDED
-
-If setting up a separate controller process is not viable, then it is possible to embed the controller as a library in each of the participant.
-
-#### CONTROLLER AS A SERVICE
-
-One of the cool feature we added in helix was use a set of controllers to manage a large number of clusters.
-For example if you have X clusters to be managed, instead of deploying X*3(3 controllers for fault tolerance) controllers for each cluster, one can deploy only 3 controllers. Each controller can manage X/3 clusters.
-If any controller fails the remaining two will manage X/2 clusters. At LinkedIn, we always deploy controllers in this mode.
-
-
-
-
-
-
-
-
diff --git a/website/0.8.1/src/site/markdown/Metrics.md b/website/0.8.1/src/site/markdown/Metrics.md
deleted file mode 100644
index 3a67b69..0000000
--- a/website/0.8.1/src/site/markdown/Metrics.md
+++ /dev/null
@@ -1,217 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-Helix Monitoring Metrics
-------------------
-
-Helix monitoring metrics are exposed as the MBeans attributes.
-The MBeans are registered based on instance role.
-
-The easiest way to see the available metrics is using jconsole and point it at a running Helix instance.
-This will allow browsing all metrics with JMX.
-
-Note that if not mentioned in the attribute name, all attributes are gauge by default.
-
-### Metrics on Both Controller and Participant
-
-#### MBean ZkClientMonitor
-ObjectName: "HelixZkClient:type=[client-type],key=[specified-client-key],PATH=[zk-client-listening-path]"
-
-|Attributes|Description|
-|----------|-----------|
-|ReadCounter|Zk Read counter. Which could be used to identify unusually high/low ZK traffic|
-|WriteCounter|Same as above|
-|ReadBytesCounter|Same as above|
-|WriteBytesCounter|Same as above|
-|StateChangeEventCounter|Zk connection state change counter. Which could be used to identify ZkClient unstable connection|
-|DataChangeEventCounter|Zk node data change counter. which could be used to identify unusual high/low ZK events occurrence or slow event processing|
-|PendingCallbackGauge|Number of the pending Zk callbacks.|
-|TotalCallbackCounter|Number of total received Zk callbacks.|
-|TotalCallbackHandledCounter|Number of total handled Zk callbacks.|
-|ReadTotalLatencyCounter|Total read latency in ms.|
-|WriteTotalLatencyCounter|Total write latency in ms.|
-|WriteFailureCounter|Total write failures.|
-|ReadFailureCounter|Total read failures.|
-|ReadLatencyGauge|Histogram (with all statistic data) of read latency.|
-|WriteLatencyGauge|Histogram (with all statistic data) of write latency.|
-|ReadBytesGauge|Histogram (with all statistic data) of read bytes of single Zk access.|
-|WriteBytesGauge|Histogram (with all statistic data) of write bytes of single Zk access.|
-
-#### MBean HelixCallbackMonitor
-ObjectName: "HelixCallback:Type=[callback-type],Key=[cluster-name].[instance-name],Change=[callback-change-type]"
-
-|Attributes|Description|
-|----------|-----------|
-|Counter|Zk Callback counter for each Helix callback type.|
-|UnbatchedCounter|Unbatched Zk Callback counter for each helix callback type.|
-|LatencyCounter|Callback handler latency counter in ms.|
-|LatencyGauge|Histogram (with all statistic data) of Callback handler latency.|
-
-#### MBean MessageQueueMonitor
-ObjectName: "ClusterStatus:cluster=[cluster-name],messageQueue=[instance-name]"
-
-|Attributes|Description|
-|----------|-----------|
-|MessageQueueBacklog|Get the message queue size|
-
-### Metrics on Controller only
-
-#### MBean ClusterStatusMonitor
-ObjectName: "ClusterStatus:cluster=[cluster-name]"
-
-|Attributes|Description|
-|----------|-----------|
-|DisabledInstancesGauge|Current number of disabled instances|
-|DisabledPartitionsGauge|Current number of disabled partitions number|
-|DownInstanceGauge|Current down instances number|
-|InstanceMessageQueueBacklog|The sum of all message queue sizes for instances in this cluster|
-|InstancesGauge|Current live instances number|
-|MaxMessageQueueSizeGauge|The maximum message queue size across all instances including controller|
-|RebalanceFailureGauge|None 0 if previous rebalance failed unexpectedly. The Gauge will be set every time rebalance is done.|
-|RebalanceFailureCounter|The number of failures during rebalance pipeline.|
-|Enabled|1 if cluster is enabled, otherwise 0|
-|Maintenance|1 if cluster is in maintenance mode, otherwise 0|
-|Paused|1 if cluster is paused, otherwise 0|
-
-#### MBean ClusterEventMonitor
-ObjectName: "ClusterStatus:cluster=[cluster-name],eventName=ClusterEvent,phaseName=[event-handling-phase]"
-
-|Attributes|Description|
-|----------|-----------|
-|TotalDurationCounter|Total event process duration for each stage.|
-|MaxSingleDurationGauge|Max event process duration for each stage within the recent hour.|
-|EventCounter|The count of processed event in each stage.|
-|DurationGauge|Histogram (with all statistic data) of event process duration for each stage.|
-
-#### MBean InstanceMonitor
-ObjectName: "ClusterStatus:cluster=[cluster-name],instanceName=[instance-name]"
-
-|Attributes|Description|
-|----------|-----------|
-|Online|This instance is Online (1) or Offline (0)|
-|Enabled|This instance is Enabled (1) or Disabled (0)|
-|TotalMessageReceived|Number of messages sent to this instance by controller|
-|DisabledPartitions|Get the total disabled partitions number for this instance|
-
-#### MBean ResourceMonitor
-ObjectName: "ClusterStatus:cluster=[cluster-name],resourceName=[resource-name]"
-
-|Attributes|Description|
-|----------|-----------|
-|PartitionGauge|Get number of partitions of the resource in best possible ideal state for this resource|
-|ErrorPartitionGauge|Get the number of current partitions in ERORR state for this resource|
-|DifferenceWithIdealStateGauge|Get the number of how many replicas' current state are different from ideal state for this resource|
-|MissingTopStatePartitionGauge|Get the number of partitions do not have top state for this resource|
-|ExternalViewPartitionGauge|Get number of partitions in ExternalView for this resource|
-|TotalMessageReceived|Get number of messages sent to this resource by controller|
-|LoadRebalanceThrottledPartitionGauge|Get number of partitions that need load rebalance but were throttled.|
-|RecoveryRebalanceThrottledPartitionGauge|Get number of partitions that need recovery rebalance but were throttled.|
-|PendingLoadRebalancePartitionGauge|Get number of partitions that have pending load rebalance requests.|
-|PendingRecoveryRebalancePartitionGauge|Get number of partitions that have pending recovery rebalance requests.|
-|MissingReplicaPartitionGauge|Get number of partitions that have replica number smaller than expected.|
-|MissingMinActiveReplicaPartitionGauge|Get number of partitions that have replica number smaller than the minimum requirement.|
-|MaxSinglePartitionTopStateHandoffDurationGauge|Get the max duration recorded when the top state is missing in any single partition.|
-|FailedTopStateHandoffCounter| Get the number of total top state transition failure.|
-|SucceededTopStateHandoffCounter|Get the number of total top state transition done successfully.|
-|SuccessfulTopStateHandoffDurationCounter|Get the total duration of all top state transitions.|
-|PartitionTopStateHandoffDurationGauge|Histogram (with all statistic data) of top state transition duration.|
-
-#### MBean PerInstanceResourceMonitor
-ObjectName: "ClusterStatus:cluster=[cluster-name],instanceName=[instance-name],resourceName=[resource-name]"
-
-|Attributes|Description|
-|----------|-----------|
-|PartitionGauge|Get number of partitions of the resource in best possible ideal state for this resource on specific instance|
-
-#### MBean JobMonitor
-ObjectName: "ClusterStatus:cluster=[cluster-name],jobType=[job-type]"
-
-|Attributes|Description|
-|----------|-----------|
-|SuccessfulJobCount|Get number of the succeeded jobs|
-|FailedJobCount|Get number of failed jobs|
-|AbortedJobCount|Get number of the aborted jobs|
-|ExistingJobGauge|Get number of existing jobs registered|
-|QueuedJobGauge|Get numbers of queued jobs, which are not running jobs|
-|RunningJobGauge|Get numbers of running jobs|
-|MaximumJobLatencyGauge|Get maximum latency of jobs running time. It will be cleared every hour|
-|JobLatencyCount|Get total job latency counter.|
-
-#### MBean WorkflowMonitor
-ObjectName: "ClusterStatus:cluster=[cluster-name],workflowType=[workflow-type]"
-
-|Attributes|Description|
-|----------|-----------|
-|SuccessfulWorkflowCount|Get number of succeeded workflows|
-|FailedWorkflowCount|Get number of failed workflows|
-|FailedWorkflowGauge|Get number of current failed workflows|
-|ExistingWorkflowGauge|Get number of current existing workflows|
-|QueuedWorkflowGauge|Get number of queued but not started workflows|
-|RunningWorkflowGauge|Get number of running workflows|
-|WorkflowLatencyCount|Get workflow latency count|
-|MaximumWorkflowLatencyGauge|Get maximum workflow latency gauge. It will be reset in 1 hour.|
-
-### Metrics on Participant only
-
-#### MBean StateTransitionStatMonitor
-ObjectName: "CLMParticipantReport:Cluster=[cluster-name],Resource=[resource-name],Transition=[transaction-id]"
-
-|Attributes|Description|
-|----------|-----------|
-|TotalStateTransitionGauge|Get the number of total state transitions|
-|TotalFailedTransitionGauge|Get the number of total failed state transitions|
-|TotalSuccessTransitionGauge|Get the number of total succeeded state transitions|
-|MeanTransitionLatency|Get the average state transition latency (from message read to finish)|
-|MaxTransitionLatency|Get the maximum state transition latency|
-|MinTransitionLatency|Get the minimum state transition latency|
-|PercentileTransitionLatency|Get the percentile of state transitions latency|
-|MeanTransitionExecuteLatency|Get the average execution latency of state transition (from task started to finish)|
-|MaxTransitionExecuteLatency|Get the maximum execution latency of state transition|
-|MinTransitionExecuteLatency|Get the minimum execution latency of state transition|
-|PercentileTransitionExecuteLatency|Get the percentile of execution latency of state transitions|
-
-#### MBean ThreadPoolExecutorMonitor
-ObjectName: "HelixThreadPoolExecutor:Type=[threadpool-type]" (threadpool-type in Message.MessageType, BatchMessageExecutor, Task)
-
-|Attributes|Description|
-|----------|-----------|
-|ThreadPoolCoreSizeGauge|Thread pool size is as configured. Aggregate total thread pool size for the whole cluster.|
-|ThreadPoolMaxSizeGauge|Same as above|
-|NumOfActiveThreadsGauge|Number of running threads.|
-|QueueSizeGauge|Queue size. Could be used to identify if too many HelixTask blocked in participant.|
-
-#### MBean MessageLatencyMonitor
-ObjectName: "CLMParticipantReport:ParticipantName=[instance-name],MonitorType=MessageLatencyMonitor"
-
-|Attributes|Description|
-|----------|-----------|
-|TotalMessageCount|Total message count|
-|TotalMessageLatency|Total message latency in ms|
-|MessagelatencyGauge|Histogram (with all statistic data) of message processing latency.|
-
-#### MBean ParticipantMessageMonitor
-ObjectName: "CLMParticipantReport:ParticipantName=[instance-name]"
-
-|Attributes|Description|
-|----------|-----------|
-|ReceivedMessages|Number of received messages|
-|DiscardedMessages|Number of discarded messages|
-|CompletedMessages|Number of completed messages|
-|FailedMessages|Number of failed messages|
-|PendingMessages|Number of pending messages to be processed|
diff --git a/website/0.8.1/src/site/markdown/Quickstart.md b/website/0.8.1/src/site/markdown/Quickstart.md
deleted file mode 100644
index d736a17..0000000
--- a/website/0.8.1/src/site/markdown/Quickstart.md
+++ /dev/null
@@ -1,663 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Quickstart</title>
-</head>
-
-Quickstart
----------
-
-Get Helix
----------
-
-First, let\'s get Helix. Either build it, or download it.
-
-### Build
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.1
-mvn install package -DskipTests
-cd helix-core/target/helix-core-pkg/bin # This folder contains all the scripts used in following sections
-chmod +x *
-```
-
-### Download
-
-Download the 0.8.1 release package [here](./download.html)
-
-Overview
---------
-
-In this Quickstart, we\'ll set up a master-slave replicated, partitioned system. Then we\'ll demonstrate how to add a node, rebalance the partitions, and show how Helix manages failover.
-
-
-Let\'s Do It
-------------
-
-Helix provides command line interfaces to set up the cluster and view the cluster state. The best way to understand how Helix views a cluster is to build a cluster.
-
-### Get to the Tools Directory
-
-If you built the code:
-
-```
-cd helix/helix/helix-core/target/helix-core-pkg/bin
-```
-
-If you downloaded the release package, extract it.
-
-
-Short Version
--------------
-You can observe the components working together in this demo, which does the following:
-
-* Create a cluster
-* Add 2 nodes (participants) to the cluster
-* Set up a resource with 6 partitions and 2 replicas: 1 Master, and 1 Slave per partition
-* Show the cluster state after Helix balances the partitions
-* Add a third node
-* Show the cluster state. Note that the third node has taken mastership of 2 partitions.
-* Kill the third node (Helix takes care of failover)
-* Show the cluster state. Note that the two surviving nodes take over mastership of the partitions from the failed node
-
-### Run the Demo
-
-```
-cd helix/helix/helix-core/target/helix-core-pkg/bin
-./quickstart.sh
-```
-
-#### The Initial Setup
-
-2 nodes are set up and the partitions are rebalanced.
-
-The cluster state is as follows:
-
-```
-CLUSTER STATE: After starting 2 nodes
- localhost_12000 localhost_12001
-MyResource_0 M S
-MyResource_1 S M
-MyResource_2 M S
-MyResource_3 M S
-MyResource_4 S M
-MyResource_5 S M
-```
-
-Note there is one master and one slave per partition.
-
-#### Add a Node
-
-A third node is added and the cluster is rebalanced.
-
-The cluster state changes to:
-
-```
-CLUSTER STATE: After adding a third node
- localhost_12000 localhost_12001 localhost_12002
-MyResource_0 S M S
-MyResource_1 S S M
-MyResource_2 M S S
-MyResource_3 S S M
-MyResource_4 M S S
-MyResource_5 S M S
-```
-
-Note there is one master and _two_ slaves per partition. This is expected because there are three nodes.
-
-#### Kill a Node
-
-Finally, a node is killed to simulate a failure
-
-Helix makes sure each partition has a master. The cluster state changes to:
-
-```
-CLUSTER STATE: After the 3rd node stops/crashes
- localhost_12000 localhost_12001 localhost_12002
-MyResource_0 S M -
-MyResource_1 S M -
-MyResource_2 M S -
-MyResource_3 M S -
-MyResource_4 M S -
-MyResource_5 S M -
-```
-
-
-Long Version
-------------
-Now you can run the same steps by hand. In this detailed version, we\'ll do the following:
-
-* Define a cluster
-* Add two nodes to the cluster
-* Add a 6-partition resource with 1 master and 2 slave replicas per partition
-* Verify that the cluster is healthy and inspect the Helix view
-* Expand the cluster: add a few nodes and rebalance the partitions
-* Failover: stop a node and verify the mastership transfer
-
-### Install and Start ZooKeeper
-
-Zookeeper can be started in standalone mode or replicated mode.
-
-More information is available at
-
-* http://zookeeper.apache.org/doc/r3.3.3/zookeeperStarted.html
-* http://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#sc_zkMulitServerSetup
-
-In this example, let\'s start zookeeper in local mode.
-
-#### Start ZooKeeper Locally on Port 2199
-
-```
-./start-standalone-zookeeper.sh 2199 &
-```
-
-### Define the Cluster
-
-The helix-admin tool is used for cluster administration tasks. In the Quickstart, we\'ll use the command line interface. Helix supports a REST interface as well.
-
-zookeeper_address is of the format host:port e.g localhost:2199 for standalone or host1:port,host2:port for multi-node.
-
-Next, we\'ll set up a cluster MYCLUSTER cluster with these attributes:
-
-* 3 instances running on localhost at ports 12913,12914,12915
-* One database named myDB with 6 partitions
-* Each partition will have 3 replicas with 1 master, 2 slaves
-* ZooKeeper running locally at localhost:2199
-
-#### Create the Cluster MYCLUSTER
-
-```
-# ./helix-admin.sh --zkSvr <zk_address> --addCluster <clustername>
-./helix-admin.sh --zkSvr localhost:2199 --addCluster MYCLUSTER
-```
-
-### Add Nodes to the Cluster
-
-In this case we\'ll add three nodes: localhost:12913, localhost:12914, localhost:12915
-
-```
-# helix-admin.sh --zkSvr <zk_address> --addNode <clustername> <host:port>
-./helix-admin.sh --zkSvr localhost:2199 --addNode MYCLUSTER localhost:12913
-./helix-admin.sh --zkSvr localhost:2199 --addNode MYCLUSTER localhost:12914
-./helix-admin.sh --zkSvr localhost:2199 --addNode MYCLUSTER localhost:12915
-```
-
-### Define the Resource and Partitioning
-
-In this example, the resource is a database, partitioned 6 ways. Note that in a production system, it\'s common to over-partition for better load balancing. Helix has been used in production to manage hundreds of databases each with 10s or 100s of partitions running on 10s of physical nodes.
-
-#### Create a Database with 6 Partitions using the MasterSlave State Model
-
-Helix ensures there will be exactly one master for each partition.
-
-```
-# helix-admin.sh --zkSvr <zk_address> --addResource <clustername> <resourceName> <numPartitions> <StateModelName>
-./helix-admin.sh --zkSvr localhost:2199 --addResource MYCLUSTER myDB 6 MasterSlave
-```
-
-#### Let Helix Assign Partitions to Nodes
-
-This command will distribute the partitions amongst all the nodes in the cluster. In this example, each partition has 3 replicas.
-
-```
-# helix-admin.sh --zkSvr <zk_address> --rebalance <clustername> <resourceName> <replication factor>
-./helix-admin.sh --zkSvr localhost:2199 --rebalance MYCLUSTER myDB 3
-```
-
-Now the cluster is defined in ZooKeeper. The nodes (localhost:12913, localhost:12914, localhost:12915) and resource (myDB, with 6 partitions using the MasterSlave model) are all properly configured. And the _IdealState_ has been calculated, assuming a replication factor of 3.
-
-### Start the Helix Controller
-
-Now that the cluster is defined in ZooKeeper, the Helix controller can manage the cluster.
-
-```
-# Start the cluster manager, which will manage MYCLUSTER
-./run-helix-controller.sh --zkSvr localhost:2199 --cluster MYCLUSTER 2>&1 > /tmp/controller.log &
-```
-
-### Start up the Cluster to be Managed
-
-We\'ve started up ZooKeeper, defined the cluster, the resources, the partitioning, and started up the Helix controller. Next, we\'ll start up the nodes of the system to be managed. Each node is a Participant, which is an instance of the system component to be managed. Helix assigns work to Participants, keeps track of their roles and health, and takes action when a node fails.
-
-```
-# 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 12913 --stateModelType MasterSlave 2>&1 > /tmp/participant_12913.log
-./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12914 --stateModelType MasterSlave 2>&1 > /tmp/participant_12914.log
-./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12915 --stateModelType MasterSlave 2>&1 > /tmp/participant_12915.log
-```
-
-### Inspect the Cluster
-
-Now, let\'s see the Helix view of our cluster. We\'ll work our way down as follows:
-
-```
-Clusters -> MYCLUSTER -> instances -> instance detail
- -> resources -> resource detail
- -> partitions
-```
-
-A single Helix controller can manage multiple clusters, though so far, we\'ve only defined one cluster. Let\'s see:
-
-```
-# List existing clusters
-./helix-admin.sh --zkSvr localhost:2199 --listClusters
-
-Existing clusters:
-MYCLUSTER
-```
-
-Now, let\'s see the Helix view of MYCLUSTER:
-
-```
-# helix-admin.sh --zkSvr <zk_address> --listClusterInfo <clusterName>
-./helix-admin.sh --zkSvr localhost:2199 --listClusterInfo MYCLUSTER
-
-Existing resources in cluster MYCLUSTER:
-myDB
-Instances in cluster MYCLUSTER:
-localhost_12915
-localhost_12914
-localhost_12913
-```
-
-Let\'s look at the details of an instance:
-
-```
-# ./helix-admin.sh --zkSvr <zk_address> --listInstanceInfo <clusterName> <InstanceName>
-./helix-admin.sh --zkSvr localhost:2199 --listInstanceInfo MYCLUSTER localhost_12913
-
-InstanceConfig: {
- "id" : "localhost_12913",
- "mapFields" : {
- },
- "listFields" : {
- },
- "simpleFields" : {
- "HELIX_ENABLED" : "true",
- "HELIX_HOST" : "localhost",
- "HELIX_PORT" : "12913"
- }
-}
-```
-
-
-#### Query Information about a Resource
-
-```
-# helix-admin.sh --zkSvr <zk_address> --listResourceInfo <clusterName> <resourceName>
-./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo MYCLUSTER myDB
-
-IdealState for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- },
- "myDB_1" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "MASTER"
- },
- "myDB_4" : {
- "localhost_12913" : "MASTER",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- "myDB_0" : [ "localhost_12914", "localhost_12913", "localhost_12915" ],
- "myDB_1" : [ "localhost_12915", "localhost_12913", "localhost_12914" ],
- "myDB_2" : [ "localhost_12913", "localhost_12915", "localhost_12914" ],
- "myDB_3" : [ "localhost_12915", "localhost_12913", "localhost_12914" ],
- "myDB_4" : [ "localhost_12913", "localhost_12914", "localhost_12915" ],
- "myDB_5" : [ "localhost_12914", "localhost_12915", "localhost_12913" ]
- },
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "REBALANCE_MODE" : "SEMI_AUTO",
- "NUM_PARTITIONS" : "6",
- "REPLICAS" : "3",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- "STATE_MODEL_FACTORY_NAME" : "DEFAULT"
- }
-}
-
-ExternalView for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- },
- "myDB_1" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "MASTER"
- },
- "myDB_4" : {
- "localhost_12913" : "MASTER",
- "localhost_12914" : "SLAVE",
- "localhost_12915" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- },
- "simpleFields" : {
- "BUCKET_SIZE" : "0"
- }
-}
-```
-
-Now, let\'s look at one of the partitions:
-
-```
-# helix-admin.sh --zkSvr <zk_address> --listResourceInfo <clusterName> <partition>
-./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo mycluster myDB_0
-```
-
-### Expand the Cluster
-
-Next, we\'ll show how Helix does the work that you\'d otherwise have to build into your system. When you add capacity to your cluster, you want the work to be evenly distributed. In this example, we started with 3 nodes, with 6 partitions. The partitions were evenly balanced, 2 masters and 4 slaves per node. Let\'s add 3 more nodes: localhost:12916, localhost:12917, localhost:12918
-
-```
-./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
-```
-
-And start up these instances:
-
-```
-# 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>&1 > /tmp/participant_12916.log
-./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12917 --stateModelType MasterSlave 2>&1 > /tmp/participant_12917.log
-./start-helix-participant.sh --zkSvr localhost:2199 --cluster MYCLUSTER --host localhost --port 12918 --stateModelType MasterSlave 2>&1 > /tmp/participant_12918.log
-```
-
-
-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.
-
-```
-./helix-admin.sh --zkSvr localhost:2199 --rebalance MYCLUSTER myDB 3
-```
-
-### View the Cluster
-
-OK, let\'s see how it looks:
-
-
-```
-./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo MYCLUSTER myDB
-
-IdealState for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_1" : {
- "localhost_12916" : "SLAVE",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12915" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_4" : {
- "localhost_12916" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- "myDB_0" : [ "localhost_12917", "localhost_12913", "localhost_12914" ],
- "myDB_1" : [ "localhost_12918", "localhost_12917", "localhost_12916" ],
- "myDB_2" : [ "localhost_12913", "localhost_12917", "localhost_12918" ],
- "myDB_3" : [ "localhost_12915", "localhost_12917", "localhost_12918" ],
- "myDB_4" : [ "localhost_12916", "localhost_12917", "localhost_12918" ],
- "myDB_5" : [ "localhost_12914", "localhost_12915", "localhost_12913" ]
- },
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "REBALANCE_MODE" : "SEMI_AUTO",
- "NUM_PARTITIONS" : "6",
- "REPLICAS" : "3",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- "STATE_MODEL_FACTORY_NAME" : "DEFAULT"
- }
-}
-
-ExternalView for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_1" : {
- "localhost_12916" : "SLAVE",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12915" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_4" : {
- "localhost_12916" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- },
- "simpleFields" : {
- "BUCKET_SIZE" : "0"
- }
-}
-```
-
-Mission accomplished. The partitions are nicely balanced.
-
-### How about Failover?
-
-Building a fault tolerant system isn\'t trivial, but with Helix, it\'s easy. Helix detects a failed instance, and triggers mastership transfer automatically.
-
-First, let's fail an instance. In this example, we\'ll kill localhost:12918 to simulate a failure.
-
-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:
-
-
-```
-./helix-admin.sh --zkSvr localhost:2199 --listResourceInfo MYCLUSTER myDB
-
-IdealState for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_1" : {
- "localhost_12916" : "SLAVE",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12915" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_4" : {
- "localhost_12916" : "MASTER",
- "localhost_12917" : "SLAVE",
- "localhost_12918" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- "myDB_0" : [ "localhost_12917", "localhost_12913", "localhost_12914" ],
- "myDB_1" : [ "localhost_12918", "localhost_12917", "localhost_12916" ],
- "myDB_2" : [ "localhost_12913", "localhost_12918", "localhost_12917" ],
- "myDB_3" : [ "localhost_12915", "localhost_12918", "localhost_12917" ],
- "myDB_4" : [ "localhost_12916", "localhost_12917", "localhost_12918" ],
- "myDB_5" : [ "localhost_12914", "localhost_12915", "localhost_12913" ]
- },
- "simpleFields" : {
- "IDEAL_STATE_MODE" : "AUTO",
- "REBALANCE_MODE" : "SEMI_AUTO",
- "NUM_PARTITIONS" : "6",
- "REPLICAS" : "3",
- "STATE_MODEL_DEF_REF" : "MasterSlave",
- "STATE_MODEL_FACTORY_NAME" : "DEFAULT"
- }
-}
-
-ExternalView for myDB:
-{
- "id" : "myDB",
- "mapFields" : {
- "myDB_0" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_1" : {
- "localhost_12916" : "SLAVE",
- "localhost_12917" : "MASTER"
- },
- "myDB_2" : {
- "localhost_12913" : "MASTER",
- "localhost_12917" : "SLAVE"
- },
- "myDB_3" : {
- "localhost_12915" : "MASTER",
- "localhost_12917" : "SLAVE"
- },
- "myDB_4" : {
- "localhost_12916" : "MASTER",
- "localhost_12917" : "SLAVE"
- },
- "myDB_5" : {
- "localhost_12913" : "SLAVE",
- "localhost_12914" : "MASTER",
- "localhost_12915" : "SLAVE"
- }
- },
- "listFields" : {
- },
- "simpleFields" : {
- "BUCKET_SIZE" : "0"
- }
-}
-```
-
-As we\'ve seen in this Quickstart, Helix takes care of partitioning, load balancing, elasticity, failure detection and recovery.
-
-### ZooInspector
-
-You can view all of the underlying data by going direct to zookeeper. Use ZooInspector that comes with zookeeper to browse the data. This is a java applet (make sure you have X windows)
-
-To start zooinspector run the following command from <zk_install_directory>/contrib/ZooInspector
-
-```
-java -cp zookeeper-3.3.3-ZooInspector.jar:lib/jtoaster-1.0.4.jar:../../lib/log4j-1.2.15.jar:../../zookeeper-3.3.3.jar org.apache.zookeeper.inspector.ZooInspector
-```
-
-### Next
-
-Now that you understand the idea of Helix, read the [tutorial](./Tutorial.html) to learn how to choose the right state model and constraints for your system, and how to implement it. In many cases, the built-in features meet your requirements. And best of all, Helix is a customizable framework, so you can plug in your own behavior, while retaining the automation provided by Helix.
-
diff --git a/website/0.8.1/src/site/markdown/Tutorial.md b/website/0.8.1/src/site/markdown/Tutorial.md
deleted file mode 100644
index d487d99..0000000
--- a/website/0.8.1/src/site/markdown/Tutorial.md
+++ /dev/null
@@ -1,207 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Tutorial</title>
-</head>
-
-# Helix Tutorial
-
-In this tutorial, we will cover the roles of a Helix-managed cluster, and show the code you need to write to integrate with it. In many cases, there is a simple default behavior that is often appropriate, but you can also customize the behavior.
-
-Convention: we first cover the _basic_ approach, which is the easiest to implement. Then, we'll describe _advanced_ options, which give you more control over the system behavior, but require you to write more code.
-
-
-### Prerequisites
-
-1. Read [Concepts/Terminology](../Concepts.html) and [Architecture](../Architecture.html)
-2. Read the [Quickstart guide](./Quickstart.html) to learn how Helix models and manages a cluster
-3. Install Helix source. See: [Quickstart](./Quickstart.html) for the steps.
-
-### Tutorial Outline
-
-1. [Participant](./tutorial_participant.html)
-2. [Spectator](./tutorial_spectator.html)
-3. [Controller](./tutorial_controller.html)
-4. [Rebalancing Algorithms](./tutorial_rebalance.html)
-5. [User-Defined Rebalancing](./tutorial_user_def_rebalancer.html)
-6. [State Machines](./tutorial_state.html)
-7. [Messaging](./tutorial_messaging.html)
-8. [Customized health check](./tutorial_health.html)
-9. [Throttling](./tutorial_throttling.html)
-10. [Application Property Store](./tutorial_propstore.html)
-11. [Admin Interface](./tutorial_admin.html)
-12. [YAML Cluster Setup](./tutorial_yaml.html)
-13. [Helix Agent (for non-JVM systems)](./tutorial_agent.html)
-14. [Task Framework](./tutorial_task_framework.html)
- 1. [Task with User Defined Content Store](./tutorial_user_content_store.html)
- 2. [Task Throttling](./tutorial_task_throttling.html)
-15. [Helix REST Service 2.0](./tutorial_rest_service.html)
-16. [Helix UI Setup](./tutorial_ui.html)
-
-### Preliminaries
-
-First, we need to set up the system. Let\'s walk through the steps in building a distributed system using Helix.
-
-#### Start ZooKeeper
-
-This starts a zookeeper in standalone mode. For production deployment, see [Apache ZooKeeper](http://zookeeper.apache.org) for instructions.
-
-```
-./start-standalone-zookeeper.sh 2199 &
-```
-
-#### Create a Cluster
-
-Creating a cluster will define the cluster in appropriate znodes on ZooKeeper.
-
-Using the Java API:
-
-```
-// Create setup tool instance
-// Note: ZK_ADDRESS is the host:port of Zookeeper
-String ZK_ADDRESS = "localhost:2199";
-admin = new ZKHelixAdmin(ZK_ADDRESS);
-
-String CLUSTER_NAME = "helix-demo";
-//Create cluster namespace in zookeeper
-admin.addCluster(CLUSTER_NAME);
-```
-
-OR
-
-Using the command-line interface:
-
-```
-./helix-admin.sh --zkSvr localhost:2199 --addCluster helix-demo
-```
-
-
-#### Configure the Nodes of the Cluster
-
-First we\'ll add new nodes to the cluster, then configure the nodes in the cluster. Each node in the cluster must be uniquely identifiable.
-The most commonly used convention is hostname:port.
-
-```
-String CLUSTER_NAME = "helix-demo";
-int NUM_NODES = 2;
-String hosts[] = new String[]{"localhost","localhost"};
-String ports[] = new String[]{7000,7001};
-for (int i = 0; i < NUM_NODES; i++)
-{
- InstanceConfig instanceConfig = new InstanceConfig(hosts[i]+ "_" + ports[i]);
- instanceConfig.setHostName(hosts[i]);
- instanceConfig.setPort(ports[i]);
- instanceConfig.setInstanceEnabled(true);
-
- //Add additional system specific configuration if needed. These can be accessed during the node start up.
- instanceConfig.getRecord().setSimpleField("key", "value");
- admin.addInstance(CLUSTER_NAME, instanceConfig);
-}
-```
-
-#### Configure the Resource
-
-A __resource__ represents the actual task performed by the nodes. It can be a database, index, topic, queue or any other processing entity.
-A resource can be divided into many sub-parts known as __partitions__.
-
-
-##### Define the State Model and Constraints
-
-For scalability and fault tolerance, each partition can have one or more replicas.
-The __state model__ allows one to declare the system behavior by first enumerating the various STATES, and the TRANSITIONS between them.
-A simple model is ONLINE-OFFLINE where ONLINE means the task is active and OFFLINE means it\'s not active.
-You can also specify how many replicas must be in each state, these are known as __constraints__.
-For example, in a search system, one might need more than one node serving the same index to handle the load.
-
-The allowed states:
-
-* MASTER
-* SLAVE
-* OFFLINE
-
-The allowed transitions:
-
-* OFFLINE to SLAVE
-* SLAVE to OFFLINE
-* SLAVE to MASTER
-* MASTER to SLAVE
-
-The constraints:
-
-* no more than 1 MASTER per partition
-* the rest of the replicas should be slaves
-
-The following snippet shows how to declare the state model and constraints for the MASTER-SLAVE model.
-
-```
-StateModelDefinition.Builder builder = new StateModelDefinition.Builder(STATE_MODEL_NAME);
-
-// Add states and their rank to indicate priority. A lower rank corresponds to a higher priority
-builder.addState(MASTER, 1);
-builder.addState(SLAVE, 2);
-builder.addState(OFFLINE);
-
-// Set the initial state when the node starts
-builder.initialState(OFFLINE);
-
-// Add transitions between the states.
-builder.addTransition(OFFLINE, SLAVE);
-builder.addTransition(SLAVE, OFFLINE);
-builder.addTransition(SLAVE, MASTER);
-builder.addTransition(MASTER, SLAVE);
-
-// set constraints on states
-
-// static constraint: upper bound of 1 MASTER
-builder.upperBound(MASTER, 1);
-
-// dynamic constraint: R means it should be derived based on the replication factor for the cluster
-// this allows a different replication factor for each resource without
-// having to define a new state model
-
-builder.dynamicUpperBound(SLAVE, "R");
-
-StateModelDefinition statemodelDefinition = builder.build();
-admin.addStateModelDef(CLUSTER_NAME, STATE_MODEL_NAME, myStateModel);
-```
-
-##### Assigning Partitions to Nodes
-
-The final goal of Helix is to ensure that the constraints on the state model are satisfied.
-Helix does this by assigning a __state__ to a partition (such as MASTER, SLAVE), and placing it on a particular node.
-
-There are 3 assignment modes Helix can operate in:
-
-* FULL_AUTO: Helix decides the placement and state of a partition.
-* SEMI_AUTO: Application decides the placement but Helix decides the state of a partition.
-* CUSTOMIZED: Application controls the placement and state of a partition.
-
-For more information on the assignment modes, see the [Rebalancing Algorithms](./tutorial_rebalance.html) section of this tutorial.
-
-```
-String RESOURCE_NAME = "MyDB";
-int NUM_PARTITIONS = 6;
-STATE_MODEL_NAME = "MasterSlave";
-String MODE = "SEMI_AUTO";
-int NUM_REPLICAS = 2;
-
-admin.addResource(CLUSTER_NAME, RESOURCE_NAME, NUM_PARTITIONS, STATE_MODEL_NAME, MODE);
-admin.rebalance(CLUSTER_NAME, RESOURCE_NAME, NUM_REPLICAS);
-```
diff --git a/website/0.8.1/src/site/markdown/design_crushed.md b/website/0.8.1/src/site/markdown/design_crushed.md
deleted file mode 100644
index db755f6..0000000
--- a/website/0.8.1/src/site/markdown/design_crushed.md
+++ /dev/null
@@ -1,173 +0,0 @@
-CrushED (Crush-based rebalancer with Even Distribution)
-============================================
-
-## Overview
-
-Helix provides AutoRebalanceStrategy which is based on card dealing strategy. This strategy takes the current mapping as an input, and computes new mappings only for the partitions that need to be moved. This provides minimum partition movement, but the mapping is not deterministic, and moreover, fault-zone aware mapping (i.e. rack-aware partitioning) is not possible.
-
-CRUSH-based partitioning scheme was implemented to provide fault-zone aware mapping and deterministic partition assignment. CrushRebalanceStrategy (and MultiRoundCrushRebalanceStrategy) algorithm uses pseudo-random partition placement to ensure consistent partition distribution. As the number of placed items (i.e partitions) approaches infinity, the distribution will be perfectly uniform. However, with a small number of placed items, especially for resources (i.e. databases) with a small [...]
-
-We want to provide a new rebalance strategy that provides a deterministic and fault-zone aware mapping while providing even partition distribution in all cases. In this document, we propose a hybrid algorithm that uses CRUSH, card dealing strategy, and consistent hashing to ensure both even distribution and minimal partition movement (while cluster topology remains the same). We call it CrushED (Crush w/ Even Distribution). Compared to CRUSH, CrushED results in a much more uniform distri [...]
-
-## Design
-
-In addition to what we already achieved in CrushRebalanceStrategy, we have 2 high level goals :
-
-1. Even distribution.
-2. Minimize partition movements when instances go up/down.
-
-CrushRebalanceStrategy has very small movement count, but the distribution is not optimal. MultiRoundCrushRebalanceStrategy was designed to solve this problem by running CRUSH multiple times on partition assignments that contribute to uneven mapping. However, due to potentially high number of rounds, computation cost is high, we observed significantly more partition movements when the cluster topology is changed.
-
-Since we have a good base strategy, CrushRebalanceStrategy, we built CrushEDRebalanceStrategy on top of it. Sample mapping of both strategies are as following. Note that blue parts remain unchanged before and after.
-
-Before (CRUSH)
-
-
-
-After (new strategy)
-
-
-
-Since the problem is NP-hard. We are not expecting the best assignment. A greedy algorithm works good enough.
-After we tried different designs, we found it's hard to achieve both goals (even distribution and fewer movements) using a single strategy. So we decided to apply a hybrid algorithm that finishes the work step by step.
-
-**Step 1, run CRUSH to get a base assignment.**
-The base assignment usually contains a certain number of uneven partitions(i.e. extra partitions above perfect distribution), so we need the following steps to re-distribute them.
-
-**Step 2, run a card dealing algorithm on the uneven parts.**
-Assign extra partitions to under-loaded nodes, using card dealing strategy. This algorithm is conceptually simple. The result ensures that all partitions are assigned to instances with minimum difference. When gauranteeing fault-zone safe assignment, our greedy algorithm may not be able to calculate possible results because of fault-zone conflict.
-
-Example of assignments after step 2,
-
-
-
-**Step 3, Shuffle partitions' preference lists.**
-State assignments (i.e. Master, Slave, Online, Offline, etc) are made according to preflist, ordered node. When using randomly ordered lists, State assignment is also random, and it may result in uneven state distribution. To resolve this issue, CrushED assigns scores to nodes as it computes pref list, to give all nodes equal chances in appearing at the top of the pref list. This operation results in a much more even state distribution.
-
-Example of master distribution before step 3,
-
-
-
-Example of master distribution after step 3,
-
-
-
-**Step 4, re-calculate the assignment for the partitions on temporarily disabled nodes using a consistent hashing algorithm.**
-Consistent hashing ensures minimize partition movement.
-Note that the first 3 steps are using full node list, regardless of disabled or offline nodes. So the assignment will be stable even the algorithm contains random factors such hashCode. Then step 4 ensures all the disabled nodes are handled correctly without causing huge partition movements.
-
-Pseudocode of above algorithm is as follows :
-
-**Pseudo Code**
-
- // Round 1: Calculate mapping using the base strategy.
- // Note to use all nodes for minimizing the influence of live node changes.
- origPartitionMap = getBaseRebalanceStrategy().computePartitionAssignment(allNodes, clusterData);
-
- // Transform current assignment to instance->partitions map, and get total partitions
- nodeToPartitionMap = convertMap(origPartitionMap);
-
- // Round 2: Rebalance mapping using card dealing algorithm.
- Topology allNodeTopo = new Topology(allNodes, clusterData);
- cardDealer.computeMapping(allNodeTopo, nodeToPartitionMap);
-
- // Since states are assigned according to preference list order, shuffle preference list for even states distribution.
- shufflePreferenceList(nodeToPartitionMap);
-
- // Round 3: Re-mapping the partitions on non-live nodes using consistent hashing for reducing movement.
- // Consistent hashing ensures minimum movements when nodes are disabled unexpectedly.
- if (!liveNodes.containsAll(allNodes)) {
- Topology liveNodeTopo = new Topology(liveNodes, clusterData);
- hashPlacement.computeMapping(liveNodeTopo, nodeToPartitionMap);
- }
-
- if (!nodeToPartitionMap.isEmpty()) {
- // Round 2 and 3 is done successfully
- return convertMap(nodeToPartitionMap);
- } else {
- return getBaseRebalanceStrategy().computePartitionAssignment(liveNodes, clusterData);
- }
-
-
-### Maximum uneven partition assignment using CrushED
-
-Helix cluster typically manages 1 or more resources (i.e. databases). For each resource, CrushED makes the best effort to ensure the partition count difference is at most 1 across all the instances. Assuming such assignment is possible considering fault-zone configuration, the worst partition distribution happens when all one off partitions are located in one node. So N resources in a cluster can theoretically have their extra partitions in one node, so the node will have N additional pa [...]
-
-## Experiment
-
-We tested CrushED by simulating real production cluster topology data. And we tested multiple scenarios:
-
-* Distribution based on cluster topology.
-* Disabling hosts to simulate hosts down.
-* Adding hosts to simulate expansion.
-* Rolling upgrade.
-
-All results show that CrushED generates more uniform global distribution compared with CRUSH.
-Moreover, partition movements in most scenarios are minimized. When topology changes (i.e. cluster expansion), there can be significantly more partition movements, but we can control the impact by using State Transition Throttling feature.
-
-### Partition Distribution
-
-Following charts demonstrate the worst cases (min load vs. max load) and STDEVs of partition/master distributions from some sample clusters data.
-If we measure the improvement by STDEV, CrushED improves the partition distribution evenness by 87% on average compared with CRUSH. And for state assignment (i.e. Mastership assignment) the evenness improvement is 68% on average.
-
-
-
-
-
-### Disabling Nodes
-
-When nodes are offline or disabled, CrushED will re-assign the partitions to other live nodes. The algorithm move only the necessary partitions.
-We simulated disabling nodes, and measured partition movement changes and mastership changes. We also used the expected movement (the partitions/masters count on the disabled nodes) as a baseline to measure extra movements.
-
-The results show that movement is highly correlated to the number of disabled nodes, and extra movements are minor (in most cases 0 movements).
-
-Note that **Rate** in this document is **the changed number / total partition or master count**.
-
-
-
-### Rolling upgrade
-
-Rolling upgrade is different from disabling nodes. Since nodes are reset one by one, in this test we assume the difference could be 2 nodes in maximum (for example, upgrading Node A then upgrading Node B).
-In this case, movements are still minimized. Even in the worst case scenario, extra partition movements and mastership changes are still close to 0%.
-
-Note that in real production clusters, we can completely avoid partition movements while doing rolling upgrade, by enabling Delayed Rebalancing.
-
-### Adding Nodes
-
-Adding nodes (i.e. cluster expansion) changes topology. CrushED uses card dealing strategy to provide even distribution, so when topology changes, there are a lot of additional partition movements than CRUSH.
-
-Note that the extra change rate is not correlated with the number of additional nodes. So our recommendation is finishing expansion in one operation so as to do only one partition shuffling.
-
-### Algorithm Performance
-
-We compared CrushED with CRUSH algorithms using different instance numbers. The tests are executed multiple times and we recorded median computation time.
-CrushED does not cost much additional computation time for regular rebalancing. In some of the worst cases, 30% more runtime was observed, compared with CRUSH, but it is quicker than MultiRoundCRUSH.
-
-However, when there are down nodes since CrushED needs to run an additional consistent hashing based re-distribution, the computation time will be much longer. In some cases, we saw more than 3 times compared to CRUSH.
-
-With some **performance improvements**, such as using cache to avoid duplicate calculation, we achieved to greatly reduce CrushED's running time. According to our experiment, it is now close to MultiRound CRUSH.
-
-
-
-## Conclusion
-
-CrushED achieves more uniform distribution compared with CRUSH at the cost of higher rebalance computation and more partition movement when the cluster topology changes.
-
-## Simple User Guide
-
-1. Ensure the resouce is using FULL_AUTO mode.
-2. Set rebalance strategy to be "org.apache.helix.controller.rebalancer.strategy.CrushEdRebalanceStrategy".
-3. Expect more partition movement on topology changes when using the new strategy.
-
-**IdeaState SimpleFields Example**
-
- HELIX_ENABLED : "true"
- IDEAL\_STATE\_MODE : "AUTO_REBALANCE"
- REBALANCE\_MODE : "FULL\_AUTO"
- REBALANCE_STRATEGY : "org.apache.helix.controller.rebalancer.strategy.CrushRebalanceStrategy"
- MIN\_ACTIVE\_REPLICAS : "0"
- NUM_PARTITIONS : "64"
- REBALANCER\_CLASS\_NAME : "org.apache.helix.controller.rebalancer.DelayedAutoRebalancer"
- REPLICAS : "1"
- STATE\_MODEL\_DEF_REF : "LeaderStandby"
-
diff --git a/website/0.8.1/src/site/markdown/index.md b/website/0.8.1/src/site/markdown/index.md
deleted file mode 100644
index 9a67ef6..0000000
--- a/website/0.8.1/src/site/markdown/index.md
+++ /dev/null
@@ -1,58 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-<head>
- <title>Helix 0.8.1 Documentation</title>
-</head>
-
-### Get Helix
-
-[Download](./download.html)
-
-[Building](./Building.html)
-
-[Release Notes](./releasenotes/release-0.8.1.html)
-
-### Hands-On
-
-[Quickstart](./Quickstart.html)
-
-[Tutorial](./Tutorial.html)
-
-[Javadocs](http://helix.apache.org/javadocs/0.8.1/index.html)
-
-### Recipes
-
-[Distributed lock manager](./recipes/lock_manager.html)
-
-[Rabbit MQ consumer group](./recipes/rabbitmq_consumer_group.html)
-
-[Rsync replicated file store](./recipes/rsync_replicated_file_store.html)
-
-[Service discovery](./recipes/service_discovery.html)
-
-[Distributed task DAG execution](./recipes/task_dag_execution.html)
-
-### Operation
-
-[Monitoring Metrics](./Metrics.html)
-
-### Design
-
-[CRUSH-ed for even distribution](./design_crushed.html)
diff --git a/website/0.8.1/src/site/markdown/recipes/lock_manager.md b/website/0.8.1/src/site/markdown/recipes/lock_manager.md
deleted file mode 100644
index 761b939..0000000
--- a/website/0.8.1/src/site/markdown/recipes/lock_manager.md
+++ /dev/null
@@ -1,236 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-Distributed Lock Manager
-------------------------
-Distributed locks are used to synchronize accesses shared resources. Most applications today use ZooKeeper to model distributed locks.
-
-The simplest way to model a lock using ZooKeeper is (See ZooKeeper leader recipe for an exact and more advanced solution)
-
-* Each process tries to create an emphemeral node
-* If the node is successfully created, the process acquires the lock
-* Otherwise, it will watch the ZNode and try to acquire the lock again if the current lock holder disappears
-
-This is good enough if there is only one lock. But in practice, an application will need many such locks. Distributing and managing the locks among difference process becomes challenging. Extending such a solution to many locks will result in:
-
-* Uneven distribution of locks among nodes; the node that starts first will acquire all the locks. Nodes that start later will be idle.
-* When a node fails, how the locks will be distributed among remaining nodes is not predicable.
-* When new nodes are added the current nodes don\'t relinquish the locks so that new nodes can acquire some locks
-
-In other words we want a system to satisfy the following requirements.
-
-* Distribute locks evenly among all nodes to get better hardware utilization
-* If a node fails, the locks that were acquired by that node should be evenly distributed among other nodes
-* If nodes are added, locks must be evenly re-distributed among nodes.
-
-Helix provides a simple and elegant solution to this problem. Simply specify the number of locks and Helix will ensure that above constraints are satisfied.
-
-To quickly see this working run the `lock-manager-demo` script where 12 locks are evenly distributed among three nodes, and when a node fails, the locks get re-distributed among remaining two nodes. Note that Helix does not re-shuffle the locks completely, instead it simply distributes the locks relinquished by dead node among 2 remaining nodes evenly.
-
-----------------------------------------------------------------------------------------
-
-### Short Version
-This version starts multiple threads within the same process to simulate a multi node deployment. Try the long version to get a better idea of how it works.
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.1
-mvn clean install package -DskipTests
-cd recipes/distributed-lock-manager/target/distributed-lock-manager-pkg/bin
-chmod +x *
-./lock-manager-demo
-```
-
-#### Output
-
-```
-./lock-manager-demo
-STARTING localhost_12000
-STARTING localhost_12002
-STARTING localhost_12001
-STARTED localhost_12000
-STARTED localhost_12002
-STARTED localhost_12001
-localhost_12001 acquired lock:lock-group_3
-localhost_12000 acquired lock:lock-group_8
-localhost_12001 acquired lock:lock-group_2
-localhost_12001 acquired lock:lock-group_4
-localhost_12002 acquired lock:lock-group_1
-localhost_12002 acquired lock:lock-group_10
-localhost_12000 acquired lock:lock-group_7
-localhost_12001 acquired lock:lock-group_5
-localhost_12002 acquired lock:lock-group_11
-localhost_12000 acquired lock:lock-group_6
-localhost_12002 acquired lock:lock-group_0
-localhost_12000 acquired lock:lock-group_9
-lockName acquired By
-======================================
-lock-group_0 localhost_12002
-lock-group_1 localhost_12002
-lock-group_10 localhost_12002
-lock-group_11 localhost_12002
-lock-group_2 localhost_12001
-lock-group_3 localhost_12001
-lock-group_4 localhost_12001
-lock-group_5 localhost_12001
-lock-group_6 localhost_12000
-lock-group_7 localhost_12000
-lock-group_8 localhost_12000
-lock-group_9 localhost_12000
-Stopping localhost_12000
-localhost_12000 Interrupted
-localhost_12001 acquired lock:lock-group_9
-localhost_12001 acquired lock:lock-group_8
-localhost_12002 acquired lock:lock-group_6
-localhost_12002 acquired lock:lock-group_7
-lockName acquired By
-======================================
-lock-group_0 localhost_12002
-lock-group_1 localhost_12002
-lock-group_10 localhost_12002
-lock-group_11 localhost_12002
-lock-group_2 localhost_12001
-lock-group_3 localhost_12001
-lock-group_4 localhost_12001
-lock-group_5 localhost_12001
-lock-group_6 localhost_12002
-lock-group_7 localhost_12002
-lock-group_8 localhost_12001
-lock-group_9 localhost_12001
-
-```
-
-----------------------------------------------------------------------------------------
-
-### Long version
-This provides more details on how to setup the cluster and where to plugin application code.
-
-#### Start ZooKeeper
-
-```
-./start-standalone-zookeeper 2199
-```
-
-#### Create a Cluster
-
-```
-./helix-admin --zkSvr localhost:2199 --addCluster lock-manager-demo
-```
-
-#### Create a Lock Group
-
-Create a lock group and specify the number of locks in the lock group.
-
-```
-./helix-admin --zkSvr localhost:2199 --addResource lock-manager-demo lock-group 6 OnlineOffline --mode AUTO_REBALANCE
-```
-
-#### Start the Nodes
-
-Create a Lock class that handles the callbacks.
-
-```
-public class Lock extends StateModel {
- private String lockName;
-
- public Lock(String lockName) {
- this.lockName = lockName;
- }
-
- public void lock(Message m, NotificationContext context) {
- System.out.println(" acquired lock:"+ lockName );
- }
-
- public void release(Message m, NotificationContext context) {
- System.out.println(" releasing lock:"+ lockName );
- }
-
-}
-```
-
-and a LockFactory that creates Locks
-
-```
-public class LockFactory extends StateModelFactory<Lock> {
- /* Instantiates the lock handler, one per lockName */
- public Lock create(String lockName) {
- return new Lock(lockName);
- }
-}
-```
-
-At node start up, simply join the cluster and Helix will invoke the appropriate callbacks on the appropriate Lock instance. One can start any number of nodes and Helix detects that a new node has joined the cluster and re-distributes the locks automatically.
-
-```
-public class LockProcess {
- public static void main(String args) {
- String zkAddress= "localhost:2199";
- String clusterName = "lock-manager-demo";
- //Give a unique id to each process, most commonly used format hostname_port
- String instanceName ="localhost_12000";
- ZKHelixAdmin helixAdmin = new ZKHelixAdmin(zkAddress);
- //configure the instance and provide some metadata
- InstanceConfig config = new InstanceConfig(instanceName);
- config.setHostName("localhost");
- config.setPort("12000");
- admin.addInstance(clusterName, config);
- //join the cluster
- HelixManager manager;
- manager = HelixManagerFactory.getHelixManager(clusterName,
- instanceName,
- InstanceType.PARTICIPANT,
- zkAddress);
- manager.getStateMachineEngine().registerStateModelFactory("OnlineOffline", modelFactory);
- manager.connect();
- Thread.currentThread.join();
- }
-}
-```
-
-#### Start the Controller
-
-The controller can be started either as a separate process or can be embedded within each node process
-
-##### Separate Process
-This is recommended when number of nodes in the cluster \> 100. For fault tolerance, you can run multiple controllers on different boxes.
-
-```
-./run-helix-controller --zkSvr localhost:2199 --cluster lock-manager-demo 2>&1 > /tmp/controller.log &
-```
-
-##### Embedded Within the Node Process
-This is recommended when the number of nodes in the cluster is less than 100. To start a controller from each process, simply add the following lines to MyClass
-
-```
-public class LockProcess {
- public static void main(String args) {
- String zkAddress= "localhost:2199";
- String clusterName = "lock-manager-demo";
- // .
- // .
- manager.connect();
- HelixManager controller;
- controller = HelixControllerMain.startHelixController(zkAddress,
- clusterName,
- "controller",
- HelixControllerMain.STANDALONE);
- Thread.currentThread.join();
- }
-}
-```
diff --git a/website/0.8.1/src/site/markdown/recipes/rabbitmq_consumer_group.md b/website/0.8.1/src/site/markdown/recipes/rabbitmq_consumer_group.md
deleted file mode 100644
index 83f4da0..0000000
--- a/website/0.8.1/src/site/markdown/recipes/rabbitmq_consumer_group.md
+++ /dev/null
@@ -1,213 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-
-RabbitMQ Consumer Group
------------------------
-
-[RabbitMQ](http://www.rabbitmq.com/) is well-known open source software the provides robust messaging for applications.
-
-One of the commonly implemented recipes using this software is a work queue. [http://www.rabbitmq.com/tutorials/tutorial-four-java.html](http://www.rabbitmq.com/tutorials/tutorial-four-java.html) describes the use case where
-
-* A producer sends a message with a routing key
-* The message is routed to the queue whose binding key exactly matches the routing key of the message
-* There are multiple consumers and each consumer is interested in processing only a subset of the messages by binding to the interested keys
-
-The example provided [here](http://www.rabbitmq.com/tutorials/tutorial-four-java.html) describes how multiple consumers can be started to process all the messages.
-
-While this works, in production systems one needs the following:
-
-* Ability to handle failures: when a consumer fails, another consumer must be started or the other consumers must start processing these messages that should have been processed by the failed consumer
-* When the existing consumers cannot keep up with the task generation rate, new consumers will be added. The tasks must be redistributed among all the consumers
-
-In this recipe, we demonstrate handling of consumer failures and new consumer additions using Helix.
-
-Mapping this usecase to Helix is pretty easy as the binding key/routing key is equivalent to a partition.
-
-Let's take an example. Lets say the queue has 6 partitions, and we have 2 consumers to process all the queues.
-What we want is all 6 queues to be evenly divided among 2 consumers.
-Eventually when the system scales, we add more consumers to keep up. This will make each consumer process tasks from 2 queues.
-Now let's say that a consumer failed, reducing the number of active consumers to 2. This means each consumer must process 3 queues.
-
-We showcase how such a dynamic application can be developed using Helix. Even though we use RabbitMQ as the pub/sub system one can extend this solution to other pub/sub systems.
-
-### Try It
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.1
-mvn clean install package -DskipTests
-cd recipes/rabbitmq-consumer-group/bin
-chmod +x *
-export HELIX_PKG_ROOT=`pwd`/helix-core/target/helix-core-pkg
-export HELIX_RABBITMQ_ROOT=`pwd`/recipes/rabbitmq-consumer-group/
-chmod +x $HELIX_PKG_ROOT/bin/*
-chmod +x $HELIX_RABBITMQ_ROOT/bin/*
-```
-
-#### Install RabbitMQ
-
-Setting up RabbitMQ on a local box is straightforward. You can find the instructions here
-http://www.rabbitmq.com/download.html
-
-#### Start ZK
-
-Start ZooKeeper at port 2199
-
-```
-$HELIX_PKG_ROOT/bin/start-standalone-zookeeper 2199
-```
-
-#### Setup the Consumer Group Cluster
-
-This will setup the cluster by creating a "rabbitmq-consumer-group" cluster and adds a "topic" with "6" queues.
-
-```
-$HELIX_RABBITMQ_ROOT/bin/setup-cluster.sh localhost:2199
-```
-
-#### Add Consumers
-
-Start 2 consumers in 2 different terminals. Each consumer is given a unique ID.
-
-```
-//start-consumer.sh zookeeperAddress (e.g. localhost:2181) consumerId , rabbitmqServer (e.g. localhost)
-$HELIX_RABBITMQ_ROOT/bin/start-consumer.sh localhost:2199 0 localhost
-$HELIX_RABBITMQ_ROOT/bin/start-consumer.sh localhost:2199 1 localhost
-
-```
-
-#### Start the Helix Controller
-
-Now start a Helix controller that starts managing the "rabbitmq-consumer-group" cluster.
-
-```
-$HELIX_RABBITMQ_ROOT/bin/start-cluster-manager.sh localhost:2199
-```
-
-#### Send Messages to the Topic
-
-Start sending messages to the topic. This script randomly selects a routing key (1-6) and sends the message to topic.
-Based on the key, messages gets routed to the appropriate queue.
-
-```
-$HELIX_RABBITMQ_ROOT/bin/send-message.sh localhost 20
-```
-
-After running this, you should see all 20 messages being processed by 2 consumers.
-
-#### Add Another Consumer
-
-Once a new consumer is started, Helix detects it. In order to balance the load between 3 consumers, it deallocates 1 partition from the existing consumers and allocates it to the new consumer. We see that
-each consumer is now processing only 2 queues.
-Helix makes sure that old nodes are asked to stop consuming before the new consumer is asked to start consuming for a given partition. But the transitions for each partition can happen in parallel.
-
-```
-$HELIX_RABBITMQ_ROOT/bin/start-consumer.sh localhost:2199 2 localhost
-```
-
-Send messages again to the topic
-
-```
-$HELIX_RABBITMQ_ROOT/bin/send-message.sh localhost 100
-```
-
-You should see that messages are now received by all 3 consumers.
-
-#### Stop a Consumer
-
-In any terminal press CTRL^C and notice that Helix detects the consumer failure and distributes the 2 partitions that were processed by failed consumer to the remaining 2 active consumers.
-
-
-### How does this work?
-
-Find the entire code [here](https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tree;f=recipes/rabbitmq-consumer-group/src/main/java/org/apache/helix/recipes/rabbitmq).
-
-#### Cluster Setup
-
-This step creates ZNode on ZooKeeper for the cluster and adds the state model. We use online offline state model since there is no need for other states. The consumer is either processing a queue or it is not.
-
-It creates a resource called "rabbitmq-consumer-group" with 6 partitions. The execution mode is set to AUTO_REBALANCE. This means that the Helix controls the assignment of partition to consumers and automatically distributes the partitions evenly among the active consumers. When a consumer is added or removed, it ensures that a minimum number of partitions are shuffled.
-
-```
-zkclient = new ZkClient(zkAddr, ZkClient.DEFAULT_SESSION_TIMEOUT,
- ZkClient.DEFAULT_CONNECTION_TIMEOUT, new ZNRecordSerializer());
-ZKHelixAdmin admin = new ZKHelixAdmin(zkclient);
-
-// add cluster
-admin.addCluster(clusterName, true);
-
-// add state model definition
-StateModelConfigGenerator generator = new StateModelConfigGenerator();
-admin.addStateModelDef(clusterName, "OnlineOffline",
- new StateModelDefinition(generator.generateConfigForOnlineOffline()));
-
-// add resource "topic" which has 6 partitions
-String resourceName = "rabbitmq-consumer-group";
-admin.addResource(clusterName, resourceName, 6, "OnlineOffline", "AUTO_REBALANCE");
-```
-
-### Starting the Consumers
-
-The only thing consumers need to know is the ZooKeeper address, cluster name and consumer ID. It does not need to know anything else.
-
-```
-_manager = HelixManagerFactory.getZKHelixManager(_clusterName,
- _consumerId,
- InstanceType.PARTICIPANT,
- _zkAddr);
-
-StateMachineEngine stateMach = _manager.getStateMachineEngine();
-ConsumerStateModelFactory modelFactory =
- new ConsumerStateModelFactory(_consumerId, _mqServer);
-stateMach.registerStateModelFactory("OnlineOffline", modelFactory);
-
-_manager.connect();
-```
-
-Once the consumer has registered the state model and the controller is started, the consumer starts getting callbacks (onBecomeOnlineFromOffline) for the partition it needs to host. All it needs to do as part of the callback is to start consuming messages from the appropriate queue. Similarly, when the controller deallocates a partitions from a consumer, it fires onBecomeOfflineFromOnline for the same partition.
-As a part of this transition, the consumer will stop consuming from a that queue.
-
-```
-@Transition(to = "ONLINE", from = "OFFLINE")
-public void onBecomeOnlineFromOffline(Message message, NotificationContext context) {
- LOG.debug(_consumerId + " becomes ONLINE from OFFLINE for " + _partition);
- if (_thread == null) {
- LOG.debug("Starting ConsumerThread for " + _partition + "...");
- _thread = new ConsumerThread(_partition, _mqServer, _consumerId);
- _thread.start();
- LOG.debug("Starting ConsumerThread for " + _partition + " done");
-
- }
-}
-
-@Transition(to = "OFFLINE", from = "ONLINE")
-public void onBecomeOfflineFromOnline(Message message, NotificationContext context)
- throws InterruptedException {
- LOG.debug(_consumerId + " becomes OFFLINE from ONLINE for " + _partition);
- if (_thread != null) {
- LOG.debug("Stopping " + _consumerId + " for " + _partition + "...");
- _thread.interrupt();
- _thread.join(2000);
- _thread = null;
- LOG.debug("Stopping " + _consumerId + " for " + _partition + " done");
- }
-}
-```
diff --git a/website/0.8.1/src/site/markdown/recipes/rsync_replicated_file_store.md b/website/0.8.1/src/site/markdown/recipes/rsync_replicated_file_store.md
deleted file mode 100644
index 0e71d73..0000000
--- a/website/0.8.1/src/site/markdown/recipes/rsync_replicated_file_store.md
+++ /dev/null
@@ -1,162 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-Near-Realtime Rsync Replicated File System
-------------------------------------------
-
-### Quick Demo
-
-* This demo starts 3 instances with id's as ```localhost_12001, localhost_12002, localhost_12003```
-* Each instance stores its files under ```/tmp/<id>/filestore```
-* ```localhost_12001``` is designated as the master, and ```localhost_12002``` and ```localhost_12003``` are the slaves
-* Files written to the master are replicated to the slaves automatically. In this demo, a.txt and b.txt are written to ```/tmp/localhost_12001/filestore``` and they get replicated to other folders.
-* When the master is stopped, ```localhost_12002``` is promoted to master.
-* The other slave ```localhost_12003``` stops replicating from ```localhost_12001``` and starts replicating from new master ```localhost_12002```
-* Files written to new master ```localhost_12002``` are replicated to ```localhost_12003```
-* In the end state of this quick demo, ```localhost_12002``` is the master and ```localhost_12003``` is the slave. Manually create files under ```/tmp/localhost_12002/filestore``` and see that appear in ```/tmp/localhost_12003/filestore```
-* Ignore the interrupted exceptions on the console :-)
-
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.1
-cd recipes/rsync-replicated-file-system/
-mvn clean install package -DskipTests
-cd target/rsync-replicated-file-system-pkg/bin
-chmod +x *
-./quickdemo
-
-```
-
-### Overview
-
-There are many applications that require storage for storing large number of relatively small data files. Examples include media stores to store small videos, images, mail attachments etc. Each of these objects is typically kilobytes, often no larger than a few megabytes. An additional distinguishing feature of these use cases is that files are typically only added or deleted, rarely updated. When there are updates, they do not have any concurrency requirements.
-
-These are much simpler requirements than what general purpose distributed file system have to satisfy; these would include concurrent access to files, random access for reads and updates, posix compliance, and others. To satisfy those requirements, general DFSs are also pretty complex that are expensive to build and maintain.
-
-A different implementation of a distributed file system includes HDFS which is inspired by Google's GFS. This is one of the most widely used distributed file system that forms the main data storage platform for Hadoop. HDFS is primary aimed at processing very large data sets and distributes files across a cluster of commodity servers by splitting up files in fixed size chunks. HDFS is not particularly well suited for storing a very large number of relatively tiny files.
-
-### File Store
-
-It's possible to build a vastly simpler system for the class of applications that have simpler requirements as we have pointed out.
-
-* Large number of files but each file is relatively small
-* Access is limited to create, delete and get entire files
-* No updates to files that are already created (or it's feasible to delete the old file and create a new one)
-
-
-We call this system a Partitioned File Store (PFS) to distinguish it from other distributed file systems. This system needs to provide the following features:
-
-* CRD access to large number of small files
-* Scalability: Files should be distributed across a large number of commodity servers based on the storage requirement
-* Fault-tolerance: Each file should be replicated on multiple servers so that individual server failures do not reduce availability
-* Elasticity: It should be possible to add capacity to the cluster easily
-
-
-Apache Helix is a generic cluster management framework that makes it very easy to provide scalability, fault-tolerance and elasticity features.
-rsync can be easily used as a replication channel between servers so that each file gets replicated on multiple servers.
-
-### Design
-
-#### High Level
-
-* Partition the file system based on the file name
-* At any time a single writer can write, we call this a master
-* For redundancy, we need to have additional replicas called slave. Slaves can optionally serve reads
-* Slave replicates data from the master
-* When a master fails, a slave gets promoted to master
-
-#### Transaction Log
-
-Every write on the master will result in creation/deletion of one or more files. In order to maintain timeline consistency slaves need to apply the changes in the same order
-To facilitate this, the master logs each transaction in a file and each transaction is associated with an 64 bit ID in which the 32 LSB represents a sequence number and MSB represents the generation number
-The sequence number gets incremented on every transaction and the generation is incremented when a new master is elected
-
-#### Replication
-
-Replication is required for slaves to keep up with changes on the master. Every time the slave applies a change it checkpoints the last applied transaction ID.
-During restarts, this allows the slave to pull changes from the last checkpointed ID. Similar to master, the slave logs each transaction to the transaction logs but instead of generating new transaction ID, it uses the same ID generated by the master.
-
-
-#### Failover
-
-When a master fails, a new slave will be promoted to master. If the previous master node is reachable, then the new master will flush all the
-changes from previous the master before taking up mastership. The new master will record the end transaction ID of the current generation and then start a new generation
-with sequence starting from 1. After this the master will begin accepting writes.
-
-
-
-
-
-### Rsync-based Solution
-
-
-
-
-This application demonstrates a file store that uses rsync as the replication mechanism. One can envision a similar system where instead of using rsync, one
-can implement a custom solution to notify the slave of the changes and also provide an api to pull the change files.
-
-#### Concepts
-* file_store_dir: Root directory for the actual data files
-* change_log_dir: The transaction logs are generated under this folder
-* check_point_dir: The slave stores the check points ( last processed transaction) here
-
-#### Master
-* File server: This component supports file uploads and downloads and writes the files to ```file_store_dir```. This is not included in this application. The idea is that most applications have different ways of implementing this component and have some associated business logic. It is not hard to come up with such a component if needed.
-* File store watcher: This component watches the ```file_store_dir``` directory on the local file system for any changes and notifies the registered listeners of the changes
-* Change log generator: This registers as a listener of the file store watcher and on each notification logs the changes into a file under ```change_log_dir```
-
-#### Slave
-* File server: This component on the slave will only support reads
-* Cluster state observer: Slave observes the cluster state and is able to know who is the current master
-* Replicator: This has two subcomponents
- - Periodic rsync of change log: This is a background process that periodically rsyncs the ```change_log_dir``` of the master to its local directory
- - Change Log Watcher: This watches the ```change_log_dir``` for changes and notifies the registered listeners of the change
- - On demand rsync invoker: This is registered as a listener to change log watcher and on every change invokes rsync to sync only the changed file
-
-#### Coordination
-
-The coordination between nodes is done by Helix. Helix does the partition management and assigns the partition to multiple nodes based on the replication factor. It elects one the nodes as master and designates others as slaves.
-It provides notifications to each node in the form of state transitions (Offline to Slave, Slave to Master). It also provides notifications when there is change is cluster state.
-This allows the slave to stop replicating from current master and start replicating from new master.
-
-In this application, we have only one partition but its very easy to extend it to support multiple partitions. By partitioning the file store, one can add new nodes and Helix will automatically
-re-distribute partitions among the nodes. To summarize, Helix provides partition management, fault tolerance and facilitates automated cluster expansion.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/website/0.8.1/src/site/markdown/recipes/service_discovery.md b/website/0.8.1/src/site/markdown/recipes/service_discovery.md
deleted file mode 100644
index 36a1575..0000000
--- a/website/0.8.1/src/site/markdown/recipes/service_discovery.md
+++ /dev/null
@@ -1,184 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-Service Discovery
------------------
-
-One of the common usage of ZooKeeper is to enable service discovery.
-The basic idea is that when a server starts up it advertises its configuration/metadata such as its hostname and port on ZooKeeper.
-This allows clients to dynamically discover the servers that are currently active. One can think of this like a service registry to which a server registers when it starts and
-is automatically deregistered when it shutdowns or crashes. In many cases it serves as an alternative to VIPs.
-
-The core idea behind this is to use ZooKeeper ephemeral nodes. The ephemeral nodes are created when the server registers and all its metadata is put into a ZNode.
-When the server shutdowns, ZooKeeper automatically removes this ZNode.
-
-There are two ways the clients can dynamically discover the active servers:
-
-### ZooKeeper Watch
-
-Clients can set a child watch under specific path on ZooKeeper.
-When a new service is registered/deregistered, ZooKeeper notifies the client via a watch event and the client can read the list of services. Even though this looks trivial,
-there are lot of things one needs to keep in mind like ensuring that you first set the watch back on ZooKeeper before reading data.
-
-
-### Poll
-
-Another approach is for the client to periodically read the ZooKeeper path and get the list of services.
-
-Both approaches have pros and cons, for example setting a watch might trigger herd effect if there are large number of clients. This is problematic, especially when servers are starting up.
-But the advantage to setting watches is that clients are immediately notified of a change which is not true in case of polling.
-In some cases, having both watches and polls makes sense; watch allows one to get notifications as soon as possible while poll provides a safety net if a watch event is missed because of code bug or ZooKeeper fails to notify.
-
-### Other Developer Considerations
-* What happens when the ZooKeeper session expires? All the watches and ephemeral nodes previously added or created by this server are lost. One needs to add the watches again, recreate the ephemeral nodes, and so on.
-* Due to network issues or Java GC pauses session expiry might happen again and again; this phenomenon is known as flapping. It\'s important for the server to detect this and deregister itself.
-
-### Other Operational Considerations
-* What if the node is behaving badly? One might kill the server, but it will lose the ability to debug. It would be nice to have the ability to mark a server as disabled and clients know that a node is disabled and will not contact that node.
-
-### Configuration Ownership
-
-This is an important aspect that is often ignored in the initial stages of your development. Typically, the service discovery pattern means that servers start up with some configuration which it simply puts into ZooKeeper. While this works well in the beginning, configuration management becomes very difficult since the servers themselves are statically configured. Any change in server configuration implies restarting the server. Ideally, it will be nice to have the ability to change conf [...]
-
-Ideally you want a hybrid solution, a node starts with minimal configuration and gets the rest of configuration from ZooKeeper.
-
-### Using Helix for Service Discovery
-
-Even though Helix has a higher-level abstraction in terms of state machines, constraints and objectives, service discovery is one of things has been a prevalent use case from the start.
-The controller uses the exact mechanism we described above to discover when new servers join the cluster. We create these ZNodes under /CLUSTERNAME/LIVEINSTANCES.
-Since at any time there is only one controller, we use a ZK watch to track the liveness of a server.
-
-This recipe simply demonstrates how one can re-use that part for implementing service discovery. This demonstrates multiple modes of service discovery:
-
-* POLL: The client reads from zookeeper at regular intervals 30 seconds. Use this if you have 100's of clients
-* WATCH: The client sets up watcher and gets notified of the changes. Use this if you have 10's of clients
-* NONE: This does neither of the above, but reads directly from zookeeper when ever needed
-
-Helix provides these additional features compared to other implementations available elsewhere:
-
-* It has the concept of disabling a node which means that a badly behaving node can be disabled using the Helix admin API
-* It automatically detects if a node connects/disconnects from zookeeper repeatedly and disables the node
-* Configuration management
- * Allows one to set configuration via the admin API at various granulaties like cluster, instance, resource, partition
- * Configurations can be dynamically changed
- * The server is notified when configurations change
-
-
-### Checkout and Build
-
-```
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout tags/helix-0.8.1
-mvn clean install package -DskipTests
-cd recipes/service-discovery/target/service-discovery-pkg/bin
-chmod +x *
-```
-
-### Start ZooKeeper
-
-```
-./start-standalone-zookeeper 2199
-```
-
-### Run the Demo
-
-```
-./service-discovery-demo.sh
-```
-
-### Output
-
-```
-START:Service discovery demo mode:WATCH
- Registering service
- host.x.y.z_12000
- host.x.y.z_12001
- host.x.y.z_12002
- host.x.y.z_12003
- host.x.y.z_12004
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12002
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Deregistering service:
- host.x.y.z_12002
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Registering service:host.x.y.z_12002
-END:Service discovery demo mode:WATCH
-=============================================
-START:Service discovery demo mode:POLL
- Registering service
- host.x.y.z_12000
- host.x.y.z_12001
- host.x.y.z_12002
- host.x.y.z_12003
- host.x.y.z_12004
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12002
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Deregistering service:
- host.x.y.z_12002
- Sleeping for poll interval:30000
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Registering service:host.x.y.z_12002
-END:Service discovery demo mode:POLL
-=============================================
-START:Service discovery demo mode:NONE
- Registering service
- host.x.y.z_12000
- host.x.y.z_12001
- host.x.y.z_12002
- host.x.y.z_12003
- host.x.y.z_12004
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12000
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12002
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Deregistering service:
- host.x.y.z_12000
- SERVICES AVAILABLE
- SERVICENAME HOST PORT
- myServiceName host.x.y.z 12001
- myServiceName host.x.y.z 12002
- myServiceName host.x.y.z 12003
- myServiceName host.x.y.z 12004
- Registering service:host.x.y.z_12000
-END:Service discovery demo mode:NONE
-=============================================
-```
diff --git a/website/0.8.1/src/site/markdown/recipes/task_dag_execution.md b/website/0.8.1/src/site/markdown/recipes/task_dag_execution.md
deleted file mode 100644
index 8779b58..0000000
--- a/website/0.8.1/src/site/markdown/recipes/task_dag_execution.md
+++ /dev/null
@@ -1,199 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
-Distributed Task Execution
---------------------------
-
-This recipe is intended to demonstrate how task dependencies can be modeled using primitives provided by Helix. A given task can be run with the desired amount of parallelism and will start only when upstream dependencies are met. The demo executes the task DAG described below using 10 workers. Although the demo starts the workers as threads, there is no requirement that all the workers need to run in the same process. In reality, these workers run on many different boxes on a cluster. [...]
-
-Redis is used as a result store. Any other suitable implementation for TaskResultStore can be plugged in.
-
-### Workflow
-
-#### Input
-
-10000 impression events and around 100 click events are pre-populated in task result store (redis).
-
-* **ImpEvent**: format: id,isFraudulent,country,gender
-
-* **ClickEvent**: format: id,isFraudulent,impEventId
-
-#### Stages
-
-+ **FilterImps**: Filters impression where isFraudulent=true.
-
-+ **FilterClicks**: Filters clicks where isFraudulent=true
-
-+ **impCountsByGender**: Generates impression counts grouped by gender. It does this by incrementing the count for 'impression_gender_counts:<gender_value>' in the task result store (redis hash). Depends on: **FilterImps**
-
-+ **impCountsByCountry**: Generates impression counts grouped by country. It does this by incrementing the count for 'impression_country_counts:<country_value>' in the task result store (redis hash). Depends on: **FilterClicks**
-
-+ **impClickJoin**: Joins clicks with corresponding impression event using impEventId as the join key. Join is needed to pull dimensions not present in click event. Depends on: **FilterImps, FilterClicks**
-
-+ **clickCountsByGender**: Generates click counts grouped by gender. It does this by incrementing the count for click_gender_counts:<gender_value> in the task result store (redis hash). Depends on: **impClickJoin**
-
-+ **clickCountsByGender**: Generates click counts grouped by country. It does this by incrementing the count for click_country_counts:<country_value> in the task result store (redis hash). Depends on: **impClickJoin**
-
-+ **report**: Reads from all aggregates generated by previous stages and prints them. Depends on: **impCountsByGender, impCountsByCountry, clickCountsByGender,clickCountsByGender**
-
-
-### Creating a DAG
-
-Each stage is represented as a Node along with the upstream dependency and desired parallelism. Each stage is modeled as a resource in Helix using OnlineOffline state model. As part of an Offline to Online transition, we watch the external view of upstream resources and wait for them to transition to the online state. See Task.java for additional info.
-
-```
-Dag dag = new Dag();
-dag.addNode(new Node("filterImps", 10, ""));
-dag.addNode(new Node("filterClicks", 5, ""));
-dag.addNode(new Node("impClickJoin", 10, "filterImps,filterClicks"));
-dag.addNode(new Node("impCountsByGender", 10, "filterImps"));
-dag.addNode(new Node("impCountsByCountry", 10, "filterImps"));
-dag.addNode(new Node("clickCountsByGender", 5, "impClickJoin"));
-dag.addNode(new Node("clickCountsByCountry", 5, "impClickJoin"));
-dag.addNode(new Node("report",1,"impCountsByGender,impCountsByCountry,clickCountsByGender,clickCountsByCountry"));
-```
-
-### Demo
-
-In order to run the demo, use the following steps
-
-See http://redis.io/topics/quickstart on how to install redis server
-
-```
-Start redis e.g:
-./redis-server --port 6379
-
-git clone https://git-wip-us.apache.org/repos/asf/helix.git
-cd helix
-git checkout helix-0.8.1
-cd recipes/task-execution
-mvn clean install package -DskipTests
-cd target/task-execution-pkg/bin
-chmod +x task-execution-demo.sh
-./task-execution-demo.sh 2181 localhost 6379
-
-```
-
-Here\'s a visual representation of the DAG.
-
-```
-
-
-
-
-
- +-----------------+ +----------------+
- | filterImps | | filterClicks |
- | (parallelism=10)| | (parallelism=5)|
- +----------+-----++ +-------+--------+
- | | | |
- | | | |
- | | | |
- | | +------->--------v------------+
- +--------------<-+ +------v-------+ | impClickJoin |
- |impCountsByGender |impCountsByCountry | (parallelism=10) |
- |(parallelism=10) |(parallelism=10) ++-------------------+-+
- +-----------+--+ +---+----------+ | |
- | | | |
- | | | |
- | | +--------v---------+ +-v-------------------+
- | | |clickCountsByGender |clickCountsByCountry |
- | | |(parallelism=5) | |(parallelism=5) |
- | | +----+-------------+ +---------------------+
- | | | |
- | | | |
- | | | |
- +----->+-----+>-----------v----+<---------------+
- | report |
- |(parallelism=1) |
- +-----------------------+
-
-```
-
-(credit for above ascii art: http://www.asciiflow.com)
-
-#### Output
-
-```
-Done populating dummy data
-Executing filter task for filterImps_3 for impressions_demo
-Executing filter task for filterImps_2 for impressions_demo
-Executing filter task for filterImps_0 for impressions_demo
-Executing filter task for filterImps_1 for impressions_demo
-Executing filter task for filterImps_4 for impressions_demo
-Executing filter task for filterClicks_3 for clicks_demo
-Executing filter task for filterClicks_1 for clicks_demo
-Executing filter task for filterImps_8 for impressions_demo
-Executing filter task for filterImps_6 for impressions_demo
-Executing filter task for filterClicks_2 for clicks_demo
-Executing filter task for filterClicks_0 for clicks_demo
-Executing filter task for filterImps_7 for impressions_demo
-Executing filter task for filterImps_5 for impressions_demo
-Executing filter task for filterClicks_4 for clicks_demo
-Executing filter task for filterImps_9 for impressions_demo
-Running AggTask for impCountsByGender_3 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_2 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_0 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_9 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_1 for filtered_impressions_demo gender
-Running AggTask for impCountsByGender_4 for filtered_impressions_demo gender
-Running AggTask for impCountsByCountry_4 for filtered_impressions_demo country
-Running AggTask for impCountsByGender_5 for filtered_impressions_demo gender
-Executing JoinTask for impClickJoin_2
-Running AggTask for impCountsByCountry_3 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_1 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_0 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_2 for filtered_impressions_demo country
-Running AggTask for impCountsByGender_6 for filtered_impressions_demo gender
-Executing JoinTask for impClickJoin_1
-Executing JoinTask for impClickJoin_0
-Executing JoinTask for impClickJoin_3
-Running AggTask for impCountsByGender_8 for filtered_impressions_demo gender
-Executing JoinTask for impClickJoin_4
-Running AggTask for impCountsByGender_7 for filtered_impressions_demo gender
-Running AggTask for impCountsByCountry_5 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_6 for filtered_impressions_demo country
-Executing JoinTask for impClickJoin_9
-Running AggTask for impCountsByCountry_8 for filtered_impressions_demo country
-Running AggTask for impCountsByCountry_7 for filtered_impressions_demo country
-Executing JoinTask for impClickJoin_5
-Executing JoinTask for impClickJoin_6
-Running AggTask for impCountsByCountry_9 for filtered_impressions_demo country
-Executing JoinTask for impClickJoin_8
-Executing JoinTask for impClickJoin_7
-Running AggTask for clickCountsByCountry_1 for joined_clicks_demo country
-Running AggTask for clickCountsByCountry_0 for joined_clicks_demo country
-Running AggTask for clickCountsByCountry_2 for joined_clicks_demo country
-Running AggTask for clickCountsByCountry_3 for joined_clicks_demo country
-Running AggTask for clickCountsByGender_1 for joined_clicks_demo gender
-Running AggTask for clickCountsByCountry_4 for joined_clicks_demo country
-Running AggTask for clickCountsByGender_3 for joined_clicks_demo gender
-Running AggTask for clickCountsByGender_2 for joined_clicks_demo gender
-Running AggTask for clickCountsByGender_4 for joined_clicks_demo gender
-Running AggTask for clickCountsByGender_0 for joined_clicks_demo gender
-Running reports task
-Impression counts per country
-{CANADA=1940, US=1958, CHINA=2014, UNKNOWN=2022, UK=1946}
-Click counts per country
-{US=24, CANADA=14, CHINA=26, UNKNOWN=14, UK=22}
-Impression counts per gender
-{F=3325, UNKNOWN=3259, M=3296}
-Click counts per gender
-{F=33, UNKNOWN=32, M=35}
-```
diff --git a/website/0.8.1/src/site/markdown/tutorial_admin.md b/website/0.8.1/src/site/markdown/tutorial_admin.md
deleted file mode 100644
index b6f408e..0000000
--- a/website/0.8.1/src/site/markdown/tutorial_admin.md
+++ /dev/null
@@ -1,408 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"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.
--->
-
... 25675 lines suppressed ...