[SERVER-39099] drop_connections_replSet.js intermittent failure Created: 18/Jan/19  Updated: 29/Oct/23  Resolved: 30/Jan/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.1.7
Fix Version/s: 4.1.8

Type: Bug Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-36416 Add a dropConnections administrative ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-01-28, Repl 2019-02-11
Participants:
Linked BF Score: 35

 Description   

Seen rarely, the first assert in this block fails, because the number of available connections to the removed secondary is 0, not 1:

assert.eq(1, primary.adminCommand({connPoolStats: 1}).hosts[memberHost].available);
assert.commandWorked(primary.adminCommand({dropConnections: 1, hostAndPort: [memberHost]}));
assert.eq(0, primary.adminCommand({connPoolStats: 1}).hosts[memberHost].available);



 Comments   
Comment by Githook User [ 30/Jan/19 ]

Author:

{'username': 'ajdavis', 'email': 'jesse@mongodb.com', 'name': 'A. Jesse Jiryu Davis'}

Message: SERVER-39099 Make dropConnections test robust
Branch: master
https://github.com/mongodb/mongo/commit/d46942c358f42379d2c4596403dbec8522b1e755

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