ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Data eviction/expiration from Ignite persistence
Date Fri, 17 Nov 2017 21:40:59 GMT

I’ve been talking to many Ignite users here and there who are already on Ignite persistence
or consider to turn it on. The majority of them are more than satisfied with its current state
and provided capabilities. That’s is really good news for us.

However, I tend to come across the people who ask about eviction/expiration policies for the
persistence itself. Had around 6 conversation about the topic this month only.

Usually the requirement is connected with a streaming use case. When an application streams
a lot of data (IoT, metrics, etc.) to the cluster but the data becomes stale in some period
of time (day, couple of days, etc.). The user doesn’t want to waste the disk space and needs
to simple purge the data from there.

My suggestion here is to create a timer task that will remove the stale data from the cluster.
However, since the demand is growing probably it’s a good time to discuss a feasibility
of this feature.

Alex G, as the main architect of the persistence, could you share your thoughts on this? What
will it cost to us to support eviction/expiration for the persistence?

View raw message