Elasticsearch configured in discovery mode, even though it is single-node

[johanneskastl]

I am by no way a elasticsearch expert, so please take this with a grain of salt.

I just noticed a message in the elasticsearch pod:

[2023-10-31T06:57:57,993][WARN ][o.e.c.c.Coordinator      ] [zammad-elasticsearch-master-0] This node is a fully-formed single-node cluster with cluster UUID [XKSSYMBYTaKcGJw8ztqpuQ], but it is configured as if to discover other nodes and form a multi-node cluster via the [discovery.seed_hosts=[zammad-elasticsearch-master-hl.zammad.svc.cluster.local]] setting. Fully-formed clusters do not attempt to discover other nodes, and nodes with different cluster UUIDs cannot belong to the same cluster. The cluster UUID persists across restarts and can only be changed by deleting the contents of the node's data path(s). Remove the discovery configuration to suppress this message.

Not sure if discovery is enabled intentionally (to allow the user to add more replicas or similar). If not, it might be a good idea to disable it to not spam the logs unnecessarily...

https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html#single-node-discovery

[monotek]

Thanks for the hint. Feel free to add a PR, changing the setting :)

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[johanneskastl]

Thanks for the hint. Feel free to add a PR, changing the setting :)

Sorry, this got completely lost. Unfortunately I have no idea what exactly needs to be changed, as I have never had the luck (hust hust) to work with elasticsearch... :-)

[mgruner]

.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.