[SERVER-13306] replicasets/tags.js times out and fails occasionally on Windows Created: 21/Mar/14  Updated: 11/Jul/16  Resolved: 23/Mar/14

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.6.0-rc2

Type: Task Priority: Minor - P4
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Happens because mongobridge is not passing back connection failures and keeps retrying forever if the target server is down. This causes the original call to time-out.

This happens at shutdown time and only on Windows, when we cannot find the server's shutdown event and backing-off to the old method of connecting and invoking the shutdown command.

2014-03-20T21:48:04.172+0000 kill_wrapper OpenEvent failed to open event to the process 4236. It has likely died already or server is running an older version. Attempting to shutdown through admin command.
 m31006| 2014-03-20T21:48:04.172+0000 connection accepted from 127.0.0.1:60115 #6 (1 connection now open)
2014-03-20 17:48:05 EDT	
 m31006| 2014-03-20T21:48:05.173+0000 warning: Failed to connect to 10.9.180.27:31001, reason: errno:10061 No connection could be made because the target machine actively refused it.
2014-03-20 17:48:06 EDT	
 m31006| 2014-03-20T21:48:06.673+0000 warning: Failed to connect to 10.9.180.27:31001, reason: errno:10061 No connection could be made because the target machine actively refused it.
2014-03-20 17:48:08 EDT	
 m31006| 2014-03-20T21:48:08.173+0000 warning: Failed to connect to 10.9.180.27:31001, reason: errno:10061 No connection could be made because the target machine actively refused it.
2014-03-20 17:48:09 EDT	
 m31006| 2014-03-20T21:48:09.673+0000 warning: Failed to connect to 10.9.180.27:31001, reason: errno:10061 No connection could be made because the target machine actively refused it.
2014-03-20 17:48:11 EDT	
 m31006| 2014-03-20T21:48:11.173+0000 warning: Failed to connect to 10.9.180.27:31001, reason: errno:10061 No connection could be made because the target machine actively refused it.
2014-03-20 17:48:12 EDT	
 m31006| 2014-03-20T21:48:12.673+0000 warning: Failed to connect to 10.9.180.27:31001, reason: errno:10061 No connection could be made because the target machine actively refused it.
2014-03-20 17:48:14 EDT	
 m31006| 2014-03-20T21:48:14.173+0000 warning: Failed to connect to 10.9.180.27:31001, reason: errno:10061 No connection could be made because the target machine actively refused it.
2014-03-20 17:48:15 EDT	
 m31006| 2014-03-20T21:48:15.673+0000 warning: Failed to connect to 10.9.180.27:31001, reason: errno:10061 No connection could be made because the target machine actively refused it.



 Comments   
Comment by Githook User [ 24/Mar/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-13306 mongobridge should not try forever to connect to dead
destinations.

The connect timeout is set to 15 seconds of retrying, after which the
connection to the client will be terminated.

Also added some extra logging and diagnostics so it is easier to analyse
test failures in the future.
Branch: v2.6
https://github.com/mongodb/mongo/commit/444bb62c24786a65334f4be214d1154dde00c71b

Comment by Githook User [ 23/Mar/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-13306 mongobridge should not try forever to connect to dead
destinations.

The connect timeout is set to 15 seconds of retrying, after which the
connection to the client will be terminated.

Also added some extra logging and diagnostics so it is easier to analyse
test failures in the future.
Branch: master
https://github.com/mongodb/mongo/commit/bfebf440342a2266f8febec161334a700dc713af

Generated at Thu Feb 08 03:31:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.