[SERVER-12910] clear thread-local shardconnection cache in mongos after every operation Created: 26/Feb/14 Updated: 11/Jul/16 Resolved: 04/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
See server.cpp::process(). Currently we clear the shardconnection cache after every request that gets a response. This is now too conservative, since write ops are upconverted to use batch write commands and do not require the same connections stay open to enforce GLE. We should clear the thead-local cache after every operation. Impact is small in a cluster which isn't doing up/downconversion, but we want to be consistent and easy to reason about. |
| Comments |
| Comment by Githook User [ 04/Mar/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |