8c52bb3a18
A few weeks ago it was discovered that the segment health function was not working as expected with production values. As a bandaid, we decided to insert the number of healthy pieces into the segment health column. This should have effectively reverted our means of prioritizing repair to the previous implementation. However, it turns out that the bandaid was placed into the code which removes items from the irreparable db and inserts them into the repair queue. This change: insert number of healthy pieces into the repair queue in the method, RemoteSegment Change-Id: Iabfc7984df0a928066b69e9aecb6f615253f1ad2 |
||
|---|---|---|
| .. | ||
| checker | ||
| irreparable | ||
| queue | ||
| repairer | ||
| priority_test.go | ||
| priority.go | ||
| repair_test.go | ||
| repair.go | ||