...
BugZero found this defect 2863 days ago.
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.
xgen-internal-githook commented on Tue, 11 Apr 2017 20:42:29 +0000: 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 xgen-internal-githook commented on Mon, 10 Apr 2017 20:06:36 +0000: 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