Description
We are seeing an issue with levelDB retention in long-running broker instances. JMX statistics are not showing many messages on destinations, but the store size is eventually climbing to many GB (50-100 observed). If we restart the broker with no other corrective action, we see disk usage drop back to less than 1 GB, so it appears that heuristic / scheduled cleanup is not working, for some reason.