ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Igfs PURGE events: do we need them?
Date Fri, 20 Nov 2015 18:10:21 GMT

The importance of the PURGE event has to do with notification about freeing
memory, otherwise occupied by a deleted file.

How hard do you think would be making the PURGE behavior consistent between
directory and file deletions?


On Fri, Nov 20, 2015 at 8:15 AM, Ivan V. <iveselovskiy@gridgain.com> wrote:

> Hi, dev,
> need opinions on the question discussed in
> https://issues.apache.org/jira/browse/IGNITE-1679  (IGFS: Purge event is
> inconsistent).
> In short: in Igfs we have "soft" delete that moves the deleted file or
> folder to special "TRASH" folder.
> Special async worker walks inside TRASH and removes the items permanently.
> When an item is completely removed, an event of type
> org.apache.ignite.events.EventType#EVT_IGFS_FILE_PURGED  is fired.
> But such events are now fired only for files, and only in case if such file
> was deleted itself, but not a part of a folder sub-tree. It's quite obvious
> that such behavior is not quite consistent, so we should either get rid of
> PURGE events at all, or make them consistent.
> In the latter case it would be good to have answer to the question: what
> are real  use cases when we may need the purge events ? (Now they seem to
> be used in tests only).
> If we don't have such real use cases, are there any objections to get rid
> of the purge events at all?
> Thanks in advance.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message