[SERVER-12275] Add MaxWriteBatchSize to isMaster results. Created: 07/Jan/14 Updated: 02/Aug/18 Resolved: 13/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Batches of writes sent via write commands are only valid if A) the total size of all "documents"/"updates"/"deletes" (not including array overhead) is < MaxBSONObjSize and B) the total number of "documents"/"updates"/"deletes" is less than some constant value (currently 1000). This constant should be accessible to clients via isMaster. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 25/Feb/14 ] |
|
The ticket to enforce this maximum is |
| Comment by Greg Studer [ 21/Feb/14 ] |
|
Yep, it should be. I'll open another ticket. |
| Comment by A. Jesse Jiryu Davis [ 21/Feb/14 ] |
|
Quick test against latest mongod and mongos code indicates that this limit is not enforced server side. Correct? |
| Comment by Githook User [ 08/Jan/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |