svn commit: r1680321 - /incubator/slider/site/trunk/content/docs/slider_specs/application_pkg_upgrade.md

[go...@apache.org]

Author: gourksaha
Date: Tue May 19 15:41:14 2015
New Revision: 1680321

URL: http://svn.apache.org/r1680321
Log:
CMS commit to slider by gourksaha

Modified:
    incubator/slider/site/trunk/content/docs/slider_specs/application_pkg_upgrade.md

Modified: incubator/slider/site/trunk/content/docs/slider_specs/application_pkg_upgrade.md
URL: http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/docs/slider_specs/application_pkg_upgrade.md?rev=1680321&r1=1680320&r2=1680321&view=diff
==============================================================================
--- incubator/slider/site/trunk/content/docs/slider_specs/application_pkg_upgrade.md (original)
+++ incubator/slider/site/trunk/content/docs/slider_specs/application_pkg_upgrade.md Tue May 19 15:41:14 2015
@@ -38,19 +38,19 @@ Automated application package upgrade wi
 ## Phases of Upgrade/Downgrade
 
 #### YARN core (libraries and configurations) upgrade/downgrade
-> Running Slider apps will continue to run, with no downtime
+    Running Slider apps will continue to run, with no downtime
 
 #### Slider client upgrade/downgrade
-> Does not affect running Slider apps at all. New version of client can co-exist with older versions of client.
+    Does not affect running Slider apps at all. New version of client can co-exist with older versions of client.
 
 #### Slider Application Master upgrade/downgrade of running applications
-> Applications started prior to the start of YARN core upgrade/downgrade, will continue to run with the 
+    Applications started prior to the start of YARN core upgrade/downgrade, will continue to run with the 
 older versions of Slider core and Hadoop libraries. There is no support for rolling upgrade of Slider AM.
 To upgrade running Slider AMs, the application needs to be stopped and restarted with the new version
 of the client.
 
 #### Applications deployed by Slider (binaries and configurations) upgrade/downgrade
-> This is the what this document is primarily about.
+    This is the what this document is primarily about.
 
 ## Upgrade Slider Application Packages
 
@@ -171,7 +171,7 @@ Downgrade is done when the following com
 ## Pre and post upgrade hooks
 
 ### Pre-upgrade hook (optional)
-> The pre-upgrade steps, if provided, will allow applications to execute simple housekeeping tasks 
+    The pre-upgrade steps, if provided, will allow applications to execute simple housekeeping tasks 
 before Slider actually calls stop operation in an upgrade scenario (specifically if they need to 
 be performed in every single container and 1000s of them are running). An example could be to 
 send a message to a queue that the current instance of memcached is going down so that the load 
@@ -182,13 +182,13 @@ pre-upgrade hook is not a good candidate
 to be exposed, like timeout, which can be used to wait at most n seconds (say) after which Slider 
 will call the application stop hook even if the pre-upgrade operation is not completed.
 
-> Use `app-packages/hbase/package/scripts/hbase_master.py` as a sample for defining the 
+    Use `app-packages/hbase/package/scripts/hbase_master.py` as a sample for defining the 
 pre-upgrade hook. Note, the pre-upgrade hook will be triggered only if the currently running
 application has been created using Slider verion `0.80.0-incubating` or later and the scripts
 in the package has the pre-upgrade hook defined.
 
 ### Post-upgrade hook (optional) - `not yet supported`
-> This allows applications to perform simple housekeeping tasks prior to calling start on the new 
+    This allows applications to perform simple housekeeping tasks prior to calling start on the new 
 version of the application component. This is helpful only if such tasks are required to be 
 performed in every single container and 1000s of them are running. This hook will be triggered only in the 
 upgrade scenario. It will not be called on new containers created using flex up, in non-upgrade