[COMPASS-3016] Compass fails to reconnect after client machine enters sleep state Created: 25/Jul/18  Updated: 29/Oct/23  Resolved: 13/Nov/19

Status: Closed
Project: Compass
Component/s: Compass
Affects Version/s: None
Fix Version/s: 1.20.0

Type: Bug Priority: Trivial - P5
Reporter: Jessica Sigafoos Assignee: Lucas Hrabovsky (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Sprint: Iteration Ragamuffin

 Description   

A customer submitted a quick bug report about Compass not being to reconnect to a cluster after the laptop it runs on enters sleep mode. After being woken up, the compass client needs to be restarted altogether, otherwise it gets "An error occurred while loading navigation: topology was destroyed".

I've raised this ticket as it is unclear if this should be a node.js improvement request ( related to NODE-845), or a compass improvement to handle unclean connection shutdowns better and discard any stale connection objects so a user can reconnect.



 Comments   
Comment by Lucas Hrabovsky (Inactive) [ 13/Nov/19 ]

I believe COMPASS-3943 fixes this problem

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