You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by ka...@apache.org on 2017/04/05 01:17:01 UTC
[1/2] storm git commit: fix md formatting for windows storm.local.dir
example (jekyll needs a newline before the code quotes)
Repository: storm
Updated Branches:
refs/heads/1.0.x-branch 739705c02 -> 8996aa0fe
fix md formatting for windows storm.local.dir example (jekyll needs a newline before the code quotes)
Signed-off-by: alexlehm <al...@gmail.com>
Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/62f650d2
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/62f650d2
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/62f650d2
Branch: refs/heads/1.0.x-branch
Commit: 62f650d2faf05aa7478e0ac9407592eb85246e1a
Parents: 739705c
Author: alexlehm <al...@gmail.com>
Authored: Sun Apr 2 12:49:01 2017 +0200
Committer: Jungtaek Lim <ka...@gmail.com>
Committed: Wed Apr 5 10:16:46 2017 +0900
----------------------------------------------------------------------
docs/Setting-up-a-Storm-cluster.md | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/storm/blob/62f650d2/docs/Setting-up-a-Storm-cluster.md
----------------------------------------------------------------------
diff --git a/docs/Setting-up-a-Storm-cluster.md b/docs/Setting-up-a-Storm-cluster.md
index 45005e2..a251d1a 100644
--- a/docs/Setting-up-a-Storm-cluster.md
+++ b/docs/Setting-up-a-Storm-cluster.md
@@ -17,11 +17,11 @@ Here's a summary of the steps for setting up a Storm cluster:
### Set up a Zookeeper cluster
-Storm uses Zookeeper for coordinating the cluster. Zookeeper **is not** used for message passing, so the load Storm places on Zookeeper is quite low. Single node Zookeeper clusters should be sufficient for most cases, but if you want failover or are deploying large Storm clusters you may want larger Zookeeper clusters. Instructions for deploying Zookeeper are [here](http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html).
+Storm uses Zookeeper for coordinating the cluster. Zookeeper **is not** used for message passing, so the load Storm places on Zookeeper is quite low. Single node Zookeeper clusters should be sufficient for most cases, but if you want failover or are deploying large Storm clusters you may want larger Zookeeper clusters. Instructions for deploying Zookeeper are [here](http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html).
A few notes about Zookeeper deployment:
-1. It's critical that you run Zookeeper under supervision, since Zookeeper is fail-fast and will exit the process if it encounters any error case. See [here](http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_supervision) for more details.
+1. It's critical that you run Zookeeper under supervision, since Zookeeper is fail-fast and will exit the process if it encounters any error case. See [here](http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_supervision) for more details.
2. It's critical that you set up a cron to compact Zookeeper's data and transaction logs. The Zookeeper daemon does not do this on its own, and if you don't set up a cron, Zookeeper will quickly run out of disk space. See [here](http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_maintenance) for more details.
### Install dependencies on Nimbus and worker machines
@@ -58,11 +58,12 @@ If the port that your Zookeeper cluster uses is different than the default, you
```yaml
storm.local.dir: "/mnt/storm"
```
-If you run storm on windows,it could be:
+If you run storm on windows, it could be:
+
```yaml
storm.local.dir: "C:\\storm-local"
```
-If you use a relative path,it will be relative to where you installed storm(STORM_HOME).
+If you use a relative path, it will be relative to where you installed storm(STORM_HOME).
You can leave it empty with default value `$STORM_HOME/storm-local`
3) **nimbus.seeds**: The worker nodes need to know which machines are the candidate of master in order to download topology jars and confs. For example:
@@ -84,7 +85,7 @@ supervisor.slots.ports:
### Monitoring Health of Supervisors
-Storm provides a mechanism by which administrators can configure the supervisor to run administrator supplied scripts periodically to determine if a node is healthy or not. Administrators can have the supervisor determine if the node is in a healthy state by performing any checks of their choice in scripts located in storm.health.check.dir. If a script detects the node to be in an unhealthy state, it must print a line to standard output beginning with the string ERROR. The supervisor will periodically run the scripts in the health check dir and check the output. If the script\u2019s output contains the string ERROR, as described above, the supervisor will shut down any workers and exit.
+Storm provides a mechanism by which administrators can configure the supervisor to run administrator supplied scripts periodically to determine if a node is healthy or not. Administrators can have the supervisor determine if the node is in a healthy state by performing any checks of their choice in scripts located in storm.health.check.dir. If a script detects the node to be in an unhealthy state, it must print a line to standard output beginning with the string ERROR. The supervisor will periodically run the scripts in the health check dir and check the output. If the script\u2019s output contains the string ERROR, as described above, the supervisor will shut down any workers and exit.
If the supervisor is running with supervision "/bin/storm node-health-check" can be called to determine if the supervisor should be launched or if the node is unhealthy.
@@ -112,6 +113,6 @@ The last step is to launch all the Storm daemons. It is critical that you run ea
1. **Nimbus**: Run the command "bin/storm nimbus" under supervision on the master machine.
2. **Supervisor**: Run the command "bin/storm supervisor" under supervision on each worker machine. The supervisor daemon is responsible for starting and stopping worker processes on that machine.
-3. **UI**: Run the Storm UI (a site you can access from the browser that gives diagnostics on the cluster and topologies) by running the command "bin/storm ui" under supervision. The UI can be accessed by navigating your web browser to http://{ui host}:8080.
+3. **UI**: Run the Storm UI (a site you can access from the browser that gives diagnostics on the cluster and topologies) by running the command "bin/storm ui" under supervision. The UI can be accessed by navigating your web browser to http://{ui host}:8080.
As you can see, running the daemons is very straightforward. The daemons will log to the logs/ directory in wherever you extracted the Storm release.
[2/2] storm git commit: Merge branch 'PR-2039-1.0.x-merge' into
1.0.x-branch
Posted by ka...@apache.org.
Merge branch 'PR-2039-1.0.x-merge' into 1.0.x-branch
Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/8996aa0f
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/8996aa0f
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/8996aa0f
Branch: refs/heads/1.0.x-branch
Commit: 8996aa0fe15db4bef73108985a7898bd0f4afa32
Parents: 739705c 62f650d
Author: Jungtaek Lim <ka...@gmail.com>
Authored: Wed Apr 5 10:16:49 2017 +0900
Committer: Jungtaek Lim <ka...@gmail.com>
Committed: Wed Apr 5 10:16:49 2017 +0900
----------------------------------------------------------------------
docs/Setting-up-a-Storm-cluster.md | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
----------------------------------------------------------------------