mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 15:47:23 -04:00
fc287bde8b
APIs which perform cluster state updates typically accept the `?master_timeout=` and `?timeout=` parameters to respectively set the pending task queue timeout and the acking timeout for the cluster state update. Both of these parameters accept the value `-1`, but `?master_timeout=-1` means to wait indefinitely whereas `?timeout=-1` means the same thing as `?timeout=0`, namely that acking times out immediately on commit. There are some situations where it makes sense to wait for as long as possible for nodes to ack a cluster state update. In practice this wait is bounded by other mechanisms (e.g. the lag detector will remove the node from the cluster after a couple of minutes of failing to apply cluster state updates) but these are not really the concern of clients. Therefore with this commit we change the meaning of `?timeout=-1` to mean that the acking timeout is infinite. |
||
|---|---|---|
| .. | ||
| logstash | ||
| security | ||
| watcher | ||
| common-options.asciidoc | ||
| common-parms.asciidoc | ||
| cron-expressions.asciidoc | ||
| defs.asciidoc | ||
| index.asciidoc | ||
| info.asciidoc | ||
| rest-api-compatibility.asciidoc | ||
| root.asciidoc | ||
| security.asciidoc | ||
| usage.asciidoc | ||
| watcher.asciidoc | ||