-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.6.8
-
Component/s: Querying
-
None
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
when we update our mongodb from 3.4 to 3.6, some query plans take much more time than 3.4. some aggregation took 10 seconds in 3.6 while 100ms in 3.4.
explain(): "rejectedPlans" is empty in 3.4, but it contains one element in 3.6.
I found the variable "_candidates" in "multi_plan.cpp" are inappropriate. In this case, it may take much more time to evaluate these candidate plans.
- duplicates
-
SERVER-36393 Contained $or pushdown optimization can cause internalQueryEnumerationMaxOrSolutions to be exceeded
-
- Backlog
-