Pain point · Reliability & bugs · Causes churn
Tracker returns 500s with database deadlocks after upgrade to 2.7.0
1 source thread · first seen 2014-10
Summary
After upgrading from 2.2.2 to 2.7.0, a bulk tracking importer using parallel threads started getting 500 errors from deadlocks on the visit table.
- Affects
- Teams using bulk tracking API
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“now when i run the same importer, i start getting error 500s from the tracker requests”