[SERVER-22347] Mongo shell replica set connections must use legacy readMode Created: 29/Jan/16 Updated: 08/Jan/24 Resolved: 17/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Shell |
| Affects Version/s: | 3.2.1 |
| Fix Version/s: | 3.2.9, 3.3.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Peter | Assignee: | Max Hirschhorn |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||
| Steps To Reproduce: | unknown |
||||||||||||||||||||
| Sprint: | Query 11 (03/14/16), Query 12 (04/04/16), Query 16 (06/24/16) | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Opened shell to create index. It was created successfully but on exit I received trace:
I've tried to reproduce this issue (dropped index, created again, ...), but failed. Still I wanted to show you this. |
| Comments |
| Comment by Githook User [ 29/Jul/16 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: Adds a Mongo.prototype.isReplicaSetConnection() method to connection (cherry picked from commit ef08c9cb7a040c36f367269edb1f144a063f1ee1) |
| Comment by Githook User [ 17/Jun/16 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: Adds a Mongo.prototype.isReplicaSetConnection() method to connection |
| Comment by David Storch [ 10/May/16 ] |
|
Our current plan is to fix this issue by forcing the shell to use legacy readMode when it is using a replica set connection. A more complete fix to the underlying issue is tracked in |
| Comment by Max Hirschhorn [ 18/Mar/16 ] |
|
Per discussion with jason.rassi, we've decided to make a change to DBClientReplicaSet so that it will issue the killCursors operation to the current primary of the replica set. As explained in an earlier comment, this approach is flawed because
However, it is consistent with our handling for getMore operations under the aforementioned scenarios. I've filed |