0 views collected around this technical thread.
This guide explains how to identify and remove outdated Elasticsearch indices by listing shards, filtering target indices, deleting them with a shell loop, and automating the process with a scheduled cron job, helping keep ELK performance optimal.
The article introduces the ECP system, a backend platform built on Elasticsearch that standardizes, automates, and visualizes index refresh workflows, addressing manual bottlenecks, data cleaning challenges, and coupling issues while providing task management, permission control, and environment isolation for high‑efficiency index operations.
This guide walks you through creating, viewing, updating, and deleting Elasticsearch indices, documents, and mappings using RESTful HTTP methods, complete with example requests, JSON bodies, and visual illustrations for each operation.
This guide walks through using Elasticsearch 7.8.0 and Postman to create, view, update, and delete indices and documents via RESTful API calls, including mapping setup and query‑based deletions, providing clear code examples and request details.
The article details WeChat Search’s practical distributed architecture—using a Chubby‑elected leader for shard‑to‑node mapping, hash‑based sharding with dynamic rebalancing, a Lambda‑style batch and near‑real‑time indexing pipeline, relaxed monotonic consistency, and group‑based searcher scaling—to illustrate trade‑offs and lessons for building scalable, reliable search services.
The article offers a thorough, step‑by‑step guide to Elasticsearch, explaining how to check cluster health, create and manage indices, define mappings and field types, use dynamic mapping, and perform maintenance tasks such as shrink, split, rollover, and cache management, all illustrated with concrete API examples.
This guide outlines practical capacity‑planning, index‑design, and write‑performance tuning for Tencent Cloud Elasticsearch clusters, covering compute and storage sizing, optimal shard counts, rollover strategies, bulk API settings, health monitoring, and common troubleshooting steps to ensure stable, high‑throughput search services.
Facing limited storage of Zabbix historical data in Elasticsearch, the article outlines a comprehensive strategy—expanding nodes, adding SSDs, redesigning index mapping, using hot‑cold node tiers, employing Curator for automated shrink, segment merging, and lifecycle management—to retain up to a year of monitoring data efficiently.