OPERATIONAL DEFECT DATABASE
...
...
I've noticed that after upgrading a 4.2 sharded cluster to 4.4, the call to setFeatureCompatibilityVersion sometimes hangs. I've set a 10 minute timeout on the command and it is reached quite often. I can't reproduce this problem all the time. It will usually take about 10s for the command to run normally. I've had cases where it reaches the 10 minutes timeout and other cases where it takes much longer than 10s but still completes within the 10 minute timeout. The logs for mongos don't seem to indicate any problem. I'm using the latest versions of 4.2 and 4.4.
dmitry.agranat commented on Thu, 11 Feb 2021 09:43:19 +0000: Hi simon.bernier-st-pierre@ubisoft.com, We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, Dima dmitry.agranat commented on Thu, 28 Jan 2021 09:56:42 +0000: Hi simon.bernier-st-pierre@ubisoft.com, Would you please archive (tar or zip) the mongod.log files covering the incident and the $dbpath/diagnostic.data directory (the contents are described here) from the mongoS the command was issued as well as from all members of the primary shard and upload them to this support uploader location? Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Also, how many shards and chunks do you have in your cluster? Thanks, Dima
1. Create a mongo 4.2 sharded cluster 2. Upgrade the binaries to 4.4 3. Call setFeatureCompatibilityVersion on mongos
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
