svn commit: r918009 - in /websites/staging/slider/trunk/content: ./ docs/slider_specs/application_instance_configuration.html

[bu...@apache.org]

Author: buildbot
Date: Thu Jul 31 03:38:52 2014
New Revision: 918009

Log:
Staging update by buildbot for slider

Modified:
    websites/staging/slider/trunk/content/   (props changed)
    websites/staging/slider/trunk/content/docs/slider_specs/application_instance_configuration.html

Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jul 31 03:38:52 2014
@@ -1 +1 @@
-1612872
+1614805

Modified: websites/staging/slider/trunk/content/docs/slider_specs/application_instance_configuration.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/slider_specs/application_instance_configuration.html (original)
+++ websites/staging/slider/trunk/content/docs/slider_specs/application_instance_configuration.html Thu Jul 31 03:38:52 2014
@@ -243,7 +243,7 @@ Latest release: <strong>0.40-incubating<
 <p><strong>dynamically allocated ports</strong></p>
 <p>Apps can ask port to be dynamically assigned by Slider or they can leave it as "0". If there is a need for advertising any listening endpoint then the ports can be marked such.</p>
 <p>For example, HBase master info port needs to be advertised so that jmx endpoint can be accessed. This is indicated by using a special value, of the form, ${COMPONENT_NAME.ALLOCATED_PORT}. E.g. "site.hbase-site.hbase.master.info.port": "${HBASE_MASTER.ALLOCATED_PORT}"</p>
-<p><a href="application_definition.md">Application Definition</a> describes how to advertise arbitrary set of properties that are dynamically finalized when application is activated.</p>
+<p><a href="application_definition.html">Application Definition</a> describes how to advertise arbitrary set of properties that are dynamically finalized when application is activated.</p>
 <p><strong>configuraing an app for ganglia metrics</strong></p>
 <p>There is no set guideline for doing so. How an application emits metrics and how the metrics are emitted to the right place is completely defined by the application. In the following example, we hso how HBase app is configured to emit metrics to a ganglia server.</p>
 <p>Ganglia server lifecycle is not controlled by the app instance. So the app instance only needs to know where to emit the metrics. This is achieved by three global variables</p>