Draft for release summary box:
ISSUE SUMMARY
Query points provided in the legacy coordinate pair format using 2dsphere indexes are not correctly checked for whether they are in bounds. This affects both the geoNear command using the spherical option and the $nearSphere operator. Such out of bounds coordinates can crash the server.
USER IMPACT
A primary crash will lead to a fail-over in a replica set. If the queries continue to be sent to current primary (and cause a crash), this will affect quorum and potentially render the replica set inoperable.
WORKAROUNDS
Removing the spherical option for the query avoids the crash but will assume a flat surface instead of a spherical one. For small regions, the difference may be acceptable as a workaround.
RESOLUTION
The query now correctly checks for the bounds and aborts with an error, instead of crashing the server.
AFFECTED VERSIONS
Version 2.6.0 is affected by this bug.
PATCHES
The patch is included in the 2.6.1 production release.
Original description
use pymongo 2.7 client, when I runCommand query geoNear, the server crash.
I know that maybe the issue of the pymongo client, but the server crash when the coordinates is wrong.
- is duplicated by
-
SERVER-13751 mongod crash on geo nearSphere query
- Closed