From 0b1298455236ddb83d003cf82ad5cc16f3345308 Mon Sep 17 00:00:00 2001 From: Michael Schurter Date: Wed, 29 Nov 2017 17:25:24 -0800 Subject: [PATCH] Add atomic migrations to changelog and docs --- CHANGELOG.md | 1 + website/source/docs/job-specification/ephemeral_disk.html.md | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7c06034d4..ce8c49d28 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -17,6 +17,7 @@ IMPROVEMENTS: * api: Environment variables are ignored during service name validation [GH-3532] * cli: Allocation create and modify times are displayed in a human readable relative format like `6 h ago` [GH-3449] + * client: Sticky volume migrations are now atomic. [GH-3563] * client: Added metrics to track state transitions of allocations [GH-3061] * client: When `network_interface` is unspecified use interface attached to default route [GH-3546] diff --git a/website/source/docs/job-specification/ephemeral_disk.html.md b/website/source/docs/job-specification/ephemeral_disk.html.md index 6f630c3b9..c3e8fe207 100644 --- a/website/source/docs/job-specification/ephemeral_disk.html.md +++ b/website/source/docs/job-specification/ephemeral_disk.html.md @@ -41,7 +41,9 @@ job "docs" { - `migrate` `(bool: false)` - When `sticky` is true, this specifies that the Nomad client should make a best-effort attempt to migrate the data from a remote machine if placement cannot be made on the original node. During data - migration, the task will block starting until the data migration has completed. + migration, the task will block starting until the data migration has + completed. Migration is atomic and any partially migrated data will be + removed if an error is encountered. - `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The current Nomad ephemeral storage implementation does not enforce this limit;