OpenSearch/rest-api-spec/test/indices.flush/10_basic.yaml

---
"Index synced flush rest test":
    - do:
       indices.create:
          index: testing

    - do:
       cluster.health:
          wait_for_status: yellow
    - do:
       indices.flush_synced:
          index: testing

    - is_false: _shards.failed

    - do:
       indices.stats: {level: shards}

    - is_true: indices.testing.shards.0.0.commit.user_data.sync_id
api for synced flush closes #11098 2015-05-05 18:12:40 +02:00			`---`
Move index sealing terminology to synced flush #10032 introduced the notion of sealing an index by marking it with a special read only marker, allowing for a couple of optimization to happen. The most important one was to speed up recoveries of shards where we know nothing has changed since they were online by skipping the file based sync phase. During the implementation we came up with a light notion which achieves the same recovery benefits but without the read only aspects which we dubbed synced flush. The fact that it was light weight and didn't put the index in read only mode, allowed us to do it automatically in the background which has great advantage. However we also felt the need to allow users to manually trigger this operation. The implementation at #11179 added the sync flush internal logic and the manual (rest) rest API. The name of the API was modeled after the sealing terminology which may end up being confusing. This commit changes the API name to match the internal synced flush naming, namely `{index}/_flush/synced'. On top of that it contains a couple other changes: - Remove all java client API. This feature is not supposed to be called programtically by applications but rather by admins. - Improve rest responses making structure similar to other (flush) API - Change IndexShard#getOperationsCount to exclude the internal +1 on open shard . it's confusing to get 1 while there are actually no ongoing operations - Some minor other clean ups 2015-05-23 17:18:21 +03:00			`"Index synced flush rest test":`
REST test: Fixed index-seal test Fixed bad YAML, and changed to wait for yellow instead of green, because REST tests usually run on a single node 2015-05-20 13:46:43 +02:00			`- do:`
			`indices.create:`
			`index: testing`
api for synced flush closes #11098 2015-05-05 18:12:40 +02:00
REST test: Fixed index-seal test Fixed bad YAML, and changed to wait for yellow instead of green, because REST tests usually run on a single node 2015-05-20 13:46:43 +02:00			`- do:`
			`cluster.health:`
			`wait_for_status: yellow`
			`- do:`
[test] fix name in synced flush test 2015-05-29 13:47:43 +02:00			`indices.flush_synced:`
REST test: Fixed index-seal test Fixed bad YAML, and changed to wait for yellow instead of green, because REST tests usually run on a single node 2015-05-20 13:46:43 +02:00			`index: testing`
Move index sealing terminology to synced flush #10032 introduced the notion of sealing an index by marking it with a special read only marker, allowing for a couple of optimization to happen. The most important one was to speed up recoveries of shards where we know nothing has changed since they were online by skipping the file based sync phase. During the implementation we came up with a light notion which achieves the same recovery benefits but without the read only aspects which we dubbed synced flush. The fact that it was light weight and didn't put the index in read only mode, allowed us to do it automatically in the background which has great advantage. However we also felt the need to allow users to manually trigger this operation. The implementation at #11179 added the sync flush internal logic and the manual (rest) rest API. The name of the API was modeled after the sealing terminology which may end up being confusing. This commit changes the API name to match the internal synced flush naming, namely `{index}/_flush/synced'. On top of that it contains a couple other changes: - Remove all java client API. This feature is not supposed to be called programtically by applications but rather by admins. - Improve rest responses making structure similar to other (flush) API - Change IndexShard#getOperationsCount to exclude the internal +1 on open shard . it's confusing to get 1 while there are actually no ongoing operations - Some minor other clean ups 2015-05-23 17:18:21 +03:00
			`- is_false: _shards.failed`

REST test: Fixed index-seal test Fixed bad YAML, and changed to wait for yellow instead of green, because REST tests usually run on a single node 2015-05-20 13:46:43 +02:00			`- do:`
			`indices.stats: {level: shards}`
api for synced flush closes #11098 2015-05-05 18:12:40 +02:00
REST test: Fixed index-seal test Fixed bad YAML, and changed to wait for yellow instead of green, because REST tests usually run on a single node 2015-05-20 13:46:43 +02:00			`- is_true: indices.testing.shards.0.0.commit.user_data.sync_id`