[SERVER-41118] Have autocomplete.js handle slow listCollections responses Created: 13/May/19  Updated: 29/Oct/23  Resolved: 14/Sep/20

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: None
Fix Version/s: 4.8.0

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: David Percy
Resolution: Fixed Votes: 0
Labels: move-sa, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-35638 Shell auto-completion blocks when lis... Closed
is related to SERVER-41117 Blacklist autocomplete.js from parall... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 9

 Description   

Currently there is a fixed 1 second timeout, but on parallel testers or just in general on slow systems, it is possible for the command to take a longer time. For testing, the timeout should be far longer. After fixing this, consider reverting SERVER-41117 so testing with the parallel test suites is enabled again.



 Comments   
Comment by Githook User [ 11/Sep/20 ]

Author:

{'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}

Message: SERVER-41118 Only timeout autocomplete when interactive
Branch: master
https://github.com/mongodb/mongo/commit/50e5c61642bd21e9d781d283c15694f029160bb3

Comment by Sara Williamson [ 20/May/19 ]

Another potential solution would be to add a switch to change the timeout length based on whether or not the shell is in interactive mode. We'll add this to a future quick win bucket.

Comment by Max Hirschhorn [ 13/May/19 ]

geert.bosch, the 1-second timeout for listing collections on a database was recently introduced by the changes from b6cc1fb as part of SERVER-35638. CC jesse

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