Purge chunking now uses a max primary key as the goal. If the purge chunk minId exceeds the maxId we're done. This solves the problem of ending the purge when the current cycle did not wipe any data. The purge.records-per-batch config option has increased because it now refers to how many keys we can per chunk, not how many records we delete per chunk. bug 796:resolved