[COMPASS-4052] Queries longer than 60 seconds time out even with MAXTIMEMS set to a value greater than 60 seconds Created: 18/Dec/19  Updated: 10/Jan/24  Resolved: 04/Aug/20

Status: Closed
Project: Compass
Component/s: Query Bar
Affects Version/s: 1.19.12, 1.20.1
Fix Version/s: No version

Type: Bug Priority: Major - P3
Reporter: Martin Canovas Assignee: Maurizio Casimirri
Resolution: Duplicate Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File DEV console.jpg     JPEG File timeout1.jpg    
Issue Links:
Related
is related to COMPASS-4381 Allow to set socketTimeoutMS in the c... Closed
Documentation Changes: Not Needed
Sprint: Iteration Xerus, Iteration Yak, Iteration Zebra, Iteration Avocado, Iteration Blackberry, Iteration Cantaloupe, Iteration Dragon Fruit, Iteration Elderberry, Iteration Fig, Iteration GuanĂ¡bana, Iteration Huckleberry, Iteration Icaco

 Description   

Compass is timing out when queries take longer than 60 seconds to complete.

This happens even when setting the "MAXTIMEMS" option to a value greater than 60 seconds.



 Comments   
Comment by Maurizio Casimirri [ 04/Aug/20 ]

Closing for https://jira.mongodb.org/browse/COMPASS-4381

Comment by Massimiliano Marcon [ 09/Mar/20 ]

jeffrey.allen done!

Generated at Wed Feb 07 22:35:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.