[SERVER-54052] Call to setFeatureCompatibilityVersion sometimes hangs when upgrading from 4.2 to 4.4 on sharded cluster Created: 26/Jan/21 Updated: 11/Feb/21 Resolved: 11/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Simon Bernier St-Pierre | Assignee: | Dmitry Agranat |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | 1. Create a mongo 4.2 sharded cluster |
| Participants: |
| Description |
|
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. |
| Comments |
| Comment by Dmitry Agranat [ 11/Feb/21 ] |
|
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, |
| Comment by Dmitry Agranat [ 28/Jan/21 ] |
|
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, |