This is an automated email from the ASF dual-hosted git repository.
lxia pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/helix.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new 2da2bd2 Updated Home (markdown)
2da2bd2 is described below
commit 2da2bd2fa2c8bb03804ddc885127662368590bdb
Author: Lei Xia <[email protected]>
AuthorDate: Wed May 29 15:36:09 2019 -0700
Updated Home (markdown)
---
Home.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Home.md b/Home.md
index 3d6d884..5c21694 100644
--- a/Home.md
+++ b/Home.md
@@ -2,7 +2,7 @@
Apache 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 automates reassignment of resources in the face of node
failure and recovery, cluster expansion, and reconfiguration.
-== What Is Cluster Management?
+## What Is Cluster Management?
To understand Helix, you first need to understand cluster management. A
distributed system typically runs on multiple nodes for the following reasons:
* scalability
@@ -15,7 +15,7 @@ scheduling of maintainence tasks, such as backups, garbage
collection, file cons
repartitioning of data or resources across the cluster informing dependent
systems of changes so they can react appropriately to cluster changes
throttling system tasks and changes
While it is possible to integrate these functions into the distributed system,
it complicates the code. Helix has abstracted common cluster management tasks,
enabling the system builder to model the desired behavior with a declarative
state model, and let Helix manage the coordination. The result is less new code
to write, and a robust, highly operable system.
-== What does Helix provide?
+## What does Helix provide?
* Automatic assignment of resources and partitions to nodes
* Node failure detection and recovery
* Dynamic addition of resources
@@ -24,7 +24,7 @@ While it is possible to integrate these functions into the
distributed system, i
* Automatic load balancing and throttling of transitions
* Optional pluggable rebalancing for user-defined assignment of resources and
partitions
-== Why Helix?
+## Why Helix?
Modeling a distributed system as a state machine with constraints on states
and transitions has the following benefits:
* Separates cluster management from the core functionality of the system.
