-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
None
-
ALL
Hi support,
we find our queris use the error index by slow logs :
//2021-04-23T00:34:31.408+0800 I COMMAND [conn1525857] command region_governance.area_info command: count { count: "area_info", query: { cityCode: { $in: [ "021" ] }, templateGuid: { $in: [ "T_536751178985275392" ] }, businessType: { $in: [ 1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31 ] }, areaStatus: { $in: [ 5 ] }, isDelete: 0 }, $db: "region_governance", $clusterTime: { clusterTime: Timestamp(1619109260, 35), signature: { hash: BinData(0, 89550148FC85585EE9B2ACA9D09E724805A8AEE0), keyId: 6918301327185412097 } }, lsid: { id: UUID("eb4fc071-0048-4cd7-8064-6cb49f5a5fa8") }, $readPreference: { mode: "secondary" } } planSummary: IXSCAN { cityCode: 1, templateType: 1, businessType: 1, operateType: 1, operateUnit: 1, 1000000002: 1 } keysExamined:55686 docsExamined:55670 numYields:438 reslen:170 locks:{ Global: { acquireCount: { r: 439 } }, Database: { acquireCount: { r: 439 } }, Collection: { acquireCount: { r: 439 } } } storage:{} protocol:op_msg 9648ms
1.we execute the query on mono shell and get the correct explain which on 'index' file,
2.we hint the error index and get the slow log's explain which on 'index1' file,
3. this is a replset , other secondary don't have the issue.
- related to
-
SERVER-56298 error explain for one secondary
- Closed