aurora-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dles...@apache.org
Subject svn commit: r1667459 - in /incubator/aurora/site: publish/ publish/documentation/latest/client-commands/ publish/documentation/latest/configuration-reference/ publish/documentation/latest/hooks/ source/documentation/latest/
Date Wed, 18 Mar 2015 06:57:08 GMT
Author: dlester
Date: Wed Mar 18 06:57:08 2015
New Revision: 1667459

URL: http://svn.apache.org/r1667459
Log:
Update Apache Aurora documentation.

Modified:
    incubator/aurora/site/publish/documentation/latest/client-commands/index.html
    incubator/aurora/site/publish/documentation/latest/configuration-reference/index.html
    incubator/aurora/site/publish/documentation/latest/hooks/index.html
    incubator/aurora/site/publish/sitemap.xml
    incubator/aurora/site/source/documentation/latest/client-commands.md
    incubator/aurora/site/source/documentation/latest/configuration-reference.md
    incubator/aurora/site/source/documentation/latest/hooks.md

Modified: incubator/aurora/site/publish/documentation/latest/client-commands/index.html
URL: http://svn.apache.org/viewvc/incubator/aurora/site/publish/documentation/latest/client-commands/index.html?rev=1667459&r1=1667458&r2=1667459&view=diff
==============================================================================
--- incubator/aurora/site/publish/documentation/latest/client-commands/index.html (original)
+++ incubator/aurora/site/publish/documentation/latest/client-commands/index.html Wed Mar
18 06:57:08 2015
@@ -55,11 +55,8 @@
 <li><a href="#updating-a-job">Updating a Job</a>
 
 <ul>
-<li><a href="#user-content-asynchronous-job-updates-beta">Asynchronous job updates
(beta)</a>
-
-<ul>
-<li><a href="#user-content-coordinated-job-updates-beta">Coordinated job updates
(beta)</a></li>
-</ul></li>
+<li><a href="#user-content-coordinated-job-updates">Coordinated job updates</a></li>
+<li><a href="#user-content-client-orchestrated-updates-deprecated">Client-orchestrated
updates (deprecated)</a></li>
 </ul></li>
 <li><a href="#renaming-a-job">Renaming a Job</a></li>
 <li><a href="#restarting-jobs">Restarting Jobs</a></li>
@@ -210,43 +207,14 @@ if it contains hook definitions and acti
 kill command.</p>
 
 <h3 id="updating-a-job">Updating a Job</h3>
-<pre class="highlight text">aurora job update CLUSTER/ROLE/ENV/NAME[/INSTANCES] &lt;configuration
file&gt;
-aurora job cancel-update CLUSTER/ROLE/ENV/NAME
-</pre>
-<p>Given a running job, does a rolling update to reflect a new
-configuration version. Only updates Tasks in the Job with a changed
-configuration. You can further restrict the operated on Tasks by specifying
-specific instances that should be updated.</p>
-
-<p>You may want to run <code>aurora job diff</code> beforehand to validate
which Tasks
-have different configurations.</p>
-
-<p>Updating jobs are locked to be sure the update finishes without
-disruption. If the update abnormally terminates, the lock may stay
-around and cause failure of subsequent update attempts.
- <code>aurora job cancel-update</code>unlocks the Job specified by
-its <code>job_key</code> argument. Be sure you don&rsquo;t issue <code>job
cancel-update</code> when
-another user is working with the specified Job.</p>
-
-<p>The <code>&lt;configuration file&gt;</code> argument for <code>job
cancel-update</code> is optional. Use
-it only if it contains hook definitions and activations that affect the
-<code>cancel_update</code> command. The <code>&lt;configuration file&gt;</code>
argument for
-<code>update</code> is required, but in addition to a new configuration it can
be
-used to define and activate hooks for <code>job update</code>.</p>
-
-<h4 id="asynchronous-job-updates-(beta)">Asynchronous job updates (beta)</h4>
-
-<p>As of 0.6.0, Aurora will control and dispatch updates (and rollbacks) within the
-scheduler. Performing updates this way also allows the scheduler to display
-update progress and job update history in the browser.</p>
 
 <p>There are several sub-commands to manage job updates:</p>
-<pre class="highlight text">aurora beta-update start &lt;job key&gt; &lt;configuration
file&gt;
-aurora beta-update status &lt;job key&gt;
-aurora beta-update pause &lt;job key&gt;
-aurora beta-update resume &lt;job key&gt;
-aurora beta-update abort &lt;job key&gt;
-aurora beta-update list &lt;cluster&gt;
+<pre class="highlight text">aurora update start &lt;job key&gt; &lt;configuration
file&gt;
+aurora update status &lt;job key&gt;
+aurora update pause &lt;job key&gt;
+aurora update resume &lt;job key&gt;
+aurora update abort &lt;job key&gt;
+aurora update list &lt;cluster&gt;
 </pre>
 <p>When you <code>start</code> a job update, the command will return once
it has sent the
 instructions to the scheduler.  At that point, you may view detailed
@@ -263,10 +231,9 @@ proceed.</p>
 instruct the scheduler to completely abandon the job update and leave the job
 in the current (possibly partially-updated) state.</p>
 
-<h5 id="coordinated-job-updates-(beta)">Coordinated job updates (beta)</h5>
+<h4 id="coordinated-job-updates">Coordinated job updates</h4>
 
-<p>Some Aurora services may benefit from having more control over the
-<a href="#user-content-asynchronous-job-updates-beta">asynchronous scheduler updater</a>
by explicitly
+<p>Some Aurora services may benefit from having more control over updates by explicitly
 acknowledging (&ldquo;heartbeating&rdquo;) job update progress. This may be helpful
for mission-critical
 service updates where explicit job health monitoring is vital during the entire job update
 lifecycle. Such job updates would rely on an external service (or a custom client) periodically
@@ -284,6 +251,34 @@ progress until the first pulse arrives.
 <code>ROLL_BACK_PAUSED</code>) is still considered active and upon resuming will
immediately make progress
 provided the pulse interval has not expired.</p>
 
+<h4 id="client-orchestrated-updates-(deprecated)">Client-orchestrated updates (deprecated)</h4>
+
+<p><em>Note: This feature is deprecated and will be removed in 0.9.0.
+Please use aurora update instead.</em></p>
+<pre class="highlight text">aurora job update CLUSTER/ROLE/ENV/NAME[/INSTANCES] &lt;configuration
file&gt;
+aurora job cancel-update CLUSTER/ROLE/ENV/NAME
+</pre>
+<p>Given a running job, does a rolling update to reflect a new
+configuration version. Only updates Tasks in the Job with a changed
+configuration. You can further restrict the operated on Tasks by specifying
+specific instances that should be updated.</p>
+
+<p>You may want to run <code>aurora job diff</code> beforehand to validate
which Tasks
+have different configurations.</p>
+
+<p>Updating jobs are locked to be sure the update finishes without
+disruption. If the update abnormally terminates, the lock may stay
+around and cause failure of subsequent update attempts.
+ <code>aurora job cancel-update</code>unlocks the Job specified by
+its <code>job_key</code> argument. Be sure you don&rsquo;t issue <code>job
cancel-update</code> when
+another user is working with the specified Job.</p>
+
+<p>The <code>&lt;configuration file&gt;</code> argument for <code>job
cancel-update</code> is optional. Use
+it only if it contains hook definitions and activations that affect the
+<code>cancel_update</code> command. The <code>&lt;configuration file&gt;</code>
argument for
+<code>update</code> is required, but in addition to a new configuration it can
be
+used to define and activate hooks for <code>job update</code>.</p>
+
 <h3 id="renaming-a-job">Renaming a Job</h3>
 
 <p>Renaming is a tricky operation as downstream clients must be informed of

Modified: incubator/aurora/site/publish/documentation/latest/configuration-reference/index.html
URL: http://svn.apache.org/viewvc/incubator/aurora/site/publish/documentation/latest/configuration-reference/index.html?rev=1667459&r1=1667458&r2=1667459&view=diff
==============================================================================
--- incubator/aurora/site/publish/documentation/latest/configuration-reference/index.html
(original)
+++ incubator/aurora/site/publish/documentation/latest/configuration-reference/index.html
Wed Mar 18 06:57:08 2015
@@ -612,7 +612,7 @@ either due to human error or machine fai
 <tr>
 <td><code>pulse_interval_secs</code></td>
 <td style="text-align: center">Integer</td>
-<td>Indicates a <a href="client-commands.md#user-content-coordinated-job-updates-beta">coordinated
update</a>. If no pulses are received within the provided interval the update will be
blocked. Beta-updater only. Will fail on submission when used with client updater. (Default:
None)</td>
+<td>Indicates a <a href="client-commands.md#user-content-coordinated-job-updates">coordinated
update</a>. If no pulses are received within the provided interval the update will be
blocked. Beta-updater only. Will fail on submission when used with client updater. (Default:
None)</td>
 </tr>
 </tbody></table>
 

Modified: incubator/aurora/site/publish/documentation/latest/hooks/index.html
URL: http://svn.apache.org/viewvc/incubator/aurora/site/publish/documentation/latest/hooks/index.html?rev=1667459&r1=1667458&r2=1667459&view=diff
==============================================================================
--- incubator/aurora/site/publish/documentation/latest/hooks/index.html (original)
+++ incubator/aurora/site/publish/documentation/latest/hooks/index.html Wed Mar 18 06:57:08
2015
@@ -171,7 +171,7 @@ returning <code>True</code>. For example
 <tr>
 <td><code>start_job_update</code></td>
 <td><code>self</code>, <code>config</code>, <code>instances=None</code></td>
-<td><code>beta-update start</code></td>
+<td><code>update start</code></td>
 </tr>
 </tbody></table>
 

Modified: incubator/aurora/site/publish/sitemap.xml
URL: http://svn.apache.org/viewvc/incubator/aurora/site/publish/sitemap.xml?rev=1667459&r1=1667458&r2=1667459&view=diff
==============================================================================
--- incubator/aurora/site/publish/sitemap.xml (original)
+++ incubator/aurora/site/publish/sitemap.xml Wed Mar 18 06:57:08 2015
@@ -2,130 +2,130 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>http://aurora.incubator.apache.org/blog/aurora-0-6-0-incubating-released/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/blog/aurora-0-7-0-incubating-released/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/blog/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/community/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/developers/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/docs/gettingstarted/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/docs/howtocontribute/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/client-cluster-configuration/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/client-commands/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/committers/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/configuration-reference/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/configuration-tutorial/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/contributing/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/cron-jobs/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/deploying-aurora-scheduler/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/developing-aurora-client/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/developing-aurora-scheduler/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/hooks/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/monitoring/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/resource-isolation/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/scheduler-storage/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/sla/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/storage-config/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/storage/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/test-resource-generation/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/thrift-deprecation/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/tutorial/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/user-guide/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/vagrant/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/documentation/latest/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/downloads/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.incubator.apache.org/</loc>
-    <lastmod>2015-03-12T00:00:00-07:00</lastmod>
+    <lastmod>2015-03-17T00:00:00-07:00</lastmod>
   </url>
 </urlset>
\ No newline at end of file

Modified: incubator/aurora/site/source/documentation/latest/client-commands.md
URL: http://svn.apache.org/viewvc/incubator/aurora/site/source/documentation/latest/client-commands.md?rev=1667459&r1=1667458&r2=1667459&view=diff
==============================================================================
--- incubator/aurora/site/source/documentation/latest/client-commands.md (original)
+++ incubator/aurora/site/source/documentation/latest/client-commands.md Wed Mar 18 06:57:08
2015
@@ -10,8 +10,8 @@ Aurora Client Commands
     - [Running a Command On a Running Job](#running-a-command-on-a-running-job)
     - [Killing a Job](#killing-a-job)
     - [Updating a Job](#updating-a-job)
-        - [Asynchronous job updates (beta)](#user-content-asynchronous-job-updates-beta)
-            - [Coordinated job updates (beta)](#user-content-coordinated-job-updates-beta)
+        - [Coordinated job updates](#user-content-coordinated-job-updates)
+        - [Client-orchestrated updates (deprecated)](#user-content-client-orchestrated-updates-deprecated)
     - [Renaming a Job](#renaming-a-job)
     - [Restarting Jobs](#restarting-jobs)
 - [Cron Jobs](#cron-jobs)
@@ -169,44 +169,14 @@ kill command.
 
 ### Updating a Job
 
-    aurora job update CLUSTER/ROLE/ENV/NAME[/INSTANCES] <configuration file>
-    aurora job cancel-update CLUSTER/ROLE/ENV/NAME
-
-Given a running job, does a rolling update to reflect a new
-configuration version. Only updates Tasks in the Job with a changed
-configuration. You can further restrict the operated on Tasks by specifying
-specific instances that should be updated.
-
-You may want to run `aurora job diff` beforehand to validate which Tasks
-have different configurations.
-
-Updating jobs are locked to be sure the update finishes without
-disruption. If the update abnormally terminates, the lock may stay
-around and cause failure of subsequent update attempts.
- `aurora job cancel-update `unlocks the Job specified by
-its `job_key` argument. Be sure you don't issue `job cancel-update` when
-another user is working with the specified Job.
-
-The `<configuration file>` argument for `job cancel-update` is optional. Use
-it only if it contains hook definitions and activations that affect the
-`cancel_update` command. The `<configuration file>` argument for
-`update` is required, but in addition to a new configuration it can be
-used to define and activate hooks for `job update`.
-
-#### Asynchronous job updates (beta)
-
-As of 0.6.0, Aurora will control and dispatch updates (and rollbacks) within the
-scheduler. Performing updates this way also allows the scheduler to display
-update progress and job update history in the browser.
-
 There are several sub-commands to manage job updates:
 
-    aurora beta-update start <job key> <configuration file>
-    aurora beta-update status <job key>
-    aurora beta-update pause <job key>
-    aurora beta-update resume <job key>
-    aurora beta-update abort <job key>
-    aurora beta-update list <cluster>
+    aurora update start <job key> <configuration file>
+    aurora update status <job key>
+    aurora update pause <job key>
+    aurora update resume <job key>
+    aurora update abort <job key>
+    aurora update list <cluster>
 
 When you `start` a job update, the command will return once it has sent the
 instructions to the scheduler.  At that point, you may view detailed
@@ -223,10 +193,9 @@ You may `abort` a job update regardless
 instruct the scheduler to completely abandon the job update and leave the job
 in the current (possibly partially-updated) state.
 
-##### Coordinated job updates (beta)
+#### Coordinated job updates
 
-Some Aurora services may benefit from having more control over the
-[asynchronous scheduler updater](#user-content-asynchronous-job-updates-beta) by explicitly
+Some Aurora services may benefit from having more control over updates by explicitly
 acknowledging ("heartbeating") job update progress. This may be helpful for mission-critical
 service updates where explicit job health monitoring is vital during the entire job update
 lifecycle. Such job updates would rely on an external service (or a custom client) periodically
@@ -244,6 +213,35 @@ progress until the first pulse arrives.
 `ROLL_BACK_PAUSED`) is still considered active and upon resuming will immediately make progress
 provided the pulse interval has not expired.
 
+#### Client-orchestrated updates (deprecated)
+
+*Note: This feature is deprecated and will be removed in 0.9.0.
+Please use aurora update instead.*
+
+    aurora job update CLUSTER/ROLE/ENV/NAME[/INSTANCES] <configuration file>
+    aurora job cancel-update CLUSTER/ROLE/ENV/NAME
+
+Given a running job, does a rolling update to reflect a new
+configuration version. Only updates Tasks in the Job with a changed
+configuration. You can further restrict the operated on Tasks by specifying
+specific instances that should be updated.
+
+You may want to run `aurora job diff` beforehand to validate which Tasks
+have different configurations.
+
+Updating jobs are locked to be sure the update finishes without
+disruption. If the update abnormally terminates, the lock may stay
+around and cause failure of subsequent update attempts.
+ `aurora job cancel-update `unlocks the Job specified by
+its `job_key` argument. Be sure you don't issue `job cancel-update` when
+another user is working with the specified Job.
+
+The `<configuration file>` argument for `job cancel-update` is optional. Use
+it only if it contains hook definitions and activations that affect the
+`cancel_update` command. The `<configuration file>` argument for
+`update` is required, but in addition to a new configuration it can be
+used to define and activate hooks for `job update`.
+
 ### Renaming a Job
 
 Renaming is a tricky operation as downstream clients must be informed of

Modified: incubator/aurora/site/source/documentation/latest/configuration-reference.md
URL: http://svn.apache.org/viewvc/incubator/aurora/site/source/documentation/latest/configuration-reference.md?rev=1667459&r1=1667458&r2=1667459&view=diff
==============================================================================
--- incubator/aurora/site/source/documentation/latest/configuration-reference.md (original)
+++ incubator/aurora/site/source/documentation/latest/configuration-reference.md Wed Mar 18
06:57:08 2015
@@ -349,7 +349,7 @@ Parameters for controlling the rate and
 | ```max_total_failures```     | Integer  | Maximum number of shard failures to be tolerated
in total during an update. Cannot be greater than or equal to the total number of tasks in
a job. (Default: 0)
 | ```rollback_on_failure```    | boolean  | When False, prevents auto rollback of a failed
update (Default: True)
 | ```wait_for_batch_completion```| boolean | When True, all threads from a given batch will
be blocked from picking up new instances until the entire batch is updated. This essentially
simulates the legacy sequential updater algorithm. (Default: False)
-| ```pulse_interval_secs```    | Integer  |  Indicates a [coordinated update](client-commands.md#user-content-coordinated-job-updates-beta).
If no pulses are received within the provided interval the update will be blocked. Beta-updater
only. Will fail on submission when used with client updater. (Default: None)
+| ```pulse_interval_secs```    | Integer  |  Indicates a [coordinated update](client-commands.md#user-content-coordinated-job-updates).
If no pulses are received within the provided interval the update will be blocked. Beta-updater
only. Will fail on submission when used with client updater. (Default: None)
 
 ### HealthCheckConfig Objects
 

Modified: incubator/aurora/site/source/documentation/latest/hooks.md
URL: http://svn.apache.org/viewvc/incubator/aurora/site/source/documentation/latest/hooks.md?rev=1667459&r1=1667458&r2=1667459&view=diff
==============================================================================
--- incubator/aurora/site/source/documentation/latest/hooks.md (original)
+++ incubator/aurora/site/source/documentation/latest/hooks.md Wed Mar 18 06:57:08 2015
@@ -92,7 +92,7 @@ You can associate `pre_`, `post_`, and `
   ```update_job``` | ```self```, ```config```, ```health_check_interval_seconds=3```, ```shards=None```
| ```job update```
   ```kill_job``` | ```self```, ```job_key```, ```shards=None``` |  ```job kill```
   ```start_cronjob``` | ```self```, ```job_key``` | ```cron start```
-  ```start_job_update``` | ```self```, ```config```, ```instances=None``` | ```beta-update
start```
+  ```start_job_update``` | ```self```, ```config```, ```instances=None``` | ```update start```
 
 Some specific examples:
 



Mime
View raw message