commit | 53c6c2d393d6d16f6a7bcffd1003320b20e0f90a | [log] [tgz] |
---|---|---|
author | David Pursehouse <dpursehouse@collab.net> | Wed Dec 04 12:46:31 2019 +0900 |
committer | David Pursehouse <dpursehouse@collab.net> | Wed Dec 04 12:51:24 2019 +0900 |
tree | 22b5594db48d0facacadcc2af90aa81732f32ee0 | |
parent | 105b303760cc6d25658fd0abc37b70d5992b54f7 [diff] |
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
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.