-
Notifications
You must be signed in to change notification settings - Fork 25.2k
ThreadPool: Rename dynamic to scaling #75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
ThreadPool: Rename dynamic to scaling, closed by 671bc4e. |
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
In elastic#73, we deprecated `content` field in favor of `_content` field. In plugin version 2.4.0, we can now remove the old field name. Closes elastic#75. (cherry picked from commit 7a0f838)
maabernethy
pushed a commit
to maabernethy/elasticsearch
that referenced
this issue
Mar 20, 2017
Claim Issue 14114
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
For elastic#36 - Add support for creating optional elasticsearch user and group
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
Since we already define the IP addresses of the target hosts in Jenkins[1], there's no need to duplicate this information in static inventory files, when setting up fixtures with night-rally. Switch to a dynamic inventory script for setting up the needed host groups for Ansible fixtures. [1] https://github.com/elastic/infra/blob/8dd21b2e6e451407515186ab60e71b5d22114ba9/ci/jjb/elasticsearch-ci/globals/templates/elastic-elasticsearch/macrobenchmarks.yml#L26-L29 Relates elastic#75
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Better fitting name, especially with other thread pools I plan to play with
The text was updated successfully, but these errors were encountered: