)]}'
{
  "commit": "53c6c2d393d6d16f6a7bcffd1003320b20e0f90a",
  "tree": "22b5594db48d0facacadcc2af90aa81732f32ee0",
  "parents": [
    "105b303760cc6d25658fd0abc37b70d5992b54f7"
  ],
  "author": {
    "name": "David Pursehouse",
    "email": "dpursehouse@collab.net",
    "time": "Wed Dec 04 12:46:31 2019 +0900"
  },
  "committer": {
    "name": "David Pursehouse",
    "email": "dpursehouse@collab.net",
    "time": "Wed Dec 04 12:51:24 2019 +0900"
  },
  "message": "ElasticV6QueryChangesTest: Close indices after test\n\nFor each test method, new indices are created with a unique name based\non the test method name. This results in 4 indices (i.e. one each for\naccounts, changes, groups and projects) for each test method that is\nrun, which in turn results in the number of allocated shards increasing.\n\nIn Elasticsearch 7.0 a shard limit was introduced [1] which so far only\ncauses a warning. However in a future version the limit will be enforced\nand result in an error.\n\nAfter each test, close the indices that were created. This results in\nthe shards being deallocated, and prevents exceeding the limit.\n\nNote that this was originally fixed in Change I6644cf9ee for ES 7.x\nbut the shard limit warning was backported to 6.x with [2] which was\nincluded since 6.8.5, so we are now also seeing warnings in the logs\nwhen running the tests for V6.\n\n[1] https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-7.0.html#_cluster_wide_shard_soft_limit\n[2] https://github.com/elastic/elasticsearch/commit/aa8b5e8\n\nBug: Issue 10120\nChange-Id: I61966c28c2640246e7a5edd026aa31d77c8533eb\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "08f48396a01dd7016c9b1755d1b01a43fc981329",
      "old_mode": 33188,
      "old_path": "javatests/com/google/gerrit/elasticsearch/ElasticV6QueryChangesTest.java",
      "new_id": "94c5a0490173b9c1949adb1c8220b2c3fe9c84bc",
      "new_mode": 33188,
      "new_path": "javatests/com/google/gerrit/elasticsearch/ElasticV6QueryChangesTest.java"
    }
  ]
}