[SERVER-26433] initial_sync_invalid_index_spec.js: Increase timeout and add handling for use3dot2InitialSync Created: 03/Oct/16  Updated: 19/Nov/16  Resolved: 06/Oct/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.0-rc1

Type: Task Priority: Major - P3
Reporter: James Wahlin Assignee: James Wahlin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Minor Change
Sprint: Integration 2016-10-10
Participants:
Linked BF Score: 0

 Description   

initial_sync_invalid_index_spec.js expects an invalid index specification option to cause members performing initial sync to abort on application. Currently the timeout is 60 seconds which is not sufficient for the initsync-3dot2-rhel-62 evergreen variant (as reported by BF-3671). We should increase the timeout to at least 120 seconds (if not the default of 5 minutes).

Additionally the initsync-3dot2-rhel-62 evergreen variant abort is triggered by a different assertion than the normal path. Add handling to recognize this assertion.



 Comments   
Comment by Githook User [ 06/Oct/16 ]

Author:

{u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}

Message: SERVER-26433 initial_sync_invalid_index_spec.js: Support for use3dot2InitialSync
Branch: master
https://github.com/mongodb/mongo/commit/6a66a952e86980f5393ed1dab1e6d4950a963de8

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