[SERVER-23885] Improve shard_aware_init.js run time Created: 22/Apr/16  Updated: 04/Jan/17  Resolved: 04/Jan/17

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

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: PM-108
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-23875 config_server_checks.js should check ... Closed
Sprint: Sharding 2017-01-02
Participants:

 Description   

The test intentionally modifies the shardIdentity document to an invalid one and tries to restart the shard. The mongod process is expected to abort here:

https://github.com/mongodb/mongo/blob/r3.3.4/jstests/sharding/shard_aware_init.js#L64

However, the shell process does not have a configurable timeout and waits for 10 minutes until it times out:

https://github.com/mongodb/mongo/blob/r3.3.4/src/mongo/shell/servers.js#L918



 Comments   
Comment by Dianna Hohensee (Inactive) [ 04/Jan/17 ]

Locally running the test, it takes 3 seconds, rather than 10 minutes, for this part of the JS test to execute. On evergreen, different variants take between half and two and a half minutes to run the test.

This issue has been incidentally resolved between April 2016 when this ticket was created and now, January 2017.

Comment by Benety Goh [ 30/Nov/16 ]

I think we can apply a fix to shard_aware_init.js that's similar to what was done here:

https://github.com/mongodb/mongo/commit/97d05f8a666b13b344a208448564b8417e1e9114#diff-517eda50242fd261fd959a08561e4b10R139

Comment by Eric Milkie [ 22/Apr/16 ]

benety.goh is writing something similar for another js test that needs this ability..

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