Handle Cassandra unavailability when accepting a new report.
Bug #1167838 reported by
Evan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Daisy |
New
|
Undecided
|
Unassigned | ||
Bug Description
We often get AllServersUnava
https:/
https:/
Rather than half-write the data for a new report, bucket, or metadata, we should back out inserts by attempting to delete them on failure where it is safe to do so.
To post a comment you must log in.
