[SERVER-76712] Inserting large number of documents (100k) into sharded collection fails with BSONObjectTooLarge after leader election Created: 01/May/23 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.20, 4.4.21 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Craven Huynh | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Steps to reproduce documented here: |
||||||||
| Participants: | |||||||||
| Story Points: | 3 | ||||||||
| Description |
|
Inserting large number of documents (100k) into sharded collection fails with BSONObjectTooLarge after leader election:
Rerunning the same insert immediately after will succeed.
This happens for both pymongo and the go-driver. Additional note: under certain circumstances, running `db.adminCommand( { flushRouterConfig: "test.apricot" })` would avoid this error as well. I think doing so after a leader election works, but flushing before a leader election does not. |