Turn on durability downgrading
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Dmedia |
Fix Released
|
High
|
Jason Gerard DeRose | ||
Bug Description
So this month we're also turning on the automatic durability downgrading.
Dmedia tracks each location where a file is stored. Normally a location provides 1 or more "copies" worth of durability, but there are a number of scenarios that can cause Dmedia to downgrade its confidence in a location, which means setting that location to zero "copies".
These thresholds will be tuned over time, and eventually we'll develop a more subtle statical model. For now, the schema is deliberately simplistic, with just enough complexity to drive the automation behaviors. And for now we're using some static thresholds that are hopefully conservative enough, but are also pretty much arbitrary:
* If a given drive (FileStore) hasn't been connected in more than 1 week, we downgrade all the copies in that FileStore
* If a new file that has *never* been verified goes more than 48 hours without being verified, we downgrade
* If a file that has been verified at least once in the past goes more than 4 weeks without being verified, we downgrade
Related branches
- James Raymond: Approve
- Matteo Ronchetti (community): Approve
-
Diff: 1426 lines (+1100/-123)10 files modifiedbenchmark-purge-store.py (+66/-0)
dmedia-cli (+6/-0)
dmedia-service (+6/-0)
dmedia/core.py (+5/-20)
dmedia/metastore.py (+107/-2)
dmedia/tests/base.py (+5/-4)
dmedia/tests/test_core.py (+0/-91)
dmedia/tests/test_metastore.py (+506/-0)
dmedia/tests/test_views.py (+376/-0)
dmedia/views.py (+23/-6)
| Changed in dmedia: | |
| status: | In Progress → Fix Committed |
| Changed in dmedia: | |
| status: | Fix Committed → Fix Released |
