Author: buildbot
Date: Thu Nov 6 16:42:07 2014
New Revision: 928158
Log:
Staging update by buildbot for slider
Modified:
websites/staging/slider/trunk/content/ (props changed)
websites/staging/slider/trunk/content/docs/configuration/core.html
Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Nov 6 16:42:07 2014
@@ -1 +1 @@
-1636951
+1637155
Modified: websites/staging/slider/trunk/content/docs/configuration/core.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/configuration/core.html
(original)
+++ websites/staging/slider/trunk/content/docs/configuration/core.html Thu Nov
6 16:42:07 2014
@@ -532,6 +532,22 @@ does not prevent any component from over
to create local configurations incompatible with the global state. (i.e.,
there is no way to declare an attribute as final). It is the responsibility
of the author of the configuration file (and their tools) to detect such
issues.</p>
+<h3 id="key-application-configuration-items">Key Application Configuration
Items</h3>
+<p>The following sections provides details about certain application
configuration properties that can be utilized to tailor the deployment of a
given application:</p>
+<h4 id="controlling-assigned-port-ranges">Controlling assigned port ranges</h4>
+<p>For certain deployments, the ports available for communication with clients
(Web UI ports, RPC ports, etc) are restricted to a specific set (e.g when
leveraging a firewall). In those situations you can designate the set of
allowed ports with the "site.global.slider.allowed.ports" setting. This
settings takes a comma-delimited set of port numbers and ranges, e.g.:</p>
+<div class="codehilite"><pre>"<span class="n">site</span><span
class="p">.</span><span class="k">global</span><span class="p">.</span><span
class="n">slider</span><span class="p">.</span><span
class="n">allowed</span><span class="p">.</span><span
class="n">ports</span>"<span class="p">:</span> "48000<span
class="p">,</span> 49000<span class="p">,</span> 50001<span
class="o">-</span>50010"
+</pre></div>
+
+
+<p>The AM exposed ports (Web UI, RPC), as well as the ports allocated to
launched application containers, will be limited to the ranges specified by the
property value.</p>
+<h4 id="delaying-container-launch">Delaying container launch</h4>
+<p>In situations where container restarts may need to be delayed to allow for
platform resources to be released (e.g. a port assigned to a container that is
stopped may be slow to release), a delay can be designated by setting the
"container.launch.delay.sec" property in the component's configuration
section:</p>
+<div class="codehilite"><pre>"<span class="n">worker</span>"<span
class="p">:</span> <span class="p">{</span>
+ "<span class="n">jvm</span><span class="p">.</span><span
class="n">heapsite</span>"<span class="p">:</span> "512<span
class="n">M</span>"<span class="p">,</span>
+ "<span class="n">container</span><span class="p">.</span><span
class="n">launch</span><span class="p">.</span><span
class="n">delay</span><span class="p">.</span><span
class="nb">sec</span>"<span class="p">:</span> "30"
+<span class="p">}</span>
+</pre></div>
</div>
<div id="footer">
