Replication Actions: Allow to control replication type - async or sync
#196
Comments
|
Replication Actions: Allow to control replication type - |
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…lastic#196) Add TF variable to select AMI version Added new tfvars variable `sw_version` to simplify AMI selection. By default it's an empty string (i.e. will not change current behavior of picking latest AMIs). To specify an AMI from a specific software version, e.g. v1.9, add `sw_version = "v1.9."` and TF will pick the latest AMI that matches "v1.9.*". Approved-by: Can Yildiz
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we document a specific walkthrough for the necessary steps that need to be done to cleanup and retrigger a failed nightly benchmark.
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow to control the replication type for index, delete, and delete_by_query operations. The replication type defaults to the node replication setting:
action.replication_type, which in turn, defaults tosync.The replication type can also be set on a per operation basis using the
replicationparameter accepting thesync, andasyncvalues.The text was updated successfully, but these errors were encountered: