[SERVER-28697] Ignore some NoProgressMade errors in sharding_balance4.js Created: 07/Apr/17  Updated: 15/Aug/17  Resolved: 10/Apr/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.5
Fix Version/s: 3.4.4, 3.5.6

Type: Bug Priority: Major - P3
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:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Sharding 2017-04-17
Participants:
Linked BF Score: 0

 Description   

The sharding_balance4.js test fails occasionally because more than 5 migrations manage to complete since the write operation started and because of this the write never manages to establish a shard version.

We should ignore up to certain number of NoProgressMade errors in order to make the test less likely to fail. This doesn't fix the inherent raciness though.



 Comments   
Comment by Githook User [ 11/Apr/17 ]

Author:

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

Message: SERVER-28697 Ignore up to 3 consectuive NoProgressMade errors in sharding_balance4.js

(cherry picked from commit 0cda35aea08ed51180239af6b18996927aa799c7)
Branch: v3.4
https://github.com/mongodb/mongo/commit/dbb62093678716934383d0e777ff836623bf634b

Comment by Githook User [ 10/Apr/17 ]

Author:

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

Message: SERVER-28697 Ignore up to 3 consectuive NoProgressMade errors in sharding_balance4.js
Branch: master
https://github.com/mongodb/mongo/commit/0cda35aea08ed51180239af6b18996927aa799c7

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