Repository: storm Updated Branches: refs/heads/asf-site 7f68ed961 -> 17565f6da
add yaml frontmatter missing from docs so they show up on the generated site Project: http://git-wip-us.apache.org/repos/asf/storm/repo Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/17565f6d Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/17565f6d Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/17565f6d Branch: refs/heads/asf-site Commit: 17565f6dab7d1316d164abc94fc6913bcef1d813 Parents: 7f68ed9 Author: P. Taylor Goetz <[email protected]> Authored: Fri Feb 12 15:42:30 2016 -0500 Committer: P. Taylor Goetz <[email protected]> Committed: Fri Feb 12 15:42:30 2016 -0500 ---------------------------------------------------------------------- documentation/Installing-native-dependencies.md | 38 -------------------- documentation/Maven.md | 1 + documentation/Pacemaker.md | 7 +++- .../Resource_Aware_Scheduler_overview.md | 5 +++ documentation/State-checkpointing.md | 5 +++ documentation/Windowing.md | 6 +++- documentation/dynamic-log-level-settings.md | 8 +++-- documentation/dynamic-worker-profiling.md | 8 +++-- documentation/nimbus-ha-design.md | 7 +++- documentation/ui-rest-api.md | 7 +++- 10 files changed, 46 insertions(+), 46 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/Installing-native-dependencies.md ---------------------------------------------------------------------- diff --git a/documentation/Installing-native-dependencies.md b/documentation/Installing-native-dependencies.md deleted file mode 100644 index 3207b8e..0000000 --- a/documentation/Installing-native-dependencies.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -layout: documentation ---- -The native dependencies are only needed on actual Storm clusters. When running Storm in local mode, Storm uses a pure Java messaging system so that you don't need to install native dependencies on your development machine. - -Installing ZeroMQ and JZMQ is usually straightforward. Sometimes, however, people run into issues with autoconf and get strange errors. If you run into any issues, please email the [Storm mailing list](http://groups.google.com/group/storm-user) or come get help in the #storm-user room on freenode. - -Storm has been tested with ZeroMQ 2.1.7, and this is the recommended ZeroMQ release that you install. You can download a ZeroMQ release [here](http://download.zeromq.org/). Installing ZeroMQ should look something like this: - -``` -wget http://download.zeromq.org/zeromq-2.1.7.tar.gz -tar -xzf zeromq-2.1.7.tar.gz -cd zeromq-2.1.7 -./configure -make -sudo make install -``` - -JZMQ is the Java bindings for ZeroMQ. JZMQ doesn't have any releases (we're working with them on that), so there is risk of a regression if you always install from the master branch. To prevent a regression from happening, you should instead install from [this fork](http://github.com/nathanmarz/jzmq) which is tested to work with Storm. Installing JZMQ should look something like this: - -``` -#install jzmq -git clone https://github.com/nathanmarz/jzmq.git -cd jzmq -./autogen.sh -./configure -make -sudo make install -``` - -To get the JZMQ build to work, you may need to do one or all of the following: - -1. Set JAVA_HOME environment variable appropriately -2. Install Java dev package (more info [here](http://codeslinger.posterous.com/getting-zeromq-and-jzmq-running-on-mac-os-x) for Mac OSX users) -3. Upgrade autoconf on your machine -4. Follow the instructions in [this blog post](http://blog.pmorelli.com/getting-zeromq-and-jzmq-running-on-mac-os-x) - -If you run into any errors when running `./configure`, [this thread](http://stackoverflow.com/questions/3522248/how-do-i-compile-jzmq-for-zeromq-on-osx) may provide a solution. \ No newline at end of file http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/Maven.md ---------------------------------------------------------------------- diff --git a/documentation/Maven.md b/documentation/Maven.md index 677a987..ffd591d 100644 --- a/documentation/Maven.md +++ b/documentation/Maven.md @@ -1,6 +1,7 @@ --- title: Maven layout: documentation +documentation: true --- To develop topologies, you'll need the Storm jars on your classpath. You should either include the unpacked jars in the classpath for your project or use Maven to include Storm as a development dependency. Storm is hosted on Maven Central. To include Storm in your project as a development dependency, add the following to your pom.xml: http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/Pacemaker.md ---------------------------------------------------------------------- diff --git a/documentation/Pacemaker.md b/documentation/Pacemaker.md index 24e3e7f..39e3014 100644 --- a/documentation/Pacemaker.md +++ b/documentation/Pacemaker.md @@ -1,4 +1,9 @@ -# Pacemaker +--- +title: Pacemaker +layout: documentation +documentation: true +--- + ### Introduction Pacemaker is a storm daemon designed to process heartbeats from workers. As Storm is scaled up, ZooKeeper begins to become a bottleneck due to high volumes of writes from workers doing heartbeats. Lots of writes to disk and too much traffic across the network is generated as ZooKeeper tries to maintain consistency. http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/Resource_Aware_Scheduler_overview.md ---------------------------------------------------------------------- diff --git a/documentation/Resource_Aware_Scheduler_overview.md b/documentation/Resource_Aware_Scheduler_overview.md index 0f5b8cb..ed5fe66 100644 --- a/documentation/Resource_Aware_Scheduler_overview.md +++ b/documentation/Resource_Aware_Scheduler_overview.md @@ -1,3 +1,8 @@ +--- +title: Resource Aware Scheduler +layout: documentation +documentation: true +--- # Introduction The purpose of this document is to provide a description of the Resource Aware Scheduler for the Storm distributed real-time computation system. This document will provide you with both a high level description of the resource aware scheduler in Storm http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/State-checkpointing.md ---------------------------------------------------------------------- diff --git a/documentation/State-checkpointing.md b/documentation/State-checkpointing.md index 889b387..c7a81f5 100644 --- a/documentation/State-checkpointing.md +++ b/documentation/State-checkpointing.md @@ -1,3 +1,8 @@ +--- +title: Storm State Management +layout: documentation +documentation: true +--- # State support in core storm Storm core has abstractions for bolts to save and retrieve the state of its operations. There is a default in-memory based state implementation and also a Redis backed implementation that provides state persistence. http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/Windowing.md ---------------------------------------------------------------------- diff --git a/documentation/Windowing.md b/documentation/Windowing.md index 803e5ca..44512f7 100644 --- a/documentation/Windowing.md +++ b/documentation/Windowing.md @@ -1,4 +1,8 @@ -# Windowing support in core storm +--- +title: Windowing Support in Core Storm +layout: documentation +documentation: true +--- Storm core has support for processing a group of tuples that falls within a window. Windows are specified with the following two parameters, http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/dynamic-log-level-settings.md ---------------------------------------------------------------------- diff --git a/documentation/dynamic-log-level-settings.md b/documentation/dynamic-log-level-settings.md index f38b708..65b2d0a 100644 --- a/documentation/dynamic-log-level-settings.md +++ b/documentation/dynamic-log-level-settings.md @@ -1,5 +1,9 @@ -Dynamic Log Level Settings -========================== +--- +title: Dynamic Log Level Settings +layout: documentation +documentation: true +--- + We have added the ability to set log level settings for a running topology using the Storm UI and the Storm CLI. http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/dynamic-worker-profiling.md ---------------------------------------------------------------------- diff --git a/documentation/dynamic-worker-profiling.md b/documentation/dynamic-worker-profiling.md index 088a232..f1b83e9 100644 --- a/documentation/dynamic-worker-profiling.md +++ b/documentation/dynamic-worker-profiling.md @@ -1,5 +1,9 @@ -Dynamic Worker Profiling -========================== +--- +title: Dynamic Worker Profiling +layout: documentation +documentation: true +--- + In multi-tenant mode, storm launches long-running JVMs across cluster without sudo access to user. Self-serving of Java heap-dumps, jstacks and java profiling of these JVMs would improve users' ability to analyze and debug issues when monitoring it actively. http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/nimbus-ha-design.md ---------------------------------------------------------------------- diff --git a/documentation/nimbus-ha-design.md b/documentation/nimbus-ha-design.md index 672eece..d0d6fd2 100644 --- a/documentation/nimbus-ha-design.md +++ b/documentation/nimbus-ha-design.md @@ -1,4 +1,9 @@ -#Highly Available Nimbus design proposal +--- +title: Highly Available Nimbus Design +layout: documentation +documentation: true +--- + ##Problem Statement: Currently the storm master aka nimbus, is a process that runs on a single machine under supervision. In most cases the nimbus failure is transient and it is restarted by the supervisor. However sometimes when disks fail and networks http://git-wip-us.apache.org/repos/asf/storm/blob/17565f6d/documentation/ui-rest-api.md ---------------------------------------------------------------------- diff --git a/documentation/ui-rest-api.md b/documentation/ui-rest-api.md index 5fe7625..5ea4e6e 100644 --- a/documentation/ui-rest-api.md +++ b/documentation/ui-rest-api.md @@ -1,4 +1,9 @@ -# Storm UI REST API +--- +title: Storm UI REST API +layout: documentation +documentation: true +--- + The Storm UI daemon provides a REST API that allows you to interact with a Storm cluster, which includes retrieving metrics data and configuration information as well as management operations such as starting or stopping topologies.
