51b5dbffb7
While there are use-cases where a single-node is in production, there are also use-cases for starting a single-node that binds transport to an external interface where the node is not in production (for example, for testing the transport client against a node started in a Docker container). It's tricky to balance the desire to always enforce the bootstrap checks when a node might be in production with the need for the community to perform testing in situations that would trip the bootstrap checks. This commit enables some flexibility for these users. By setting the discovery type to "single-node", we disable the bootstrap checks independently of how transport is bound. While this sounds like a hole in the bootstrap checks, the bootstrap checks can already be avoided in the single-node use-case by binding only HTTP but not transport. For users that are genuinely in production on a single-node use-case with transport bound to an external use-case, they can set the system property "es.enable.bootstrap.checks" to force running the bootstrap checks. It would be a mistake for them not to do this. Relates #23598 |
||
|---|---|---|
| .. | ||
| install | ||
| sysconfig | ||
| bootstrap-checks.asciidoc | ||
| cluster_restart.asciidoc | ||
| configuration.asciidoc | ||
| important-settings.asciidoc | ||
| install.asciidoc | ||
| reindex_upgrade.asciidoc | ||
| rolling_upgrade.asciidoc | ||
| secure-settings.asciidoc | ||
| stopping.asciidoc | ||
| sysconfig.asciidoc | ||
| upgrade.asciidoc | ||