[SERVER-34953] MobileSE: validate on mobile should retry SQLITE_BUSY errors Created: 11/May/18 Updated: 06/Dec/22 Resolved: 20/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | nonnyc, storage-engines | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, MobileRecordStore::validate() uses a SqliteStatement to read data from the collection being validated. This construct can throw a WriteConflictException, but there is no outer WriteConflict retry loop to back-off-and-retry when this error occurs. |
| Comments |
| Comment by Sulabh Mahajan [ 20/Jun/18 ] |
|
|
| Comment by Alexander Gorrod [ 18/May/18 ] |
|
This will likely be resolved along with the changes in |