339d1212cd
It's impossible to time correctly this check. The segment may expire just at the time we upload the repaired pieces to new storage nodes. They will reject this as expired and the repair will fail. Also, we penalize storage nodes with audit failure only if they fail piece hash verification, i.e. return incorrect data, but only if they have already deleted the piece. So, it would be best if the repair service does not care about object expiration at all. This is a responsibility of another service. Removing this check will also simplify how we migrate this code correctly to the metabase. Change-Id: I09f7b372ae2602daee919a8a73cd0475fb263cd2 |
||
|---|---|---|
| .. | ||
| checker | ||
| irreparable | ||
| queue | ||
| repairer | ||
| priority_test.go | ||
| priority.go | ||
| repair_test.go | ||
| repair.go | ||