Expedited delete » History » Version 1
Tom Clegg, 06/08/2016 02:48 PM
| 1 | 1 | Tom Clegg | h1. Expedited delete |
|---|---|---|---|
| 2 | |||
| 3 | See #9364, #9278, [[Expiring collections]] |
||
| 4 | |||
| 5 | Example use case: a user has stored a very large collection, then realized one or more of the following: |
||
| 6 | * This data should not be stored here at all (uploaded the wrong files) |
||
| 7 | * This data consumes too much space (disks are full) |
||
| 8 | * This data costs too much to store (using too much cloud storage) |
||
| 9 | |||
| 10 | An admin should be able to delete the relevant blocks, bypassing the usual GC-race window, but (aside from that) in the safest possible way. |