92b2c74ce1
When I proposed using serializable transactions I was hoping we would be able to refresh data of individual users concurrently. Unfortunately upon closer inspection it was revealed this was not the case. This could result in a lot of queries failing due to serialization errors, overloading the database in the process (given enough workers trying to update the target table). To work around this we're now using a Redis lease that is cancelled upon completion. This ensures we can update the data of different users concurrently without overloading the database. The code will try to obtain the lease until it succeeds, waiting at least 1 second between retries. This is necessary as we may otherwise end up _not_ updating the data which is not an option. |
||
|---|---|---|
| .. | ||
| 01_admin.rb | ||
| 04_project.rb | ||
| 05_users.rb | ||
| 06_teams.rb | ||
| 07_milestones.rb | ||
| 09_issues.rb | ||
| 10_merge_requests.rb | ||
| 11_keys.rb | ||
| 12_snippets.rb | ||
| 13_comments.rb | ||
| 14_pipelines.rb | ||
| 15_award_emoji.rb | ||
| 16_protected_branches.rb | ||
| 17_cycle_analytics.rb | ||