[ZBXNEXT-4320] Elasticsearch : store history data in multiple date-based indices Created: 2018 Jan 08 Updated: 2024 Apr 10 Resolved: 2018 May 24 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F), Server (S) |
Affects Version/s: | 3.4.5 |
Fix Version/s: | 4.0.0alpha7, 4.0 (plan) |
Type: | Change Request | Priority: | Critical |
Reporter: | Julien Leboeuf | Assignee: | Vjaceslavs Bogdanovs |
Resolution: | Fixed | Votes: | 3 |
Labels: | elasticsearch | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||||||
Team: | Team D | ||||||||
Team: | Team D | ||||||||
Sprint: | Sprint 33, Sprint 34 | ||||||||
Story Points: | 1 |
Description |
In order to properly scale history data in elasticsearch, we should use multiple indices per type, and the common way to split them is by date. With only one index, we can't dynamically add shards as index grows (a reindex is needed otherwise), we can't store fresh data in hot nodes and move old ones to cold nodes, etc.. IMO there are two ways to achieve date based indices setup :
|
Comments |
Comment by Luzin Anatolij Alekseevich [ 2018 May 07 ] |
Hello! |
Comment by Julien Leboeuf [ 2018 May 23 ] |
Thank you so much for implementing this feature ! Now the way is open to long term storage of metric data and fast querying |