[SERVER-23665] Direct config server write in batch_write_command_sharded.js should wait for replication Created: 12/Apr/16  Updated: 26/Apr/16  Resolved: 12/Apr/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.5

Type: Bug Priority: Minor - P4
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 13 (04/22/16)
Participants:
Linked BF Score: 0

 Description   

The batch_write_command_sharded.js has a step, which directly writes to the config servers and then performs operation, which expects the data just written to be visible by mongos. This may not happen if the write has not propagated to the secondary node chosen by mongos.

We should fix the test to wait for replication.



 Comments   
Comment by Githook User [ 12/Apr/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-23665 Wait for replication in batch_write_command_sharded.js
Branch: master
https://github.com/mongodb/mongo/commit/51abe7d21b799a3758ce71d18ac7d6a088f71e2c

Generated at Thu Feb 08 04:04:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.