Bug #210
Writing to DB should take an exponential backoff approach
| Status: | Closed | Start date: | 04/08/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | Release 2.0 | |||
| Resolution: | wontfix | Pull request: | ||
| Affected Versions: |
Description
Now it tries 10 times each 1 milisecond, if the scheduler locks the DB for more than 10 milliseconds (which is not rare in high volume VMs envs) access to the DB is blocked and strange behavior arises. This compromises scalability.
Associated revisions
History
#1
Updated by Ruben S. Montero about 11 years ago
- Status changed from New to Closed
- Resolution set to wontfix
With the new scheduler and DB backends this is not needed