[SERVER-69794] Investigate support for excluding sharding critical section checks in AutoGet Created: 19/Sep/22 Updated: 24/Jul/23 Resolved: 24/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
As part of One of the alternatives discussed was the possibility of adding support to the AutoGet RAII types. These currently perform a sharding check when acquiring the DB lock. This would better document places where it is safe to not do these checks. Currently the recommended choice is to manually acquire a DBLock or CollectionLock to skip them. If adding support to the AutoGet methods is the option considered, a follow-up ticket should work on removing current manual lock acquisition in favour of AutoGet. |
| Comments |
| Comment by Yujin Kang Park [ 21/Jul/23 ] |
|
jordi.serra-torrens@mongodb.com Yes, assuming this request might not be useful elsewhere, I think we should be able to close it after |
| Comment by Jordi Serra Torrens [ 21/Jul/23 ] |
|
yujin.kang@mongodb.com My understanding is that this request was related to index builds, and |
| Comment by Jordi Serra Torrens [ 22/Sep/22 ] |
|
I don't think we should skip dbVersion checks in some particular occasions. If the client declared a dbVersion, it should be always checked. |