Skip to content

Remove outdated ES hardware recommendations

Manuel Grabowski requested to merge docs/mg-removeesrecommendations-20221108 into master

What does this MR do?

While working on https://gitlab.zendesk.com/agent/tickets/321721, we realized that https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html that we link to extensively here appears to be extremely outdated:

image

It's a bit confusing whether "version 2" in this case refers to ES2, or just version 2 of this specific "book" that contains this hardware chapter. It appears to be the latter, but according to the preface of that book version it also targets ES 2: https://www.elastic.co/guide/en/elasticsearch/guide/current/_elasticsearch_version.html – the copyright notice was last updated in 2015.

I'm happy to be proven wrong and closing this MR, but I could not find any evidence to the contrary and think we should remove the references. Unfortunately it seems that ES does not have a more current version of that information, so unless we come up with our own recommendations it appears that we won't be able to give any specific guidance regarding resources for ES.

Related issues

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

Merge request reports