Update elasticsearch-setup.rst for clustering#8757
Update elasticsearch-setup.rst for clustering#8757
Conversation
Note that I have no experience of deploying an Elasticsearch cluster, so these updates were created by Claude.
|
Newest code from mattermost has been published to preview environment for Git SHA 497d27c |
Updated after initial testing
|
Newest code from mattermost has been published to preview environment for Git SHA e3dc6a1 |
Further tweaks for accuracy
|
Newest code from mattermost has been published to preview environment for Git SHA 00f6390 |
Errors found in original doc
More fixes from original doc
|
Newest code from mattermost has been published to preview environment for Git SHA 19c27ba |
|
Newest code from mattermost has been published to preview environment for Git SHA 6db9c12 |
Adding more context for less experienced Linux admins
|
Newest code from mattermost has been published to preview environment for Git SHA 33ab58b |
Claude's an idiot!
|
Newest code from mattermost has been published to preview environment for Git SHA 0bc6082 |
Claude was hallucinating
|
Newest code from mattermost has been published to preview environment for Git SHA 2f3115c |
Added important detail about CA certificates for Elasticsearch v8
|
Newest code from mattermost has been published to preview environment for Git SHA 24dcb1b |
Final tweaks - ready for review
|
Newest code from mattermost has been published to preview environment for Git SHA 3cee54a |
esethna
left a comment
esethna
left a comment
There was a problem hiding this comment.
Thanks John! I made a few high level comments. A few other thoughts:
- Can you confirm you've run through the instructions as written for ES 8 end-to-end?
- Who can we get from the MM team to act as a technical SME for review?
|
|
||
| Set up Elasticsearch | ||
| --------------------- | ||
| Set up a single Elasticsearch node |
There was a problem hiding this comment.
Is there ever an instance where we recommend only 1 ES node? Looking at the reference architectures I don't see one. I think we need to be more prescriptive on when it should be 1 vs 2+, and make sure to point ot the reference architectures as the source of truth
| sudo systemctl start elasticsearch.service | ||
|
|
||
| 3. Confirm Elasticsearch is working on the server by running the following command: | ||
| 3. Confirm Elasticsearch is working on the server. For Elasticsearch 7.x: |
There was a problem hiding this comment.
My understanding is that ES 7 is deprecated now, so should we just have ES 8 instructions and remove everything related to ES7?
| Set up an Elasticsearch cluster | ||
| -------------------------------- | ||
|
|
||
| For production environments requiring high availability and fault tolerance, deploy Elasticsearch as a multi-node cluster rather than a single node. A cluster distributes data across multiple nodes, providing redundancy and improved search performance. If one node goes down, the remaining nodes continue to serve search requests without interruption. |
There was a problem hiding this comment.
Same here, we should be more opinionated on when a cluster is recommended, pointing to the reference architectures
|
|
||
| The ``cluster.initial_master_nodes`` setting is only used during the very first bootstrap of the cluster. Once the cluster is formed, this setting is ignored. Some administrators choose to remove it after initial cluster formation to prevent accidental re-bootstrapping. | ||
|
|
||
| Set up a cluster using Elasticsearch 7.x |
2 participants
Note that I have no experience of deploying an Elasticsearch cluster, so these updates were created by Claude.
Summary
Ticket Link