-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
Fully Compatible
-
ALL
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
FeatureFlagUtil.isPresentAndEnabledOnAllNodes() (added in SERVER-125913) opens a direct connection to every replica set member with new Mongo(member.name). member.name comes from replSetGetStatus and is always the MongoRPC address.
On gRPC variants (e.g. rhel8-arm64-debug-aubsan-compile-grpc, run with --shellGRPC), enable_grpc_on_connect.js makes every new Mongo() use gRPC unless the caller passes {gRPC: false}. The shell therefore tries to open a gRPC channel to the MongoRPC port, which has no gRPC listener, and fails:
`The test then exits with code -3.
Failing task: rhel8_arm64_debug_aubsan_compile_grpc_sharding_jscore_passthrough_execution_control_with_prioritization_2, revision 8fbe07a4.`
Fix. Pass {gRPC: false} for these direct per-node connections in feature_flag_util.js. The other helpers that connect directly to mongod nodes already do this (fixture_helpers.js, discover_topology.js, shardingtest.js). The fix also covers the other callers of isPresentAndEnabledOnAllNodes in clustered_collection_bounded_scan_common.js.
Verification. I ran or_use_clustered_collection.js locally against sharding_jscore_passthrough with the CI gRPC flags: --shellGRPC, TLS, --additionalFeatureFlags featureFlagGRPC. Without the fix, the same HostUnreachable failure. With the fix, all 11 tests pass.
- is related to
-
SERVER-125913 Support building non-contiguous recordid ranges from queries on clustered indexes
-
- Closed
-