tree 50c0fb677f9cec03f7d92bafa40a69860031fbca
parent 3a86708875cbc3840ebb9b70d6eb08e3ba82db1e
author David Pursehouse <dpursehouse@collab.net> 1543840024 +0900
committer David Pursehouse <dpursehouse@collab.net> 1543879957 +0900

ElasticV7QueryChangesTest: Close indices after test

For each test method, new indices are created with a unique name based
on the test method name. This results in 3 indices (i.e. one each for
accounts, changes and groups) for each test method that is run, which
in turn results in the number of allocated shards increasing.

In Elasticsearch 7.0 a shard limit is introduced [1] which so far only
causes a warning. However in a future version (not clear if this means
the final 7.0 release or a subsequent one) the limit will be enforced
and result in an error.

After each test, close the indices that were created. This results in
the shards being deallocated, and prevents exceeding the limit.

[1] https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-7.0.html#_cluster_wide_shard_soft_limit

Bug: Issue 10120
Change-Id: I6644cf9ee84a6133005d07c2310761707a74b96c