Guance ES Multi-tenant Lifecycle Management Practice¶

I. Life Cycle Management(ilm)¶

1.1 Data Stage¶

Stage Name	Description	Write in	Query
hot	Thermal data stage	Frequent writing	Frequent query
warm	Temperature data stage	Unable to write	More frequent queries
cold	Cold data stage	Unable to write	Infrequent query, slow query
frozen	Freezing data stage	Unable to write	Very few queries, very slow queries
delete	Delete data stage	Unable to write	Unable to query

1.2 Index Operation¶

Note:

（1）In the hot data phase, the starting point of rolling time is the index creation time

（2）For other data stages (except hot data stage), the starting point of time calculation is the rolling end time

1.3 Example¶

II Practical application of Guance¶

Storage Policy	Description	Thermal Data Stage	Temperature Data Stage	Delete Data Stage
es_rp0	Save data for 1 day	min_age = 0 rollover	min_age = 6h forcemerge {1} shrink	min_age = 1d delete
es_rp2d	Save data for 2 days	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age = 2d delete
es_rp1	Save data for 7 days (a week)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age = 7d delete
es_rp2	Save data for 14 days(2 weeks)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age = 14d delete
es_rp3	Save data for 30 days(a month)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age = 30d delete
es_rp60d	Save data for 60 days (2 months)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age = 60d delete
es_rp4	Save data for 90 days (3 months)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age = 90d delete
es_rp5	Save data for 180 days (half a year)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age = 180d delete
es_rp6	Save data for 360 days (a year)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age = 360d delete
es_rp720d	Save data for 720 days (nearly 2 years)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age=720d delete
es_rp7	Save data for 1095 days (3 years)	min_age = 0 rollover	min_age = 1d forcemerge {1} shrink	min_age=1095d delete

III. FAQ¶

3.1 Reduced Data Storage Time¶

After modifying the saving policy, a new index will be scrolled out. The previous index data will not be deleted until the deletion date condition is met, that is, the previous index data will be measured and charged all the time.

3.2 Longer Data saving Time¶

After modifying the saving policy, a new index will be scrolled out. Before that, the saving time of index data will not be longer, and the new index saving time will use the new configuration.