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 2016/07/08 10:36:31 UTC

svn commit: r1751878 - in /storm/site: publish/ publish/releases/0.10.0/ publish/releases/0.10.1/ publish/releases/1.0.0/ publish/releases/1.0.0/images/ publish/releases/1.0.1/ publish/releases/1.0.1/images/ publish/releases/2.0.0-SNAPSHOT/ publish/rel...

Author: kabhwan
Date: Fri Jul  8 10:36:30 2016
New Revision: 1751878

URL: http://svn.apache.org/viewvc?rev=1751878&view=rev
Log:
STORM-1895,STORM-1633,STORM-118

Modified:
    storm/site/publish/feed.xml
    storm/site/publish/releases/0.10.0/feed.xml
    storm/site/publish/releases/0.10.1/feed.xml
    storm/site/publish/releases/1.0.0/Command-line-client.html
    storm/site/publish/releases/1.0.0/distcache-blobstore.html
    storm/site/publish/releases/1.0.0/images/transactional-batches.png
    storm/site/publish/releases/1.0.0/images/transactional-commit-flow.png
    storm/site/publish/releases/1.0.0/images/transactional-design-2.png
    storm/site/publish/releases/1.0.1/Command-line-client.html
    storm/site/publish/releases/1.0.1/distcache-blobstore.html
    storm/site/publish/releases/1.0.1/images/transactional-batches.png
    storm/site/publish/releases/1.0.1/images/transactional-commit-flow.png
    storm/site/publish/releases/1.0.1/images/transactional-design-2.png
    storm/site/publish/releases/2.0.0-SNAPSHOT/Command-line-client.html
    storm/site/publish/releases/2.0.0-SNAPSHOT/distcache-blobstore.html
    storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-batches.png
    storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-commit-flow.png
    storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-design-2.png
    storm/site/publish/releases/current/Command-line-client.html
    storm/site/publish/releases/current/distcache-blobstore.html
    storm/site/publish/releases/current/images/transactional-batches.png
    storm/site/publish/releases/current/images/transactional-commit-flow.png
    storm/site/publish/releases/current/images/transactional-design-2.png
    storm/site/releases/1.0.0/Command-line-client.md
    storm/site/releases/1.0.0/distcache-blobstore.md
    storm/site/releases/1.0.0/images/transactional-batches.png
    storm/site/releases/1.0.0/images/transactional-commit-flow.png
    storm/site/releases/1.0.0/images/transactional-design-2.png
    storm/site/releases/1.0.1/Command-line-client.md
    storm/site/releases/1.0.1/distcache-blobstore.md
    storm/site/releases/1.0.1/images/transactional-batches.png
    storm/site/releases/1.0.1/images/transactional-commit-flow.png
    storm/site/releases/1.0.1/images/transactional-design-2.png
    storm/site/releases/2.0.0-SNAPSHOT/Command-line-client.md
    storm/site/releases/2.0.0-SNAPSHOT/distcache-blobstore.md
    storm/site/releases/2.0.0-SNAPSHOT/images/transactional-batches.png
    storm/site/releases/2.0.0-SNAPSHOT/images/transactional-commit-flow.png
    storm/site/releases/2.0.0-SNAPSHOT/images/transactional-design-2.png

Modified: storm/site/publish/feed.xml
URL: http://svn.apache.org/viewvc/storm/site/publish/feed.xml?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/feed.xml (original)
+++ storm/site/publish/feed.xml Fri Jul  8 10:36:30 2016
@@ -5,8 +5,8 @@
     <description></description>
     <link>http://storm.apache.org/</link>
     <atom:link href="http://storm.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Thu, 09 Jun 2016 15:09:32 +0900</pubDate>
-    <lastBuildDate>Thu, 09 Jun 2016 15:09:32 +0900</lastBuildDate>
+    <pubDate>Fri, 08 Jul 2016 19:21:03 +0900</pubDate>
+    <lastBuildDate>Fri, 08 Jul 2016 19:21:03 +0900</lastBuildDate>
     <generator>Jekyll v3.1.2</generator>
     
       <item>

Modified: storm/site/publish/releases/0.10.0/feed.xml
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/0.10.0/feed.xml?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/0.10.0/feed.xml (original)
+++ storm/site/publish/releases/0.10.0/feed.xml Fri Jul  8 10:36:30 2016
@@ -5,8 +5,8 @@
     <description></description>
     <link>http://storm.apache.org/</link>
     <atom:link href="http://storm.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Thu, 09 Jun 2016 15:09:32 +0900</pubDate>
-    <lastBuildDate>Thu, 09 Jun 2016 15:09:32 +0900</lastBuildDate>
+    <pubDate>Fri, 08 Jul 2016 19:21:03 +0900</pubDate>
+    <lastBuildDate>Fri, 08 Jul 2016 19:21:03 +0900</lastBuildDate>
     <generator>Jekyll v3.1.2</generator>
     
       <item>

Modified: storm/site/publish/releases/0.10.1/feed.xml
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/0.10.1/feed.xml?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/0.10.1/feed.xml (original)
+++ storm/site/publish/releases/0.10.1/feed.xml Fri Jul  8 10:36:30 2016
@@ -5,8 +5,8 @@
     <description></description>
     <link>http://storm.apache.org/</link>
     <atom:link href="http://storm.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Thu, 09 Jun 2016 15:09:32 +0900</pubDate>
-    <lastBuildDate>Thu, 09 Jun 2016 15:09:32 +0900</lastBuildDate>
+    <pubDate>Fri, 08 Jul 2016 19:21:03 +0900</pubDate>
+    <lastBuildDate>Fri, 08 Jul 2016 19:21:03 +0900</lastBuildDate>
     <generator>Jekyll v3.1.2</generator>
     
       <item>

Modified: storm/site/publish/releases/1.0.0/Command-line-client.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.0/Command-line-client.html?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/1.0.0/Command-line-client.html (original)
+++ storm/site/publish/releases/1.0.0/Command-line-client.html Fri Jul  8 10:36:30 2016
@@ -156,6 +156,22 @@
 <li>supervisor</li>
 <li>ui</li>
 <li>drpc</li>
+<li>blobstore</li>
+<li>dev-zookeeper</li>
+<li>get-errors</li>
+<li>heartbeats</li>
+<li>kill_workers</li>
+<li>list</li>
+<li>logviewer</li>
+<li>monitor</li>
+<li>node-health-check</li>
+<li>pacemaker</li>
+<li>set_log_level</li>
+<li>shell</li>
+<li>sql</li>
+<li>upload-credentials</li>
+<li>version</li>
+<li>help</li>
 </ol>
 
 <h3 id="jar">jar</h3>
@@ -240,6 +256,156 @@
 
 <p>Launches a DRPC daemon. This command should be run under supervision with a tool like <a href="http://cr.yp.to/daemontools.html">daemontools</a> or <a href="http://mmonit.com/monit/">monit</a>. See <a href="Distributed-RPC.html">Distributed RPC</a> for more information.</p>
 
+<h3 id="blobstore">blobstore</h3>
+
+<p>Syntax: <code>storm blobstore cmd</code></p>
+
+<p>list [KEY...] - lists blobs currently in the blob store</p>
+
+<p>cat [-f FILE] KEY - read a blob and then either write it to a file, or STDOUT (requires read access).</p>
+
+<p>create [-f FILE] [-a ACL ...] [--replication-factor NUMBER] KEY - create a new blob. Contents comes from a FILE or STDIN. ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list.</p>
+
+<p>update [-f FILE] KEY - update the contents of a blob.  Contents comes from a FILE or STDIN (requires write access).</p>
+
+<p>delete KEY - delete an entry from the blob store (requires write access).</p>
+
+<p>set-acl [-s ACL] KEY - ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list (requires admin access).</p>
+
+<p>replication --read KEY - Used to read the replication factor of the blob.</p>
+
+<p>replication --update --replication-factor NUMBER KEY where NUMBER &gt; 0. It is used to update the replication factor of a blob.</p>
+
+<p>For example, the following would create a mytopo:data.tgz key using the data stored in data.tgz.  User alice would have full access, bob would have read/write access and everyone else would have read access.</p>
+
+<p>storm blobstore create mytopo:data.tgz -f data.tgz -a u:alice:rwa,u:bob:rw,o::r</p>
+
+<p>See <a href="distcache-blobstore.html">Blobstore(Distcahce)</a> for more information.</p>
+
+<h3 id="dev-zookeeper">dev-zookeeper</h3>
+
+<p>Syntax: <code>storm dev-zookeeper</code></p>
+
+<p>Launches a fresh Zookeeper server using &quot;dev.zookeeper.path&quot; as its local dir and &quot;storm.zookeeper.port&quot; as its port. This is only intended for development/testing, the Zookeeper instance launched is not configured to be used in production.</p>
+
+<h3 id="get-errors">get-errors</h3>
+
+<p>Syntax: <code>storm get-errors topology-name</code></p>
+
+<p>Get the latest error from the running topology. The returned result contains the key value pairs for component-name and component-error for the components in error. The result is returned in json format.</p>
+
+<h3 id="heartbeats">heartbeats</h3>
+
+<p>Syntax: <code>storm heartbeats [cmd]</code></p>
+
+<p>list PATH - lists heartbeats nodes under PATH currently in the ClusterState.
+get  PATH - Get the heartbeat data at PATH</p>
+
+<h3 id="kill_workers">kill_workers</h3>
+
+<p>Syntax: <code>storm kill_workers</code></p>
+
+<p>Kill the workers running on this supervisor. This command should be run on a supervisor node. If the cluster is running in secure mode, then user needs to have admin rights on the node to be able to successfully kill all workers.</p>
+
+<h3 id="list">list</h3>
+
+<p>Syntax: <code>storm list</code></p>
+
+<p>List the running topologies and their statuses.</p>
+
+<h3 id="logviewer">logviewer</h3>
+
+<p>Syntax: <code>storm logviewer</code></p>
+
+<p>Launches the log viewer daemon. It provides a web interface for viewing storm log files. This command should be run under supervision with a tool like daemontools or monit.</p>
+
+<p>See Setting up a Storm cluster for more information.(<a href="http://storm.apache.org/documentation/Setting-up-a-Storm-cluster">http://storm.apache.org/documentation/Setting-up-a-Storm-cluster</a>)</p>
+
+<h3 id="monitor">monitor</h3>
+
+<p>Syntax: <code>storm monitor topology-name [-i interval-secs] [-m component-id] [-s stream-id] [-w [emitted | transferred]]</code></p>
+
+<p>Monitor given topology&#39;s throughput interactively.
+One can specify poll-interval, component-id, stream-id, watch-item[emitted | transferred]
+  By default,
+    poll-interval is 4 seconds;
+    all component-ids will be list;
+    stream-id is &#39;default&#39;;
+    watch-item is &#39;emitted&#39;;</p>
+
+<h3 id="node-health-check">node-health-check</h3>
+
+<p>Syntax: <code>storm node-health-check</code></p>
+
+<p>Run health checks on the local supervisor.</p>
+
+<h3 id="pacemaker">pacemaker</h3>
+
+<p>Syntax: <code>storm pacemaker</code></p>
+
+<p>Launches the Pacemaker daemon. This command should be run under
+supervision with a tool like daemontools or monit.</p>
+
+<p>See Setting up a Storm cluster for more information.(<a href="http://storm.apache.org/documentation/Setting-up-a-Storm-cluster">http://storm.apache.org/documentation/Setting-up-a-Storm-cluster</a>)</p>
+
+<h3 id="set_log_level">set_log_level</h3>
+
+<p>Syntax: <code>storm set_log_level -l [logger name]=[log level][:optional timeout] -r [logger name] topology-name</code></p>
+
+<p>Dynamically change topology log levels</p>
+
+<p>where log level is one of: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF
+and timeout is integer seconds.</p>
+
+<p>e.g.
+  ./bin/storm set_log_level -l ROOT=DEBUG:30 topology-name</p>
+
+<p>Set the root logger&#39;s level to DEBUG for 30 seconds</p>
+
+<p>./bin/storm set_log_level -l com.myapp=WARN topology-name</p>
+
+<p>Set the com.myapp logger&#39;s level to WARN for 30 seconds</p>
+
+<p>./bin/storm set_log_level -l com.myapp=WARN -l com.myOtherLogger=ERROR:123 topology-name</p>
+
+<p>Set the com.myapp logger&#39;s level to WARN indifinitely, and com.myOtherLogger to ERROR for 123 seconds</p>
+
+<p>./bin/storm set_log_level -r com.myOtherLogger topology-name</p>
+
+<p>Clears settings, resetting back to the original level</p>
+
+<h3 id="shell">shell</h3>
+
+<p>Syntax: <code>storm shell resourcesdir command args</code></p>
+
+<p>Makes constructing jar and uploading to nimbus for using non JVM languages</p>
+
+<p>eg: <code>storm shell resources/ python topology.py arg1 arg2</code></p>
+
+<h3 id="sql">sql</h3>
+
+<p>Syntax: <code>storm sql sql-file topology-name</code></p>
+
+<p>Compiles the SQL statements into a Trident topology and submits it to Storm.</p>
+
+<h3 id="upload-credentials">upload-credentials</h3>
+
+<p>Syntax: <code>storm upload_credentials topology-name [credkey credvalue]*</code></p>
+
+<p>Uploads a new set of credentials to a running topology</p>
+
+<h3 id="version">version</h3>
+
+<p>Syntax: <code>storm version</code></p>
+
+<p>Prints the version number of this Storm release.</p>
+
+<h3 id="help">help</h3>
+
+<p>Syntax: <code>storm help [command]</code></p>
+
+<p>Print one help message or list of available commands</p>
+
 
 
 	          </div>

Modified: storm/site/publish/releases/1.0.0/distcache-blobstore.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.0/distcache-blobstore.html?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/1.0.0/distcache-blobstore.html (original)
+++ storm/site/publish/releases/1.0.0/distcache-blobstore.html Fri Jul  8 10:36:30 2016
@@ -194,7 +194,7 @@ The main stages can be depicted as follo
 <h3 id="blob-creation-command">Blob Creation Command</h3>
 
 <p>Blobs in the blobstore can be created through command line using the following command.</p>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 </code></pre></div>
 <p>The above command creates a blob with a key name “key1” corresponding to the file README.txt. 
 The access given to all users being read, write and admin with a replication factor of 4.</p>
@@ -462,7 +462,7 @@ The default is 60 seconds, a value of -1
 <p>To use the distributed cache feature, the user first has to &quot;introduce&quot; files
 that need to be cached and bind them to key strings. To achieve this, the user
 uses the &quot;blobstore create&quot; command of the storm executable, as follows:</p>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--repl-fctr NUMBER] [keyname]
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--replication-factor NUMBER] [keyname]
 </code></pre></div>
 <p>The contents come from a FILE, if provided by -f or --file option, otherwise
 from STDIN.<br>
@@ -482,14 +482,14 @@ following format:</p>
 <li>_ = ignored<br></li>
 </ul>
 
-<p>The replication factor can be set to a value greater than 1 using --repl-fctr.</p>
+<p>The replication factor can be set to a value greater than 1 using --replication-factor.</p>
 
 <p>Note: The replication right now is configurable for a hdfs blobstore but for a
 local blobstore the replication always stays at 1. For a hdfs blobstore
 the default replication is set to 3.</p>
 
 <h6 id="example">Example:</h6>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 </code></pre></div>
 <p>In the above example, the <em>README.txt</em> file is added to the distributed cache.
 It can be accessed using the key string &quot;<em>key1</em>&quot; for any topology that needs
@@ -579,7 +579,7 @@ requires read access.</p>
 (requires admin access).</p>
 
 <h3 id="update-the-replication-factor-for-a-blob">Update the replication factor for a blob</h3>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --update --repl-fctr 5 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --update --replication-factor 5 key1
 </code></pre></div>
 <h3 id="read-the-replication-factor-of-a-blob">Read the replication factor of a blob</h3>
 <div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --read key1

Modified: storm/site/publish/releases/1.0.0/images/transactional-batches.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.0/images/transactional-batches.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/1.0.0/images/transactional-commit-flow.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.0/images/transactional-commit-flow.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/1.0.0/images/transactional-design-2.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.0/images/transactional-design-2.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/1.0.1/Command-line-client.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.1/Command-line-client.html?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/1.0.1/Command-line-client.html (original)
+++ storm/site/publish/releases/1.0.1/Command-line-client.html Fri Jul  8 10:36:30 2016
@@ -156,6 +156,22 @@
 <li>supervisor</li>
 <li>ui</li>
 <li>drpc</li>
+<li>blobstore</li>
+<li>dev-zookeeper</li>
+<li>get-errors</li>
+<li>heartbeats</li>
+<li>kill_workers</li>
+<li>list</li>
+<li>logviewer</li>
+<li>monitor</li>
+<li>node-health-check</li>
+<li>pacemaker</li>
+<li>set_log_level</li>
+<li>shell</li>
+<li>sql</li>
+<li>upload-credentials</li>
+<li>version</li>
+<li>help</li>
 </ol>
 
 <h3 id="jar">jar</h3>
@@ -240,6 +256,156 @@
 
 <p>Launches a DRPC daemon. This command should be run under supervision with a tool like <a href="http://cr.yp.to/daemontools.html">daemontools</a> or <a href="http://mmonit.com/monit/">monit</a>. See <a href="Distributed-RPC.html">Distributed RPC</a> for more information.</p>
 
+<h3 id="blobstore">blobstore</h3>
+
+<p>Syntax: <code>storm blobstore cmd</code></p>
+
+<p>list [KEY...] - lists blobs currently in the blob store</p>
+
+<p>cat [-f FILE] KEY - read a blob and then either write it to a file, or STDOUT (requires read access).</p>
+
+<p>create [-f FILE] [-a ACL ...] [--replication-factor NUMBER] KEY - create a new blob. Contents comes from a FILE or STDIN. ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list.</p>
+
+<p>update [-f FILE] KEY - update the contents of a blob.  Contents comes from a FILE or STDIN (requires write access).</p>
+
+<p>delete KEY - delete an entry from the blob store (requires write access).</p>
+
+<p>set-acl [-s ACL] KEY - ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list (requires admin access).</p>
+
+<p>replication --read KEY - Used to read the replication factor of the blob.</p>
+
+<p>replication --update --replication-factor NUMBER KEY where NUMBER &gt; 0. It is used to update the replication factor of a blob.</p>
+
+<p>For example, the following would create a mytopo:data.tgz key using the data stored in data.tgz.  User alice would have full access, bob would have read/write access and everyone else would have read access.</p>
+
+<p>storm blobstore create mytopo:data.tgz -f data.tgz -a u:alice:rwa,u:bob:rw,o::r</p>
+
+<p>See <a href="distcache-blobstore.html">Blobstore(Distcahce)</a> for more information.</p>
+
+<h3 id="dev-zookeeper">dev-zookeeper</h3>
+
+<p>Syntax: <code>storm dev-zookeeper</code></p>
+
+<p>Launches a fresh Zookeeper server using &quot;dev.zookeeper.path&quot; as its local dir and &quot;storm.zookeeper.port&quot; as its port. This is only intended for development/testing, the Zookeeper instance launched is not configured to be used in production.</p>
+
+<h3 id="get-errors">get-errors</h3>
+
+<p>Syntax: <code>storm get-errors topology-name</code></p>
+
+<p>Get the latest error from the running topology. The returned result contains the key value pairs for component-name and component-error for the components in error. The result is returned in json format.</p>
+
+<h3 id="heartbeats">heartbeats</h3>
+
+<p>Syntax: <code>storm heartbeats [cmd]</code></p>
+
+<p>list PATH - lists heartbeats nodes under PATH currently in the ClusterState.
+get  PATH - Get the heartbeat data at PATH</p>
+
+<h3 id="kill_workers">kill_workers</h3>
+
+<p>Syntax: <code>storm kill_workers</code></p>
+
+<p>Kill the workers running on this supervisor. This command should be run on a supervisor node. If the cluster is running in secure mode, then user needs to have admin rights on the node to be able to successfully kill all workers.</p>
+
+<h3 id="list">list</h3>
+
+<p>Syntax: <code>storm list</code></p>
+
+<p>List the running topologies and their statuses.</p>
+
+<h3 id="logviewer">logviewer</h3>
+
+<p>Syntax: <code>storm logviewer</code></p>
+
+<p>Launches the log viewer daemon. It provides a web interface for viewing storm log files. This command should be run under supervision with a tool like daemontools or monit.</p>
+
+<p>See Setting up a Storm cluster for more information.(<a href="http://storm.apache.org/documentation/Setting-up-a-Storm-cluster">http://storm.apache.org/documentation/Setting-up-a-Storm-cluster</a>)</p>
+
+<h3 id="monitor">monitor</h3>
+
+<p>Syntax: <code>storm monitor topology-name [-i interval-secs] [-m component-id] [-s stream-id] [-w [emitted | transferred]]</code></p>
+
+<p>Monitor given topology&#39;s throughput interactively.
+One can specify poll-interval, component-id, stream-id, watch-item[emitted | transferred]
+  By default,
+    poll-interval is 4 seconds;
+    all component-ids will be list;
+    stream-id is &#39;default&#39;;
+    watch-item is &#39;emitted&#39;;</p>
+
+<h3 id="node-health-check">node-health-check</h3>
+
+<p>Syntax: <code>storm node-health-check</code></p>
+
+<p>Run health checks on the local supervisor.</p>
+
+<h3 id="pacemaker">pacemaker</h3>
+
+<p>Syntax: <code>storm pacemaker</code></p>
+
+<p>Launches the Pacemaker daemon. This command should be run under
+supervision with a tool like daemontools or monit.</p>
+
+<p>See Setting up a Storm cluster for more information.(<a href="http://storm.apache.org/documentation/Setting-up-a-Storm-cluster">http://storm.apache.org/documentation/Setting-up-a-Storm-cluster</a>)</p>
+
+<h3 id="set_log_level">set_log_level</h3>
+
+<p>Syntax: <code>storm set_log_level -l [logger name]=[log level][:optional timeout] -r [logger name] topology-name</code></p>
+
+<p>Dynamically change topology log levels</p>
+
+<p>where log level is one of: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF
+and timeout is integer seconds.</p>
+
+<p>e.g.
+  ./bin/storm set_log_level -l ROOT=DEBUG:30 topology-name</p>
+
+<p>Set the root logger&#39;s level to DEBUG for 30 seconds</p>
+
+<p>./bin/storm set_log_level -l com.myapp=WARN topology-name</p>
+
+<p>Set the com.myapp logger&#39;s level to WARN for 30 seconds</p>
+
+<p>./bin/storm set_log_level -l com.myapp=WARN -l com.myOtherLogger=ERROR:123 topology-name</p>
+
+<p>Set the com.myapp logger&#39;s level to WARN indifinitely, and com.myOtherLogger to ERROR for 123 seconds</p>
+
+<p>./bin/storm set_log_level -r com.myOtherLogger topology-name</p>
+
+<p>Clears settings, resetting back to the original level</p>
+
+<h3 id="shell">shell</h3>
+
+<p>Syntax: <code>storm shell resourcesdir command args</code></p>
+
+<p>Makes constructing jar and uploading to nimbus for using non JVM languages</p>
+
+<p>eg: <code>storm shell resources/ python topology.py arg1 arg2</code></p>
+
+<h3 id="sql">sql</h3>
+
+<p>Syntax: <code>storm sql sql-file topology-name</code></p>
+
+<p>Compiles the SQL statements into a Trident topology and submits it to Storm.</p>
+
+<h3 id="upload-credentials">upload-credentials</h3>
+
+<p>Syntax: <code>storm upload_credentials topology-name [credkey credvalue]*</code></p>
+
+<p>Uploads a new set of credentials to a running topology</p>
+
+<h3 id="version">version</h3>
+
+<p>Syntax: <code>storm version</code></p>
+
+<p>Prints the version number of this Storm release.</p>
+
+<h3 id="help">help</h3>
+
+<p>Syntax: <code>storm help [command]</code></p>
+
+<p>Print one help message or list of available commands</p>
+
 
 
 	          </div>

Modified: storm/site/publish/releases/1.0.1/distcache-blobstore.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.1/distcache-blobstore.html?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/1.0.1/distcache-blobstore.html (original)
+++ storm/site/publish/releases/1.0.1/distcache-blobstore.html Fri Jul  8 10:36:30 2016
@@ -194,7 +194,7 @@ The main stages can be depicted as follo
 <h3 id="blob-creation-command">Blob Creation Command</h3>
 
 <p>Blobs in the blobstore can be created through command line using the following command.</p>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 </code></pre></div>
 <p>The above command creates a blob with a key name “key1” corresponding to the file README.txt. 
 The access given to all users being read, write and admin with a replication factor of 4.</p>
@@ -462,7 +462,7 @@ The default is 60 seconds, a value of -1
 <p>To use the distributed cache feature, the user first has to &quot;introduce&quot; files
 that need to be cached and bind them to key strings. To achieve this, the user
 uses the &quot;blobstore create&quot; command of the storm executable, as follows:</p>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--repl-fctr NUMBER] [keyname]
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--replication-factor NUMBER] [keyname]
 </code></pre></div>
 <p>The contents come from a FILE, if provided by -f or --file option, otherwise
 from STDIN.<br>
@@ -482,14 +482,14 @@ following format:</p>
 <li>_ = ignored<br></li>
 </ul>
 
-<p>The replication factor can be set to a value greater than 1 using --repl-fctr.</p>
+<p>The replication factor can be set to a value greater than 1 using --replication-factor.</p>
 
 <p>Note: The replication right now is configurable for a hdfs blobstore but for a
 local blobstore the replication always stays at 1. For a hdfs blobstore
 the default replication is set to 3.</p>
 
 <h6 id="example">Example:</h6>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 </code></pre></div>
 <p>In the above example, the <em>README.txt</em> file is added to the distributed cache.
 It can be accessed using the key string &quot;<em>key1</em>&quot; for any topology that needs
@@ -579,7 +579,7 @@ requires read access.</p>
 (requires admin access).</p>
 
 <h3 id="update-the-replication-factor-for-a-blob">Update the replication factor for a blob</h3>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --update --repl-fctr 5 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --update --replication-factor 5 key1
 </code></pre></div>
 <h3 id="read-the-replication-factor-of-a-blob">Read the replication factor of a blob</h3>
 <div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --read key1

Modified: storm/site/publish/releases/1.0.1/images/transactional-batches.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.1/images/transactional-batches.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/1.0.1/images/transactional-commit-flow.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.1/images/transactional-commit-flow.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/1.0.1/images/transactional-design-2.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/1.0.1/images/transactional-design-2.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/Command-line-client.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/Command-line-client.html?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/2.0.0-SNAPSHOT/Command-line-client.html (original)
+++ storm/site/publish/releases/2.0.0-SNAPSHOT/Command-line-client.html Fri Jul  8 10:36:30 2016
@@ -156,6 +156,22 @@
 <li>supervisor</li>
 <li>ui</li>
 <li>drpc</li>
+<li>blobstore</li>
+<li>dev-zookeeper</li>
+<li>get-errors</li>
+<li>heartbeats</li>
+<li>kill_workers</li>
+<li>list</li>
+<li>logviewer</li>
+<li>monitor</li>
+<li>node-health-check</li>
+<li>pacemaker</li>
+<li>set_log_level</li>
+<li>shell</li>
+<li>sql</li>
+<li>upload-credentials</li>
+<li>version</li>
+<li>help</li>
 </ol>
 
 <h3 id="jar">jar</h3>
@@ -240,6 +256,156 @@
 
 <p>Launches a DRPC daemon. This command should be run under supervision with a tool like <a href="http://cr.yp.to/daemontools.html">daemontools</a> or <a href="http://mmonit.com/monit/">monit</a>. See <a href="Distributed-RPC.html">Distributed RPC</a> for more information.</p>
 
+<h3 id="blobstore">blobstore</h3>
+
+<p>Syntax: <code>storm blobstore cmd</code></p>
+
+<p>list [KEY...] - lists blobs currently in the blob store</p>
+
+<p>cat [-f FILE] KEY - read a blob and then either write it to a file, or STDOUT (requires read access).</p>
+
+<p>create [-f FILE] [-a ACL ...] [--replication-factor NUMBER] KEY - create a new blob. Contents comes from a FILE or STDIN. ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list.</p>
+
+<p>update [-f FILE] KEY - update the contents of a blob.  Contents comes from a FILE or STDIN (requires write access).</p>
+
+<p>delete KEY - delete an entry from the blob store (requires write access).</p>
+
+<p>set-acl [-s ACL] KEY - ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list (requires admin access).</p>
+
+<p>replication --read KEY - Used to read the replication factor of the blob.</p>
+
+<p>replication --update --replication-factor NUMBER KEY where NUMBER &gt; 0. It is used to update the replication factor of a blob.</p>
+
+<p>For example, the following would create a mytopo:data.tgz key using the data stored in data.tgz.  User alice would have full access, bob would have read/write access and everyone else would have read access.</p>
+
+<p>storm blobstore create mytopo:data.tgz -f data.tgz -a u:alice:rwa,u:bob:rw,o::r</p>
+
+<p>See <a href="distcache-blobstore.html">Blobstore(Distcahce)</a> for more information.</p>
+
+<h3 id="dev-zookeeper">dev-zookeeper</h3>
+
+<p>Syntax: <code>storm dev-zookeeper</code></p>
+
+<p>Launches a fresh Zookeeper server using &quot;dev.zookeeper.path&quot; as its local dir and &quot;storm.zookeeper.port&quot; as its port. This is only intended for development/testing, the Zookeeper instance launched is not configured to be used in production.</p>
+
+<h3 id="get-errors">get-errors</h3>
+
+<p>Syntax: <code>storm get-errors topology-name</code></p>
+
+<p>Get the latest error from the running topology. The returned result contains the key value pairs for component-name and component-error for the components in error. The result is returned in json format.</p>
+
+<h3 id="heartbeats">heartbeats</h3>
+
+<p>Syntax: <code>storm heartbeats [cmd]</code></p>
+
+<p>list PATH - lists heartbeats nodes under PATH currently in the ClusterState.
+get  PATH - Get the heartbeat data at PATH</p>
+
+<h3 id="kill_workers">kill_workers</h3>
+
+<p>Syntax: <code>storm kill_workers</code></p>
+
+<p>Kill the workers running on this supervisor. This command should be run on a supervisor node. If the cluster is running in secure mode, then user needs to have admin rights on the node to be able to successfully kill all workers.</p>
+
+<h3 id="list">list</h3>
+
+<p>Syntax: <code>storm list</code></p>
+
+<p>List the running topologies and their statuses.</p>
+
+<h3 id="logviewer">logviewer</h3>
+
+<p>Syntax: <code>storm logviewer</code></p>
+
+<p>Launches the log viewer daemon. It provides a web interface for viewing storm log files. This command should be run under supervision with a tool like daemontools or monit.</p>
+
+<p>See Setting up a Storm cluster for more information.(<a href="http://storm.apache.org/documentation/Setting-up-a-Storm-cluster">http://storm.apache.org/documentation/Setting-up-a-Storm-cluster</a>)</p>
+
+<h3 id="monitor">monitor</h3>
+
+<p>Syntax: <code>storm monitor topology-name [-i interval-secs] [-m component-id] [-s stream-id] [-w [emitted | transferred]]</code></p>
+
+<p>Monitor given topology&#39;s throughput interactively.
+One can specify poll-interval, component-id, stream-id, watch-item[emitted | transferred]
+  By default,
+    poll-interval is 4 seconds;
+    all component-ids will be list;
+    stream-id is &#39;default&#39;;
+    watch-item is &#39;emitted&#39;;</p>
+
+<h3 id="node-health-check">node-health-check</h3>
+
+<p>Syntax: <code>storm node-health-check</code></p>
+
+<p>Run health checks on the local supervisor.</p>
+
+<h3 id="pacemaker">pacemaker</h3>
+
+<p>Syntax: <code>storm pacemaker</code></p>
+
+<p>Launches the Pacemaker daemon. This command should be run under
+supervision with a tool like daemontools or monit.</p>
+
+<p>See Setting up a Storm cluster for more information.(<a href="http://storm.apache.org/documentation/Setting-up-a-Storm-cluster">http://storm.apache.org/documentation/Setting-up-a-Storm-cluster</a>)</p>
+
+<h3 id="set_log_level">set_log_level</h3>
+
+<p>Syntax: <code>storm set_log_level -l [logger name]=[log level][:optional timeout] -r [logger name] topology-name</code></p>
+
+<p>Dynamically change topology log levels</p>
+
+<p>where log level is one of: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF
+and timeout is integer seconds.</p>
+
+<p>e.g.
+  ./bin/storm set_log_level -l ROOT=DEBUG:30 topology-name</p>
+
+<p>Set the root logger&#39;s level to DEBUG for 30 seconds</p>
+
+<p>./bin/storm set_log_level -l com.myapp=WARN topology-name</p>
+
+<p>Set the com.myapp logger&#39;s level to WARN for 30 seconds</p>
+
+<p>./bin/storm set_log_level -l com.myapp=WARN -l com.myOtherLogger=ERROR:123 topology-name</p>
+
+<p>Set the com.myapp logger&#39;s level to WARN indifinitely, and com.myOtherLogger to ERROR for 123 seconds</p>
+
+<p>./bin/storm set_log_level -r com.myOtherLogger topology-name</p>
+
+<p>Clears settings, resetting back to the original level</p>
+
+<h3 id="shell">shell</h3>
+
+<p>Syntax: <code>storm shell resourcesdir command args</code></p>
+
+<p>Makes constructing jar and uploading to nimbus for using non JVM languages</p>
+
+<p>eg: <code>storm shell resources/ python topology.py arg1 arg2</code></p>
+
+<h3 id="sql">sql</h3>
+
+<p>Syntax: <code>storm sql sql-file topology-name</code></p>
+
+<p>Compiles the SQL statements into a Trident topology and submits it to Storm.</p>
+
+<h3 id="upload-credentials">upload-credentials</h3>
+
+<p>Syntax: <code>storm upload_credentials topology-name [credkey credvalue]*</code></p>
+
+<p>Uploads a new set of credentials to a running topology</p>
+
+<h3 id="version">version</h3>
+
+<p>Syntax: <code>storm version</code></p>
+
+<p>Prints the version number of this Storm release.</p>
+
+<h3 id="help">help</h3>
+
+<p>Syntax: <code>storm help [command]</code></p>
+
+<p>Print one help message or list of available commands</p>
+
 
 
 	          </div>

Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/distcache-blobstore.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/distcache-blobstore.html?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/2.0.0-SNAPSHOT/distcache-blobstore.html (original)
+++ storm/site/publish/releases/2.0.0-SNAPSHOT/distcache-blobstore.html Fri Jul  8 10:36:30 2016
@@ -194,7 +194,7 @@ The main stages can be depicted as follo
 <h3 id="blob-creation-command">Blob Creation Command</h3>
 
 <p>Blobs in the blobstore can be created through command line using the following command.</p>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 </code></pre></div>
 <p>The above command creates a blob with a key name “key1” corresponding to the file README.txt. 
 The access given to all users being read, write and admin with a replication factor of 4.</p>
@@ -462,7 +462,7 @@ The default is 60 seconds, a value of -1
 <p>To use the distributed cache feature, the user first has to &quot;introduce&quot; files
 that need to be cached and bind them to key strings. To achieve this, the user
 uses the &quot;blobstore create&quot; command of the storm executable, as follows:</p>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--repl-fctr NUMBER] [keyname]
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--replication-factor NUMBER] [keyname]
 </code></pre></div>
 <p>The contents come from a FILE, if provided by -f or --file option, otherwise
 from STDIN.<br>
@@ -482,14 +482,14 @@ following format:</p>
 <li>_ = ignored<br></li>
 </ul>
 
-<p>The replication factor can be set to a value greater than 1 using --repl-fctr.</p>
+<p>The replication factor can be set to a value greater than 1 using --replication-factor.</p>
 
 <p>Note: The replication right now is configurable for a hdfs blobstore but for a
 local blobstore the replication always stays at 1. For a hdfs blobstore
 the default replication is set to 3.</p>
 
 <h6 id="example">Example:</h6>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 </code></pre></div>
 <p>In the above example, the <em>README.txt</em> file is added to the distributed cache.
 It can be accessed using the key string &quot;<em>key1</em>&quot; for any topology that needs
@@ -579,7 +579,7 @@ requires read access.</p>
 (requires admin access).</p>
 
 <h3 id="update-the-replication-factor-for-a-blob">Update the replication factor for a blob</h3>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --update --repl-fctr 5 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --update --replication-factor 5 key1
 </code></pre></div>
 <h3 id="read-the-replication-factor-of-a-blob">Read the replication factor of a blob</h3>
 <div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --read key1

Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-batches.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-batches.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-commit-flow.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-commit-flow.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-design-2.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/images/transactional-design-2.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/current/Command-line-client.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Command-line-client.html?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/current/Command-line-client.html (original)
+++ storm/site/publish/releases/current/Command-line-client.html Fri Jul  8 10:36:30 2016
@@ -156,6 +156,22 @@
 <li>supervisor</li>
 <li>ui</li>
 <li>drpc</li>
+<li>blobstore</li>
+<li>dev-zookeeper</li>
+<li>get-errors</li>
+<li>heartbeats</li>
+<li>kill_workers</li>
+<li>list</li>
+<li>logviewer</li>
+<li>monitor</li>
+<li>node-health-check</li>
+<li>pacemaker</li>
+<li>set_log_level</li>
+<li>shell</li>
+<li>sql</li>
+<li>upload-credentials</li>
+<li>version</li>
+<li>help</li>
 </ol>
 
 <h3 id="jar">jar</h3>
@@ -240,6 +256,156 @@
 
 <p>Launches a DRPC daemon. This command should be run under supervision with a tool like <a href="http://cr.yp.to/daemontools.html">daemontools</a> or <a href="http://mmonit.com/monit/">monit</a>. See <a href="Distributed-RPC.html">Distributed RPC</a> for more information.</p>
 
+<h3 id="blobstore">blobstore</h3>
+
+<p>Syntax: <code>storm blobstore cmd</code></p>
+
+<p>list [KEY...] - lists blobs currently in the blob store</p>
+
+<p>cat [-f FILE] KEY - read a blob and then either write it to a file, or STDOUT (requires read access).</p>
+
+<p>create [-f FILE] [-a ACL ...] [--replication-factor NUMBER] KEY - create a new blob. Contents comes from a FILE or STDIN. ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list.</p>
+
+<p>update [-f FILE] KEY - update the contents of a blob.  Contents comes from a FILE or STDIN (requires write access).</p>
+
+<p>delete KEY - delete an entry from the blob store (requires write access).</p>
+
+<p>set-acl [-s ACL] KEY - ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list (requires admin access).</p>
+
+<p>replication --read KEY - Used to read the replication factor of the blob.</p>
+
+<p>replication --update --replication-factor NUMBER KEY where NUMBER &gt; 0. It is used to update the replication factor of a blob.</p>
+
+<p>For example, the following would create a mytopo:data.tgz key using the data stored in data.tgz.  User alice would have full access, bob would have read/write access and everyone else would have read access.</p>
+
+<p>storm blobstore create mytopo:data.tgz -f data.tgz -a u:alice:rwa,u:bob:rw,o::r</p>
+
+<p>See <a href="distcache-blobstore.html">Blobstore(Distcahce)</a> for more information.</p>
+
+<h3 id="dev-zookeeper">dev-zookeeper</h3>
+
+<p>Syntax: <code>storm dev-zookeeper</code></p>
+
+<p>Launches a fresh Zookeeper server using &quot;dev.zookeeper.path&quot; as its local dir and &quot;storm.zookeeper.port&quot; as its port. This is only intended for development/testing, the Zookeeper instance launched is not configured to be used in production.</p>
+
+<h3 id="get-errors">get-errors</h3>
+
+<p>Syntax: <code>storm get-errors topology-name</code></p>
+
+<p>Get the latest error from the running topology. The returned result contains the key value pairs for component-name and component-error for the components in error. The result is returned in json format.</p>
+
+<h3 id="heartbeats">heartbeats</h3>
+
+<p>Syntax: <code>storm heartbeats [cmd]</code></p>
+
+<p>list PATH - lists heartbeats nodes under PATH currently in the ClusterState.
+get  PATH - Get the heartbeat data at PATH</p>
+
+<h3 id="kill_workers">kill_workers</h3>
+
+<p>Syntax: <code>storm kill_workers</code></p>
+
+<p>Kill the workers running on this supervisor. This command should be run on a supervisor node. If the cluster is running in secure mode, then user needs to have admin rights on the node to be able to successfully kill all workers.</p>
+
+<h3 id="list">list</h3>
+
+<p>Syntax: <code>storm list</code></p>
+
+<p>List the running topologies and their statuses.</p>
+
+<h3 id="logviewer">logviewer</h3>
+
+<p>Syntax: <code>storm logviewer</code></p>
+
+<p>Launches the log viewer daemon. It provides a web interface for viewing storm log files. This command should be run under supervision with a tool like daemontools or monit.</p>
+
+<p>See Setting up a Storm cluster for more information.(<a href="http://storm.apache.org/documentation/Setting-up-a-Storm-cluster">http://storm.apache.org/documentation/Setting-up-a-Storm-cluster</a>)</p>
+
+<h3 id="monitor">monitor</h3>
+
+<p>Syntax: <code>storm monitor topology-name [-i interval-secs] [-m component-id] [-s stream-id] [-w [emitted | transferred]]</code></p>
+
+<p>Monitor given topology&#39;s throughput interactively.
+One can specify poll-interval, component-id, stream-id, watch-item[emitted | transferred]
+  By default,
+    poll-interval is 4 seconds;
+    all component-ids will be list;
+    stream-id is &#39;default&#39;;
+    watch-item is &#39;emitted&#39;;</p>
+
+<h3 id="node-health-check">node-health-check</h3>
+
+<p>Syntax: <code>storm node-health-check</code></p>
+
+<p>Run health checks on the local supervisor.</p>
+
+<h3 id="pacemaker">pacemaker</h3>
+
+<p>Syntax: <code>storm pacemaker</code></p>
+
+<p>Launches the Pacemaker daemon. This command should be run under
+supervision with a tool like daemontools or monit.</p>
+
+<p>See Setting up a Storm cluster for more information.(<a href="http://storm.apache.org/documentation/Setting-up-a-Storm-cluster">http://storm.apache.org/documentation/Setting-up-a-Storm-cluster</a>)</p>
+
+<h3 id="set_log_level">set_log_level</h3>
+
+<p>Syntax: <code>storm set_log_level -l [logger name]=[log level][:optional timeout] -r [logger name] topology-name</code></p>
+
+<p>Dynamically change topology log levels</p>
+
+<p>where log level is one of: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF
+and timeout is integer seconds.</p>
+
+<p>e.g.
+  ./bin/storm set_log_level -l ROOT=DEBUG:30 topology-name</p>
+
+<p>Set the root logger&#39;s level to DEBUG for 30 seconds</p>
+
+<p>./bin/storm set_log_level -l com.myapp=WARN topology-name</p>
+
+<p>Set the com.myapp logger&#39;s level to WARN for 30 seconds</p>
+
+<p>./bin/storm set_log_level -l com.myapp=WARN -l com.myOtherLogger=ERROR:123 topology-name</p>
+
+<p>Set the com.myapp logger&#39;s level to WARN indifinitely, and com.myOtherLogger to ERROR for 123 seconds</p>
+
+<p>./bin/storm set_log_level -r com.myOtherLogger topology-name</p>
+
+<p>Clears settings, resetting back to the original level</p>
+
+<h3 id="shell">shell</h3>
+
+<p>Syntax: <code>storm shell resourcesdir command args</code></p>
+
+<p>Makes constructing jar and uploading to nimbus for using non JVM languages</p>
+
+<p>eg: <code>storm shell resources/ python topology.py arg1 arg2</code></p>
+
+<h3 id="sql">sql</h3>
+
+<p>Syntax: <code>storm sql sql-file topology-name</code></p>
+
+<p>Compiles the SQL statements into a Trident topology and submits it to Storm.</p>
+
+<h3 id="upload-credentials">upload-credentials</h3>
+
+<p>Syntax: <code>storm upload_credentials topology-name [credkey credvalue]*</code></p>
+
+<p>Uploads a new set of credentials to a running topology</p>
+
+<h3 id="version">version</h3>
+
+<p>Syntax: <code>storm version</code></p>
+
+<p>Prints the version number of this Storm release.</p>
+
+<h3 id="help">help</h3>
+
+<p>Syntax: <code>storm help [command]</code></p>
+
+<p>Print one help message or list of available commands</p>
+
 
 
 	          </div>

Modified: storm/site/publish/releases/current/distcache-blobstore.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/distcache-blobstore.html?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/publish/releases/current/distcache-blobstore.html (original)
+++ storm/site/publish/releases/current/distcache-blobstore.html Fri Jul  8 10:36:30 2016
@@ -194,7 +194,7 @@ The main stages can be depicted as follo
 <h3 id="blob-creation-command">Blob Creation Command</h3>
 
 <p>Blobs in the blobstore can be created through command line using the following command.</p>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 </code></pre></div>
 <p>The above command creates a blob with a key name “key1” corresponding to the file README.txt. 
 The access given to all users being read, write and admin with a replication factor of 4.</p>
@@ -462,7 +462,7 @@ The default is 60 seconds, a value of -1
 <p>To use the distributed cache feature, the user first has to &quot;introduce&quot; files
 that need to be cached and bind them to key strings. To achieve this, the user
 uses the &quot;blobstore create&quot; command of the storm executable, as follows:</p>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--repl-fctr NUMBER] [keyname]
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--replication-factor NUMBER] [keyname]
 </code></pre></div>
 <p>The contents come from a FILE, if provided by -f or --file option, otherwise
 from STDIN.<br>
@@ -482,14 +482,14 @@ following format:</p>
 <li>_ = ignored<br></li>
 </ul>
 
-<p>The replication factor can be set to a value greater than 1 using --repl-fctr.</p>
+<p>The replication factor can be set to a value greater than 1 using --replication-factor.</p>
 
 <p>Note: The replication right now is configurable for a hdfs blobstore but for a
 local blobstore the replication always stays at 1. For a hdfs blobstore
 the default replication is set to 3.</p>
 
 <h6 id="example">Example:</h6>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 </code></pre></div>
 <p>In the above example, the <em>README.txt</em> file is added to the distributed cache.
 It can be accessed using the key string &quot;<em>key1</em>&quot; for any topology that needs
@@ -579,7 +579,7 @@ requires read access.</p>
 (requires admin access).</p>
 
 <h3 id="update-the-replication-factor-for-a-blob">Update the replication factor for a blob</h3>
-<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --update --repl-fctr 5 key1
+<div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --update --replication-factor 5 key1
 </code></pre></div>
 <h3 id="read-the-replication-factor-of-a-blob">Read the replication factor of a blob</h3>
 <div class="highlight"><pre><code class="language-" data-lang="">storm blobstore replication --read key1

Modified: storm/site/publish/releases/current/images/transactional-batches.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/images/transactional-batches.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/current/images/transactional-commit-flow.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/images/transactional-commit-flow.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/publish/releases/current/images/transactional-design-2.png
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/images/transactional-design-2.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/1.0.0/Command-line-client.md
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.0/Command-line-client.md?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/releases/1.0.0/Command-line-client.md (original)
+++ storm/site/releases/1.0.0/Command-line-client.md Fri Jul  8 10:36:30 2016
@@ -20,6 +20,22 @@ These commands are:
 1. supervisor
 1. ui
 1. drpc
+1. blobstore
+1. dev-zookeeper
+1. get-errors
+1. heartbeats
+1. kill_workers
+1. list
+1. logviewer
+1. monitor
+1. node-health-check
+1. pacemaker
+1. set_log_level
+1. shell
+1. sql
+1. upload-credentials
+1. version
+1. help
 
 ### jar
 
@@ -102,3 +118,152 @@ Launches the UI daemon. The UI provides
 Syntax: `storm drpc`
 
 Launches a DRPC daemon. This command should be run under supervision with a tool like [daemontools](http://cr.yp.to/daemontools.html) or [monit](http://mmonit.com/monit/). See [Distributed RPC](Distributed-RPC.html) for more information.
+
+### blobstore
+
+Syntax: `storm blobstore cmd`
+
+list [KEY...] - lists blobs currently in the blob store
+
+cat [-f FILE] KEY - read a blob and then either write it to a file, or STDOUT (requires read access).
+
+create [-f FILE] [-a ACL ...] [--replication-factor NUMBER] KEY - create a new blob. Contents comes from a FILE or STDIN. ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list.
+
+update [-f FILE] KEY - update the contents of a blob.  Contents comes from a FILE or STDIN (requires write access).
+
+delete KEY - delete an entry from the blob store (requires write access).
+
+set-acl [-s ACL] KEY - ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list (requires admin access).
+
+replication --read KEY - Used to read the replication factor of the blob.
+
+replication --update --replication-factor NUMBER KEY where NUMBER > 0. It is used to update the replication factor of a blob.
+
+For example, the following would create a mytopo:data.tgz key using the data stored in data.tgz.  User alice would have full access, bob would have read/write access and everyone else would have read access.
+
+storm blobstore create mytopo:data.tgz -f data.tgz -a u:alice:rwa,u:bob:rw,o::r
+
+See [Blobstore(Distcahce)](distcache-blobstore.html) for more information.
+
+### dev-zookeeper
+
+Syntax: `storm dev-zookeeper`
+
+Launches a fresh Zookeeper server using "dev.zookeeper.path" as its local dir and "storm.zookeeper.port" as its port. This is only intended for development/testing, the Zookeeper instance launched is not configured to be used in production.
+
+### get-errors
+
+Syntax: `storm get-errors topology-name`
+
+Get the latest error from the running topology. The returned result contains the key value pairs for component-name and component-error for the components in error. The result is returned in json format.
+
+### heartbeats
+
+Syntax: `storm heartbeats [cmd]`
+
+list PATH - lists heartbeats nodes under PATH currently in the ClusterState.
+get  PATH - Get the heartbeat data at PATH
+
+### kill_workers
+
+Syntax: `storm kill_workers`
+
+Kill the workers running on this supervisor. This command should be run on a supervisor node. If the cluster is running in secure mode, then user needs to have admin rights on the node to be able to successfully kill all workers.
+
+### list
+
+Syntax: `storm list`
+
+List the running topologies and their statuses.
+
+### logviewer
+
+Syntax: `storm logviewer`
+
+Launches the log viewer daemon. It provides a web interface for viewing storm log files. This command should be run under supervision with a tool like daemontools or monit.
+
+See Setting up a Storm cluster for more information.(http://storm.apache.org/documentation/Setting-up-a-Storm-cluster)
+
+### monitor
+
+Syntax: `storm monitor topology-name [-i interval-secs] [-m component-id] [-s stream-id] [-w [emitted | transferred]]`
+
+Monitor given topology's throughput interactively.
+One can specify poll-interval, component-id, stream-id, watch-item[emitted | transferred]
+  By default,
+    poll-interval is 4 seconds;
+    all component-ids will be list;
+    stream-id is 'default';
+    watch-item is 'emitted';
+
+### node-health-check
+
+Syntax: `storm node-health-check`
+
+Run health checks on the local supervisor.
+
+### pacemaker
+
+Syntax: `storm pacemaker`
+
+Launches the Pacemaker daemon. This command should be run under
+supervision with a tool like daemontools or monit.
+
+See Setting up a Storm cluster for more information.(http://storm.apache.org/documentation/Setting-up-a-Storm-cluster)
+
+### set_log_level
+
+Syntax: `storm set_log_level -l [logger name]=[log level][:optional timeout] -r [logger name] topology-name`
+
+Dynamically change topology log levels
+    
+where log level is one of: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF
+and timeout is integer seconds.
+
+e.g.
+  ./bin/storm set_log_level -l ROOT=DEBUG:30 topology-name
+
+  Set the root logger's level to DEBUG for 30 seconds
+
+  ./bin/storm set_log_level -l com.myapp=WARN topology-name
+
+  Set the com.myapp logger's level to WARN for 30 seconds
+
+  ./bin/storm set_log_level -l com.myapp=WARN -l com.myOtherLogger=ERROR:123 topology-name
+
+  Set the com.myapp logger's level to WARN indifinitely, and com.myOtherLogger to ERROR for 123 seconds
+
+  ./bin/storm set_log_level -r com.myOtherLogger topology-name
+
+  Clears settings, resetting back to the original level
+
+### shell
+
+Syntax: `storm shell resourcesdir command args`
+
+Makes constructing jar and uploading to nimbus for using non JVM languages
+
+eg: `storm shell resources/ python topology.py arg1 arg2`
+
+### sql
+
+Syntax: `storm sql sql-file topology-name`
+
+Compiles the SQL statements into a Trident topology and submits it to Storm.
+
+### upload-credentials
+
+Syntax: `storm upload_credentials topology-name [credkey credvalue]*`
+
+Uploads a new set of credentials to a running topology
+
+### version
+
+Syntax: `storm version`
+
+Prints the version number of this Storm release.
+
+### help
+Syntax: `storm help [command]`
+
+Print one help message or list of available commands

Modified: storm/site/releases/1.0.0/distcache-blobstore.md
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.0/distcache-blobstore.md?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/releases/1.0.0/distcache-blobstore.md (original)
+++ storm/site/releases/1.0.0/distcache-blobstore.md Fri Jul  8 10:36:30 2016
@@ -55,7 +55,7 @@ The main stages can be depicted as follo
 Blobs in the blobstore can be created through command line using the following command.
 
 ```
-storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 ```
 
 The above command creates a blob with a key name “key1” corresponding to the file README.txt. 
@@ -324,7 +324,7 @@ that need to be cached and bind them to
 uses the "blobstore create" command of the storm executable, as follows:
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--repl-fctr NUMBER] [keyname]
+storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--replication-factor NUMBER] [keyname]
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The contents come from a FILE, if provided by -f or --file option, otherwise
@@ -346,7 +346,7 @@ where:
 * a = admin access  
 * _ = ignored  
 
-The replication factor can be set to a value greater than 1 using --repl-fctr.
+The replication factor can be set to a value greater than 1 using --replication-factor.
 
 Note: The replication right now is configurable for a hdfs blobstore but for a
 local blobstore the replication always stays at 1. For a hdfs blobstore
@@ -355,7 +355,7 @@ the default replication is set to 3.
 ###### Example:  
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In the above example, the *README.txt* file is added to the distributed cache.
@@ -475,7 +475,7 @@ ACL is in the form [uo]:[username]:[r-][
 ### Update the replication factor for a blob
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore replication --update --repl-fctr 5 key1
+storm blobstore replication --update --replication-factor 5 key1
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 ### Read the replication factor of a blob

Modified: storm/site/releases/1.0.0/images/transactional-batches.png
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.0/images/transactional-batches.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/1.0.0/images/transactional-commit-flow.png
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.0/images/transactional-commit-flow.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/1.0.0/images/transactional-design-2.png
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.0/images/transactional-design-2.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/1.0.1/Command-line-client.md
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.1/Command-line-client.md?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/releases/1.0.1/Command-line-client.md (original)
+++ storm/site/releases/1.0.1/Command-line-client.md Fri Jul  8 10:36:30 2016
@@ -20,6 +20,22 @@ These commands are:
 1. supervisor
 1. ui
 1. drpc
+1. blobstore
+1. dev-zookeeper
+1. get-errors
+1. heartbeats
+1. kill_workers
+1. list
+1. logviewer
+1. monitor
+1. node-health-check
+1. pacemaker
+1. set_log_level
+1. shell
+1. sql
+1. upload-credentials
+1. version
+1. help
 
 ### jar
 
@@ -102,3 +118,152 @@ Launches the UI daemon. The UI provides
 Syntax: `storm drpc`
 
 Launches a DRPC daemon. This command should be run under supervision with a tool like [daemontools](http://cr.yp.to/daemontools.html) or [monit](http://mmonit.com/monit/). See [Distributed RPC](Distributed-RPC.html) for more information.
+
+### blobstore
+
+Syntax: `storm blobstore cmd`
+
+list [KEY...] - lists blobs currently in the blob store
+
+cat [-f FILE] KEY - read a blob and then either write it to a file, or STDOUT (requires read access).
+
+create [-f FILE] [-a ACL ...] [--replication-factor NUMBER] KEY - create a new blob. Contents comes from a FILE or STDIN. ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list.
+
+update [-f FILE] KEY - update the contents of a blob.  Contents comes from a FILE or STDIN (requires write access).
+
+delete KEY - delete an entry from the blob store (requires write access).
+
+set-acl [-s ACL] KEY - ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list (requires admin access).
+
+replication --read KEY - Used to read the replication factor of the blob.
+
+replication --update --replication-factor NUMBER KEY where NUMBER > 0. It is used to update the replication factor of a blob.
+
+For example, the following would create a mytopo:data.tgz key using the data stored in data.tgz.  User alice would have full access, bob would have read/write access and everyone else would have read access.
+
+storm blobstore create mytopo:data.tgz -f data.tgz -a u:alice:rwa,u:bob:rw,o::r
+
+See [Blobstore(Distcahce)](distcache-blobstore.html) for more information.
+
+### dev-zookeeper
+
+Syntax: `storm dev-zookeeper`
+
+Launches a fresh Zookeeper server using "dev.zookeeper.path" as its local dir and "storm.zookeeper.port" as its port. This is only intended for development/testing, the Zookeeper instance launched is not configured to be used in production.
+
+### get-errors
+
+Syntax: `storm get-errors topology-name`
+
+Get the latest error from the running topology. The returned result contains the key value pairs for component-name and component-error for the components in error. The result is returned in json format.
+
+### heartbeats
+
+Syntax: `storm heartbeats [cmd]`
+
+list PATH - lists heartbeats nodes under PATH currently in the ClusterState.
+get  PATH - Get the heartbeat data at PATH
+
+### kill_workers
+
+Syntax: `storm kill_workers`
+
+Kill the workers running on this supervisor. This command should be run on a supervisor node. If the cluster is running in secure mode, then user needs to have admin rights on the node to be able to successfully kill all workers.
+
+### list
+
+Syntax: `storm list`
+
+List the running topologies and their statuses.
+
+### logviewer
+
+Syntax: `storm logviewer`
+
+Launches the log viewer daemon. It provides a web interface for viewing storm log files. This command should be run under supervision with a tool like daemontools or monit.
+
+See Setting up a Storm cluster for more information.(http://storm.apache.org/documentation/Setting-up-a-Storm-cluster)
+
+### monitor
+
+Syntax: `storm monitor topology-name [-i interval-secs] [-m component-id] [-s stream-id] [-w [emitted | transferred]]`
+
+Monitor given topology's throughput interactively.
+One can specify poll-interval, component-id, stream-id, watch-item[emitted | transferred]
+  By default,
+    poll-interval is 4 seconds;
+    all component-ids will be list;
+    stream-id is 'default';
+    watch-item is 'emitted';
+
+### node-health-check
+
+Syntax: `storm node-health-check`
+
+Run health checks on the local supervisor.
+
+### pacemaker
+
+Syntax: `storm pacemaker`
+
+Launches the Pacemaker daemon. This command should be run under
+supervision with a tool like daemontools or monit.
+
+See Setting up a Storm cluster for more information.(http://storm.apache.org/documentation/Setting-up-a-Storm-cluster)
+
+### set_log_level
+
+Syntax: `storm set_log_level -l [logger name]=[log level][:optional timeout] -r [logger name] topology-name`
+
+Dynamically change topology log levels
+    
+where log level is one of: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF
+and timeout is integer seconds.
+
+e.g.
+  ./bin/storm set_log_level -l ROOT=DEBUG:30 topology-name
+
+  Set the root logger's level to DEBUG for 30 seconds
+
+  ./bin/storm set_log_level -l com.myapp=WARN topology-name
+
+  Set the com.myapp logger's level to WARN for 30 seconds
+
+  ./bin/storm set_log_level -l com.myapp=WARN -l com.myOtherLogger=ERROR:123 topology-name
+
+  Set the com.myapp logger's level to WARN indifinitely, and com.myOtherLogger to ERROR for 123 seconds
+
+  ./bin/storm set_log_level -r com.myOtherLogger topology-name
+
+  Clears settings, resetting back to the original level
+
+### shell
+
+Syntax: `storm shell resourcesdir command args`
+
+Makes constructing jar and uploading to nimbus for using non JVM languages
+
+eg: `storm shell resources/ python topology.py arg1 arg2`
+
+### sql
+
+Syntax: `storm sql sql-file topology-name`
+
+Compiles the SQL statements into a Trident topology and submits it to Storm.
+
+### upload-credentials
+
+Syntax: `storm upload_credentials topology-name [credkey credvalue]*`
+
+Uploads a new set of credentials to a running topology
+
+### version
+
+Syntax: `storm version`
+
+Prints the version number of this Storm release.
+
+### help
+Syntax: `storm help [command]`
+
+Print one help message or list of available commands

Modified: storm/site/releases/1.0.1/distcache-blobstore.md
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.1/distcache-blobstore.md?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/releases/1.0.1/distcache-blobstore.md (original)
+++ storm/site/releases/1.0.1/distcache-blobstore.md Fri Jul  8 10:36:30 2016
@@ -55,7 +55,7 @@ The main stages can be depicted as follo
 Blobs in the blobstore can be created through command line using the following command.
 
 ```
-storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 ```
 
 The above command creates a blob with a key name “key1” corresponding to the file README.txt. 
@@ -324,7 +324,7 @@ that need to be cached and bind them to
 uses the "blobstore create" command of the storm executable, as follows:
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--repl-fctr NUMBER] [keyname]
+storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--replication-factor NUMBER] [keyname]
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The contents come from a FILE, if provided by -f or --file option, otherwise
@@ -346,7 +346,7 @@ where:
 * a = admin access  
 * _ = ignored  
 
-The replication factor can be set to a value greater than 1 using --repl-fctr.
+The replication factor can be set to a value greater than 1 using --replication-factor.
 
 Note: The replication right now is configurable for a hdfs blobstore but for a
 local blobstore the replication always stays at 1. For a hdfs blobstore
@@ -355,7 +355,7 @@ the default replication is set to 3.
 ###### Example:  
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In the above example, the *README.txt* file is added to the distributed cache.
@@ -475,7 +475,7 @@ ACL is in the form [uo]:[username]:[r-][
 ### Update the replication factor for a blob
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore replication --update --repl-fctr 5 key1
+storm blobstore replication --update --replication-factor 5 key1
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 ### Read the replication factor of a blob

Modified: storm/site/releases/1.0.1/images/transactional-batches.png
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.1/images/transactional-batches.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/1.0.1/images/transactional-commit-flow.png
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.1/images/transactional-commit-flow.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/1.0.1/images/transactional-design-2.png
URL: http://svn.apache.org/viewvc/storm/site/releases/1.0.1/images/transactional-design-2.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/2.0.0-SNAPSHOT/Command-line-client.md
URL: http://svn.apache.org/viewvc/storm/site/releases/2.0.0-SNAPSHOT/Command-line-client.md?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/releases/2.0.0-SNAPSHOT/Command-line-client.md (original)
+++ storm/site/releases/2.0.0-SNAPSHOT/Command-line-client.md Fri Jul  8 10:36:30 2016
@@ -20,6 +20,22 @@ These commands are:
 1. supervisor
 1. ui
 1. drpc
+1. blobstore
+1. dev-zookeeper
+1. get-errors
+1. heartbeats
+1. kill_workers
+1. list
+1. logviewer
+1. monitor
+1. node-health-check
+1. pacemaker
+1. set_log_level
+1. shell
+1. sql
+1. upload-credentials
+1. version
+1. help
 
 ### jar
 
@@ -102,3 +118,152 @@ Launches the UI daemon. The UI provides
 Syntax: `storm drpc`
 
 Launches a DRPC daemon. This command should be run under supervision with a tool like [daemontools](http://cr.yp.to/daemontools.html) or [monit](http://mmonit.com/monit/). See [Distributed RPC](Distributed-RPC.html) for more information.
+
+### blobstore
+
+Syntax: `storm blobstore cmd`
+
+list [KEY...] - lists blobs currently in the blob store
+
+cat [-f FILE] KEY - read a blob and then either write it to a file, or STDOUT (requires read access).
+
+create [-f FILE] [-a ACL ...] [--replication-factor NUMBER] KEY - create a new blob. Contents comes from a FILE or STDIN. ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list.
+
+update [-f FILE] KEY - update the contents of a blob.  Contents comes from a FILE or STDIN (requires write access).
+
+delete KEY - delete an entry from the blob store (requires write access).
+
+set-acl [-s ACL] KEY - ACL is in the form [uo]:[username]:[r-][w-][a-] can be comma separated list (requires admin access).
+
+replication --read KEY - Used to read the replication factor of the blob.
+
+replication --update --replication-factor NUMBER KEY where NUMBER > 0. It is used to update the replication factor of a blob.
+
+For example, the following would create a mytopo:data.tgz key using the data stored in data.tgz.  User alice would have full access, bob would have read/write access and everyone else would have read access.
+
+storm blobstore create mytopo:data.tgz -f data.tgz -a u:alice:rwa,u:bob:rw,o::r
+
+See [Blobstore(Distcahce)](distcache-blobstore.html) for more information.
+
+### dev-zookeeper
+
+Syntax: `storm dev-zookeeper`
+
+Launches a fresh Zookeeper server using "dev.zookeeper.path" as its local dir and "storm.zookeeper.port" as its port. This is only intended for development/testing, the Zookeeper instance launched is not configured to be used in production.
+
+### get-errors
+
+Syntax: `storm get-errors topology-name`
+
+Get the latest error from the running topology. The returned result contains the key value pairs for component-name and component-error for the components in error. The result is returned in json format.
+
+### heartbeats
+
+Syntax: `storm heartbeats [cmd]`
+
+list PATH - lists heartbeats nodes under PATH currently in the ClusterState.
+get  PATH - Get the heartbeat data at PATH
+
+### kill_workers
+
+Syntax: `storm kill_workers`
+
+Kill the workers running on this supervisor. This command should be run on a supervisor node. If the cluster is running in secure mode, then user needs to have admin rights on the node to be able to successfully kill all workers.
+
+### list
+
+Syntax: `storm list`
+
+List the running topologies and their statuses.
+
+### logviewer
+
+Syntax: `storm logviewer`
+
+Launches the log viewer daemon. It provides a web interface for viewing storm log files. This command should be run under supervision with a tool like daemontools or monit.
+
+See Setting up a Storm cluster for more information.(http://storm.apache.org/documentation/Setting-up-a-Storm-cluster)
+
+### monitor
+
+Syntax: `storm monitor topology-name [-i interval-secs] [-m component-id] [-s stream-id] [-w [emitted | transferred]]`
+
+Monitor given topology's throughput interactively.
+One can specify poll-interval, component-id, stream-id, watch-item[emitted | transferred]
+  By default,
+    poll-interval is 4 seconds;
+    all component-ids will be list;
+    stream-id is 'default';
+    watch-item is 'emitted';
+
+### node-health-check
+
+Syntax: `storm node-health-check`
+
+Run health checks on the local supervisor.
+
+### pacemaker
+
+Syntax: `storm pacemaker`
+
+Launches the Pacemaker daemon. This command should be run under
+supervision with a tool like daemontools or monit.
+
+See Setting up a Storm cluster for more information.(http://storm.apache.org/documentation/Setting-up-a-Storm-cluster)
+
+### set_log_level
+
+Syntax: `storm set_log_level -l [logger name]=[log level][:optional timeout] -r [logger name] topology-name`
+
+Dynamically change topology log levels
+    
+where log level is one of: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF
+and timeout is integer seconds.
+
+e.g.
+  ./bin/storm set_log_level -l ROOT=DEBUG:30 topology-name
+
+  Set the root logger's level to DEBUG for 30 seconds
+
+  ./bin/storm set_log_level -l com.myapp=WARN topology-name
+
+  Set the com.myapp logger's level to WARN for 30 seconds
+
+  ./bin/storm set_log_level -l com.myapp=WARN -l com.myOtherLogger=ERROR:123 topology-name
+
+  Set the com.myapp logger's level to WARN indifinitely, and com.myOtherLogger to ERROR for 123 seconds
+
+  ./bin/storm set_log_level -r com.myOtherLogger topology-name
+
+  Clears settings, resetting back to the original level
+
+### shell
+
+Syntax: `storm shell resourcesdir command args`
+
+Makes constructing jar and uploading to nimbus for using non JVM languages
+
+eg: `storm shell resources/ python topology.py arg1 arg2`
+
+### sql
+
+Syntax: `storm sql sql-file topology-name`
+
+Compiles the SQL statements into a Trident topology and submits it to Storm.
+
+### upload-credentials
+
+Syntax: `storm upload_credentials topology-name [credkey credvalue]*`
+
+Uploads a new set of credentials to a running topology
+
+### version
+
+Syntax: `storm version`
+
+Prints the version number of this Storm release.
+
+### help
+Syntax: `storm help [command]`
+
+Print one help message or list of available commands

Modified: storm/site/releases/2.0.0-SNAPSHOT/distcache-blobstore.md
URL: http://svn.apache.org/viewvc/storm/site/releases/2.0.0-SNAPSHOT/distcache-blobstore.md?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
--- storm/site/releases/2.0.0-SNAPSHOT/distcache-blobstore.md (original)
+++ storm/site/releases/2.0.0-SNAPSHOT/distcache-blobstore.md Fri Jul  8 10:36:30 2016
@@ -55,7 +55,7 @@ The main stages can be depicted as follo
 Blobs in the blobstore can be created through command line using the following command.
 
 ```
-storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 ```
 
 The above command creates a blob with a key name “key1” corresponding to the file README.txt. 
@@ -324,7 +324,7 @@ that need to be cached and bind them to
 uses the "blobstore create" command of the storm executable, as follows:
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--repl-fctr NUMBER] [keyname]
+storm blobstore create [-f|--file FILE] [-a|--acl ACL1,ACL2,...] [--replication-factor NUMBER] [keyname]
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The contents come from a FILE, if provided by -f or --file option, otherwise
@@ -346,7 +346,7 @@ where:
 * a = admin access  
 * _ = ignored  
 
-The replication factor can be set to a value greater than 1 using --repl-fctr.
+The replication factor can be set to a value greater than 1 using --replication-factor.
 
 Note: The replication right now is configurable for a hdfs blobstore but for a
 local blobstore the replication always stays at 1. For a hdfs blobstore
@@ -355,7 +355,7 @@ the default replication is set to 3.
 ###### Example:  
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore create --file README.txt --acl o::rwa --repl-fctr 4 key1
+storm blobstore create --file README.txt --acl o::rwa --replication-factor 4 key1
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In the above example, the *README.txt* file is added to the distributed cache.
@@ -475,7 +475,7 @@ ACL is in the form [uo]:[username]:[r-][
 ### Update the replication factor for a blob
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-storm blobstore replication --update --repl-fctr 5 key1
+storm blobstore replication --update --replication-factor 5 key1
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 ### Read the replication factor of a blob

Modified: storm/site/releases/2.0.0-SNAPSHOT/images/transactional-batches.png
URL: http://svn.apache.org/viewvc/storm/site/releases/2.0.0-SNAPSHOT/images/transactional-batches.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/2.0.0-SNAPSHOT/images/transactional-commit-flow.png
URL: http://svn.apache.org/viewvc/storm/site/releases/2.0.0-SNAPSHOT/images/transactional-commit-flow.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.

Modified: storm/site/releases/2.0.0-SNAPSHOT/images/transactional-design-2.png
URL: http://svn.apache.org/viewvc/storm/site/releases/2.0.0-SNAPSHOT/images/transactional-design-2.png?rev=1751878&r1=1751877&r2=1751878&view=diff
==============================================================================
Binary files - no diff available.