[SERVER-12950] Ordered write commands in mongos do not correctly break batches Created: 27/Feb/14 Updated: 11/Jul/16 Resolved: 03/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | 2.6.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
There is a batch per-op, which is very slow for large number of ops. Correct behavior is to figure out how many of the next ops can go to the same shard, then send all those in a batch. (Ops that go to multiple shards must be sent on their own in ordered mode.) Current workaround is to use unordered batches for performance testing. |
| Comments |
| Comment by Githook User [ 04/Mar/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by Githook User [ 03/Mar/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |