Bumping the logging level is key to this; even if you succeed in finding
data files that demonstrate what happened, without the more detailed
logging it may be impossible to tell *why* it happened. If you get a large
enough disk attached to the machine to hold months of logs, that's great,
just mak
It is possible that there is a bug in the ack compaction feature, but if so
it only shows itself in
some very special cases. I have tried stressing it, but to no avail. In all
my tests the broker
does the right thing.
There are no cron jobs deleting any files in this system. The broker thinks
that
I've never seen anything like this on the mailing list, and the one project
where I've been directly involved in managing brokers used non-persistent
messaging exclusively so I've never seen it personally.
Here are a few crazy ideas of what might possibly cause the behavior you
described:
- As
