should there be something to suppress posts when files are created...

Nobody has claimed this yet.

on systems that are more heavily loaded, or running slower, there seems to be a tendency for INOTIFY
to produce CREAT events for the file being created, and then separate modify events...

possibilities:

* we are periodically processing and event queue. should we read the queue once, looking for duplicates, and remove the first op?
* there is already a flag for create events, perhaps just set that off in flow tests, and perhaps elsewhere. problem is... what if someone actually is creating an empty file? then it just will not be propagated.

It would be an enhancement if we can reduce the number of posts needed to duplicate the same tree by omitting CREAT events that are overridden by modifies...

We could go further in the batching... say for empty files, hold onto them for a few seconds in a queue, and only create them if no other event comes later to squash them...

not sure. currently this is taken care of by putting plugins in shovels/winnows, so no effect on HPC mirror client, but it complicates deployment a bit.

Start by tracing the INOTIFY event queue and the handling of CREAT and MODIFY events. Clarify whether duplicate events should be removed during batching and how empty files must be preserved; done should include a defined behavior and validation that reduces redundant posts without losing legitimate creations.

Written by the indexing model from the issue text.