[SERVER-78753] setFeatureCompatibilityVersion times out waiting for replication Created: 07/Jul/23  Updated: 02/Feb/24  Resolved: 02/Feb/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Adi Zaimi Assignee: Adi Zaimi
Resolution: Gone away Votes: 0
Labels: sharding-nyc-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Operating System: ALL
Sprint: Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11, Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5
Participants:

 Description   

This started occuring for test  transaction_too_large_for_cache.js in suite fcv_upgrade_downgrade_sharded_collections_jscore_passthrough after we enabled `num_rs_nodes_per_shard: 2`.

The error is as follows:

2023-07-06T21:33:34.069Z assert: command failed: {
        "ok" : 0,        "errmsg" : "waiting for replication timed out; Error details: { wtimeout: true, writeConcern: { w: \"majority\", wtimeout: 60000, provenance: \"clientSupplied\" } }",
        "code" : 64,
        "codeName" : "WriteConcernFailed",
        "$clusterTime" : {
                "clusterTime" : Timestamp(1688679210, 1),
                "signature" : {
                        "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
                        "keyId" : NumberLong(0)
                }
        },
        "operationTime" : Timestamp(1688679033, 3)
 } with original command request: {
        "setFeatureCompatibilityVersion" : "7.0",
        "$clusterTime" : {
                "clusterTime" : Timestamp(1688679032, 2),
                "signature" : {
                        "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
                        "keyId" : NumberLong(0)
                }
        }
 } 

In the following evg run:
https://parsley.mongodb.com/resmoke/a937e625225912ff2b6f4dc02e96c042/all?bookmarks=0,211984&shareLine=53199

 

Previous evg runs also exhibited same error, for the same test:

https://parsley.mongodb.com/resmoke/2438fb36237d75b62048170c4ba92249/test/176f5def62d9fce9bf0901f2f146a65c?bookmarks=0,43874,316477&shareLine=0
https://parsley.mongodb.com/resmoke/26cb00282d025dbba2df25fb57fc9d40/test/176f56b9dcfaf54748a0dec6d0a0ab81?bookmarks=0,26,87&shareLine=0

 


Generated at Thu Feb 08 06:39:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.