From 413f10e4b421b532ddd9a729fcb9de225588e11c Mon Sep 17 00:00:00 2001 From: Simon Willnauer Date: Wed, 21 Sep 2016 14:32:07 +0200 Subject: [PATCH 1/2] Add migration guide note for `_flush?wait_if_ongoing` This change adds a note to the migration guide for the change of the default value from `false` to `true`. Relates to #20597 --- docs/reference/migration/migrate_5_0/rest.asciidoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/reference/migration/migrate_5_0/rest.asciidoc b/docs/reference/migration/migrate_5_0/rest.asciidoc index afba8819ed348..b55274e39bf45 100644 --- a/docs/reference/migration/migrate_5_0/rest.asciidoc +++ b/docs/reference/migration/migrate_5_0/rest.asciidoc @@ -98,3 +98,11 @@ The `wait_for_relocating_shards` parameter that used to take a number is now sim flag `wait_for_no_relocating_shards`, which if set to true, means the request will wait (up until the configured timeout) for the cluster to have no shard relocations before returning. Defaults to false, which means the operation will not wait. + +==== `wait_if_ongoing` now defaults to `true` in `/_flush` + +The `wait_if_ongoing` flag default has changed to `true` causing `_flush` calls to wait and block +if another flush operation is currently running on the same shard. In turn, if `wait_if_ongoing` is set to +`false` and another flush operation is already running the flush is skipped and the shards flush call will return +immediately without any error. In previous versions `flush_not_allowed` exceptions where reported for each skipped shard. + From f77e5d3d98c01db4593056923cd5e71813a99450 Mon Sep 17 00:00:00 2001 From: Simon Willnauer Date: Wed, 21 Sep 2016 14:46:57 +0200 Subject: [PATCH 2/2] Move flush change to index-apis.asciidoc --- docs/reference/migration/migrate_5_0/index-apis.asciidoc | 7 +++++++ docs/reference/migration/migrate_5_0/rest.asciidoc | 8 -------- 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/docs/reference/migration/migrate_5_0/index-apis.asciidoc b/docs/reference/migration/migrate_5_0/index-apis.asciidoc index c8f939c259d76..91c0a4ca27ca0 100644 --- a/docs/reference/migration/migrate_5_0/index-apis.asciidoc +++ b/docs/reference/migration/migrate_5_0/index-apis.asciidoc @@ -69,3 +69,10 @@ prefer there to be only one (obvious) way to do things like this. As of 5.0 indexing a document with `op_type=create` without specifying an ID is not supported anymore. + +==== Flush API + +The `wait_if_ongoing` flag default has changed to `true` causing `_flush` calls to wait and block +if another flush operation is currently running on the same shard. In turn, if `wait_if_ongoing` is set to +`false` and another flush operation is already running the flush is skipped and the shards flush call will return +immediately without any error. In previous versions `flush_not_allowed` exceptions where reported for each skipped shard. \ No newline at end of file diff --git a/docs/reference/migration/migrate_5_0/rest.asciidoc b/docs/reference/migration/migrate_5_0/rest.asciidoc index b55274e39bf45..afba8819ed348 100644 --- a/docs/reference/migration/migrate_5_0/rest.asciidoc +++ b/docs/reference/migration/migrate_5_0/rest.asciidoc @@ -98,11 +98,3 @@ The `wait_for_relocating_shards` parameter that used to take a number is now sim flag `wait_for_no_relocating_shards`, which if set to true, means the request will wait (up until the configured timeout) for the cluster to have no shard relocations before returning. Defaults to false, which means the operation will not wait. - -==== `wait_if_ongoing` now defaults to `true` in `/_flush` - -The `wait_if_ongoing` flag default has changed to `true` causing `_flush` calls to wait and block -if another flush operation is currently running on the same shard. In turn, if `wait_if_ongoing` is set to -`false` and another flush operation is already running the flush is skipped and the shards flush call will return -immediately without any error. In previous versions `flush_not_allowed` exceptions where reported for each skipped shard. -