ee https://docs.google.com/document/d/18H0k_QKo0a9b9fDndhw3MXm6Db27lmXzFAOjDPFA1T4/edit#heading=h.19lnn0712d8r
for a description of the problem. Basically, we create a lot of IndexedDB Index Key tombstones (not leveldb tombstones) when we operate on object stores that have Indexes.
The bug tracks the CLs for adding the stats collecting / tombstone crawling feature, and should serve as the Finch bug.
Why do we want to use finch? We don't need to gather stats from the entire population, as it is a little risky and also incurs disk activity. We are fine with a small sample. Once we have gathered stats, we gradually turn on deletion.
For both stats and deletion, we want to carefully monitor all errors, as this sweeper does a lot of disk analysis and reports very robust error metrics. We want to be extra careful to not break anything, even though there are tests.
Comment 1 by jsb...@chromium.org
, Jun 5 2017