mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
[DOCS] Swap [float]
for [discrete]
(#60124)
Changes instances of `[float]` in our docs for `[discrete]`. Asciidoctor prefers the `[discrete]` tag for floating headings: https://asciidoctor.org/docs/asciidoc-asciidoctor-diffs/#blocks
This commit is contained in:
parent
8ad8421262
commit
2774cd6938
258 changed files with 1023 additions and 1023 deletions
|
@ -33,7 +33,7 @@ The documentation for each plugin usually includes specific installation
|
|||
instructions for that plugin, but below we document the various available
|
||||
options:
|
||||
|
||||
[float]
|
||||
[discrete]
|
||||
=== Core Elasticsearch plugins
|
||||
|
||||
Core Elasticsearch plugins can be installed as follows:
|
||||
|
@ -149,7 +149,7 @@ For safety reasons, a node will not start if it is missing a mandatory plugin.
|
|||
[[listing-removing-updating]]
|
||||
=== Listing, Removing and Updating Installed Plugins
|
||||
|
||||
[float]
|
||||
[discrete]
|
||||
=== Listing plugins
|
||||
|
||||
A list of the currently loaded plugins can be retrieved with the `list` option:
|
||||
|
@ -162,7 +162,7 @@ sudo bin/elasticsearch-plugin list
|
|||
Alternatively, use the {ref}/cluster-nodes-info.html[node-info API] to find
|
||||
out which plugins are installed on each node in the cluster
|
||||
|
||||
[float]
|
||||
[discrete]
|
||||
=== Removing plugins
|
||||
|
||||
Plugins can be removed manually, by deleting the appropriate directory under
|
||||
|
@ -182,7 +182,7 @@ purge the configuration files while removing a plugin, use `-p` or `--purge`.
|
|||
This can option can be used after a plugin is removed to remove any lingering
|
||||
configuration files.
|
||||
|
||||
[float]
|
||||
[discrete]
|
||||
=== Updating plugins
|
||||
|
||||
Plugins are built for a specific version of Elasticsearch, and therefore must be reinstalled
|
||||
|
@ -198,7 +198,7 @@ sudo bin/elasticsearch-plugin install [pluginname]
|
|||
|
||||
The `plugin` scripts supports a number of other command line parameters:
|
||||
|
||||
[float]
|
||||
[discrete]
|
||||
=== Silent/Verbose mode
|
||||
|
||||
The `--verbose` parameter outputs more debug information, while the `--silent`
|
||||
|
@ -211,7 +211,7 @@ return the following exit codes:
|
|||
`74`:: IO error
|
||||
`70`:: any other error
|
||||
|
||||
[float]
|
||||
[discrete]
|
||||
=== Batch mode
|
||||
|
||||
Certain plugins require more privileges than those provided by default in core
|
||||
|
@ -229,7 +229,7 @@ mode can be forced by specifying `-b` or `--batch` as follows:
|
|||
sudo bin/elasticsearch-plugin install --batch [pluginname]
|
||||
-----------------------------------
|
||||
|
||||
[float]
|
||||
[discrete]
|
||||
=== Custom config directory
|
||||
|
||||
If your `elasticsearch.yml` config file is in a custom location, you will need
|
||||
|
@ -241,7 +241,7 @@ can do this as follows:
|
|||
sudo ES_PATH_CONF=/path/to/conf/dir bin/elasticsearch-plugin install <plugin name>
|
||||
---------------------
|
||||
|
||||
[float]
|
||||
[discrete]
|
||||
=== Proxy settings
|
||||
|
||||
To install a plugin via a proxy, you can add the proxy details to the
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue