Return-Path:
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
.
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
instruct the scheduler to completely abandon the job update and leave the job in the current (possibly partially-updated) state. -start
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.Coordinated job updates (beta)
+Coordinated job updates
-Some Aurora services may benefit from having more control over the -asynchronous scheduler updater 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 @@ -284,6 +251,34 @@ 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 +itsjob_key
argument. Be sure you don’t issuejob cancel-update
when +another user is working with the specified Job.The
+<configuration file>
argument forjob 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 forjob update
.Renaming a Job
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
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 pulse_interval_secs
Integer -Indicates a coordinated update. 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) +Indicates a coordinated update. 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) True
. For exampleModified: 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 @@ start_job_update
- self
,config
,instances=None
+ beta-update start
update start
\ 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] http://aurora.incubator.apache.org/blog/aurora-0-6-0-incubating-released/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/blog/aurora-0-7-0-incubating-released/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/blog/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/community/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/developers/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/docs/gettingstarted/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/docs/howtocontribute/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/client-cluster-configuration/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/client-commands/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/committers/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/configuration-reference/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/configuration-tutorial/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/contributing/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/cron-jobs/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/deploying-aurora-scheduler/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/developing-aurora-client/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/developing-aurora-scheduler/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/hooks/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/monitoring/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/resource-isolation/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/scheduler-storage/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/sla/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/storage-config/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/storage/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/test-resource-generation/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/thrift-deprecation/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/tutorial/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/user-guide/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/vagrant/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/documentation/latest/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/downloads/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 http://aurora.incubator.apache.org/ -2015-03-12T00:00:00-07:00 +2015-03-17T00:00:00-07:00 - 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 ` ` argument for `job cancel-update` is optional. Use -it only if it contains hook definitions and activations that affect the -`cancel_update` command. The ` ` 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 - aurora beta-update status - aurora beta-update pause - aurora beta-update resume - aurora beta-update abort - aurora beta-update list + aurora update start + aurora update status + aurora update pause + aurora update resume + aurora update abort + aurora update list 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] + 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 ` ` argument for `job cancel-update` is optional. Use +it only if it contains hook definitions and activations that affect the +`cancel_update` command. The ` ` 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: