tree 22b5594db48d0facacadcc2af90aa81732f32ee0
parent 105b303760cc6d25658fd0abc37b70d5992b54f7
author David Pursehouse <dpursehouse@collab.net> 1575431191 +0900
committer David Pursehouse <dpursehouse@collab.net> 1575431484 +0900

ElasticV6QueryChangesTest: 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 4 indices (i.e. one each for
accounts, changes, groups and projects) 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 was introduced [1] which so far only
causes a warning. However in a future version 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.

Note that this was originally fixed in Change I6644cf9ee for ES 7.x
but the shard limit warning was backported to 6.x with [2] which was
included since 6.8.5, so we are now also seeing warnings in the logs
when running the tests for V6.

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

Bug: Issue 10120
Change-Id: I61966c28c2640246e7a5edd026aa31d77c8533eb