[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:
Depends
Duplicate
is duplicated by SERVER-10723 Bulk insert is slow in sharded enviro... Closed
is duplicated by SERVER-12787 Strange performance characteristics o... Closed
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: SERVER-12950 don't mark writes as completed after errors in ordered batch
Branch: master
https://github.com/mongodb/mongo/commit/9fae141a1f3fe652fa6002e47722c5ceb051cffb

Comment by Githook User [ 03/Mar/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-12950 break ordered batches at first multi-shard op
Branch: master
https://github.com/mongodb/mongo/commit/24f85cdfdba1db685f4da499d8fcb77385e57da7

Generated at Thu Feb 08 03:30:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.