1f8f7ebf06
inconsistency The original design had a flaw which can potentially cause discrepancy for nodes reputation status between reputations table and nodes table. In the event of a failure(network issue, db failure, satellite failure, etc.) happens between update to reputations table and update to nodes table, data can be out of sync. This PR tries to fix above issue by passing through node's reputation from the beginning of an audit/repair(this data is from nodes table) to the next update in reputation service. If the updated reputation status from the service is different from the existing node status, the service will try to update nodes table. In the case of a failure, the service will be able to try update nodes table again since it can see the discrepancy of the data. This will allow both tables to be in-sync eventually. Change-Id: Ic22130b4503a594b7177237b18f7e68305c2f122 |
||
|---|---|---|
| .. | ||
| straynodes | ||
| benchmark_test.go | ||
| checkin_test.go | ||
| config.go | ||
| db_test.go | ||
| downloadselection_test.go | ||
| downloadselection.go | ||
| peeridentities_test.go | ||
| peeridentities.go | ||
| piececount_test.go | ||
| selection_test.go | ||
| service_test.go | ||
| service.go | ||
| statdb_test.go | ||
| uploadselection_test.go | ||
| uploadselection.go | ||