[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:
Duplicate
duplicates SERVER-33992 Mobile SE: Test validate functionalit... Closed
Related
is related to SERVER-32997 Mobile SE: Design and implement multi... Closed
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 ]

SERVER-33992 is going to revisit validate() functionality and fix it to do the right thing for mobile and retry on receiving a busy error.

Comment by Alexander Gorrod [ 18/May/18 ]

This will likely be resolved along with the changes in SERVER-32997, but leaving open for now in case it isn't.

Generated at Thu Feb 08 04:38:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.