-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.4.4
-
Component/s: Geo
-
ALL
-
Refactor geospatial $geoNear/$nearSphere/geoNear command code to use the standard query framework and geometry covering changes from SERVER-5800.
This refactor affects $geoNear in both 2D and 2DSphere indexes - no behavior change is intended.
A side effect of this change is that progressive $geoNear sort is supported, and the full search does not have to be performed at once.
Original Description:
It appears that a long-running 2d-indexed geo query on a replica set with authentication will only yield when it finds matching documents. If the gap during which it does not find documents is long enough, it will become unresponsive, miss its heartbeats, and the secondaries assume it is down. Eventually they will cause an election and fail over the primary.
During this time, the primary is fully aware of this and prints
Fri Jun 21 17:17:13.307 [rsHealthPoll] replset info capslock.local:27018 thinks that we are down
- is duplicated by
-
SERVER-9200 Cannot Connect During Long Query
- Closed
-
SERVER-5236 $near query should return results progressively
- Closed
-
SERVER-3933 Allowing a greater number of results when using $near which perhaps allow distance and sorting / ordering by distance as an operator
- Closed
- is related to
-
SERVER-9983 Authenticating as internal user shouldn't require a database lock
- Closed
-
SERVER-84819 geo performance issue in 2.7.7
- Closed
- related to
-
SERVER-10047 2dsphere $near does not yield
- Closed
-
SERVER-44223 Complete TODO listed in SERVER-9986
- Closed
-
SERVER-5800 Refactor 2D $geoWithin into new query framework (expression index)
- Closed