Elasticsearch/improvements: Difference between revisions

Browse history interactively

← Older edit

VisualWikitext

Revision as of 09:05, 9 June 2025 view source Greg Rundlett (talk \| contribs) 94 edits describe links Tag: Visual edit ← Older edit		Latest revision as of 10:06, 9 June 2025 view source Admin (talk \| contribs) Image-reviewer, Bureaucrats, Check users, confirmed, Moderators (CommentStreams), Interface administrators, Push subscription managers, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), staff, Suppressors, sysadmin, Administrators, uploadaccess, upwizcampeditors, Widget editors 2,745 edits link to issue 133 Tag: Visual edit
Line 1:		Line 1:
	There have been non-stop failures of the Elasticsearch backend due to memory constraints. We need to get to the bottom of it. Is it because the site is getting hammered by bots at the same time that the VM is undersized? Without increasing the size of the VM, can we better protect and limit the resources for stability?		There have been non-stop failures of the Elasticsearch backend due to memory constraints. We need to get to the bottom of it. Is it because the site is getting hammered by bots at the same time that the VM is undersized? Without increasing the size of the VM, can we better protect and limit the resources for stability?

	Aside from increasing site stability, there are additional platform tools we want to add like Metricbeat and/or Filebeat but we also want to convert to OpenSearch so we may well be duplicating the effort in short order.		Aside from increasing site stability, there are additional platform tools we want to add like Metricbeat and/or Filebeat '''but''' we also want to [https://github.com/freephile/meza/issues/133 convert to OpenSearch] (issue 133) so we may well be duplicating the effort in short order.