Currently, each of my indexes is set to a specific and own frozenTimePeriodInSecs, but I am noticing they are not rolling over to cold when the frozenTimePeriodInSecs value is set.
Data Age (keeps growing) vs Frozen Age (stays as what it is set in frozenTimePeriodInSecs)
maxWarmDBCount is set to:
maxWarmDBCount = 4294967295
Does this effect?
If the value is changed, would data roll to cold?
@rickymckenzie10 - To simplify your understanding of warm and cold buckets and different parameters.
(Only applicable when you are not using volumes)
Warm Buckets -> buckets in /db path
Cold Buckets -> buckets in /colddb path
Frozen Buckets -> Deleted/Archived data
Warm to Cold Bucket Movement -> when maxWarmDBCount bucket count is reached.
Cold to Frozen (deleting, max age) Bucket Movement -> when all events are older than frozenTimePeriodInSecs
I hope this helps you understand the parameters better. Kindly upvote if it does!!!
Hey Ricky,
AFAIK maxWarmDBCount doesn't affect the rollover of data (but it can be storage hungry so be careful with that), it is something the frozenTimePeriodInSecs do instead. In your case, if I understood correctly, the frozen time already passed but your data did not rolled over, and that may be either because your cluster manager is too busy at the moment (and you are experiencing delay in this processing) OR maybe it is waiting for the buckets to hit a threshold in size. Check the bucket replication status also, it may indicate if there is any problem in there...
Are you using maxTotalDataSizeMB key by any chance? Try to add that also to see if you get any diff behavior.
@victor_menezes can you expand a little more on this:
AFAIK maxWarmDBCount doesn't affect the rollover of data (but it can be storage hungry so be careful with that), it is something the frozenTimePeriodInSecs do instead
Yes, I am using maxTotalDataSizeMB in each of the indexes. They all have their specific size.