Skip to content

Commit

Permalink
Moved guidance on passing env vars as args to Configuration - it was …
Browse files Browse the repository at this point in the history
…previously under installation (#962) (#969)

Signed-off-by: JeffH-AWS <[email protected]>

Signed-off-by: JeffH-AWS <[email protected]>
(cherry picked from commit 4303783)

Co-authored-by: Jeff Huss <[email protected]>
  • Loading branch information
opensearch-trigger-bot[bot] and Jeff Huss authored Aug 24, 2022
1 parent ee786c5 commit 02d51de
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions _opensearch/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,13 @@ Most OpenSearch configuration can take place in the cluster settings API. Certai

Whenever possible, use the cluster settings API instead; `opensearch.yml` is local to each node, whereas the API applies the setting to all nodes in the cluster. Certain settings, however, require `opensearch.yml`. In general, these settings relate to networking, cluster formation, and the local file system. To learn more, see [Cluster formation]({{site.url}}{{site.baseurl}}/opensearch/cluster/).

## Specify settings as environment variables

You can specify environment variables as arguments using `-E` when launching OpenSearch:

```bash
./opensearch -Ecluster.name=opensearch-cluster -Enode.name=opensearch-node1 -Ehttp.host=0.0.0.0 -Ediscovery.type=single-node
```

## Update cluster settings using the API

Expand Down

0 comments on commit 02d51de

Please sign in to comment.