[SERVER-10976] releaseConnectionsAfterResponse not respected by mongod mapreduce Created: 30/Sep/13  Updated: 10/Dec/14  Resolved: 01/May/14

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

Type: Bug Priority: Minor - P4
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Won't Fix Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File RCAR_mr_test.js    
Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

Mongod also uses the sharded connection pool when finishing a sharded mapreduce. If there are many incoming mongos connections for sharded mapreduce, it would be more efficient if used outgoing connections to other shards were returned to the pool after use (since GLE does not apply here).



 Comments   
Comment by Greg Studer [ 01/May/14 ]

This is a minor issue that will be superseded by further work on connection pooling.

Comment by Daniel Pasette (Inactive) [ 26/Jan/14 ]

We know the issue here, and don't believe it will actually impact production deployments.

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