-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.1.7
-
Component/s: Querying
-
None
-
ALL
-
Running a $geoNear on a 2d index with a readConcern majority will fail with the following error:
m31000| 2015-09-02T11:50:41.740-0400 I COMMAND [conn1] command test.geo2 command: count { count: "geo2", query: { loc: { $geoNear: [ 50.0, 50.0 ] } }, fields: {}, limit: 100.0, readConcern: { level: "majority" } } ntoreturn:1 ntoskip:0 keyUpdates:0 writeConflicts:0 numYields:0 reslen:242 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_command 1204ms { "waitedMS" : NumberLong(230), "ok" : 0, "errmsg" : "error processing query: ns=test.geo2Tree: GEONEAR field=loc maxdist=1.79769e+308 isNearSphere=0\nSort: {}\nProj: {}\n planner returned error: unable to find index for $geoNear query", "code" : 2 }
- duplicates
-
SERVER-20260 New indexes should bump their Collection's minimum SnapshotName
- Closed