From 3d7f0399c5d06b85067602033514982b64b8be3a Mon Sep 17 00:00:00 2001 From: Simon Willnauer Date: Wed, 21 Sep 2016 14:47:30 +0200 Subject: [PATCH] Add migration guide note for `_flush?wait_if_ongoing` (#20603) 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/index-apis.asciidoc | 7 +++++++ 1 file changed, 7 insertions(+) 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