[SERVER-44594] Mongo Upgrade to 3.4 taking more time on Secondary Created: 13/Nov/19 Updated: 07/Apr/23 Resolved: 20/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | 3.4.23 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Pratiksha Aggarwal | Assignee: | Carl Champain (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
While upgrading mongodb from mongo 3.2 - mongo 3.4 on amazon linux machine mongo upgrade process on secondary servers is taking 20mins on each node, while on primary and read replica node mongo upgrade process completed in 2min. The time took by upgrade process on secondary servers is 10mins while running transaction test and other 10min after transaction test was successful. What can be the possible reason for this time? The upgrade process was done on non-prod environment having half n hour of oplog window. On production environment on what basis can we predict the possible time for this process?? there can be the chances node going into recovery state on production environment if process takes an hour or so? |
| Comments |
| Comment by Carl Champain (Inactive) [ 20/Nov/19 ] | ||||||||||||||||||
|
Hi pragupta, Thanks for the report. Unfortunately, we won't be able to investigate this issue as a bug since 3.2 is already end-of-lifed, and 3.4 will be end-of-lifed in January 2020. I will now close this ticket. However, if you need further assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. Kind regards,
| ||||||||||||||||||
| Comment by Pratiksha Aggarwal [ 18/Nov/19 ] | ||||||||||||||||||
|
Please provide an update on this. | ||||||||||||||||||
| Comment by Pratiksha Aggarwal [ 15/Nov/19 ] | ||||||||||||||||||
|
Sample Logs while mongo upgrade on secondary server retrieving key from https://www.mongodb.org/static/pgp/server-3.4.asc
Running transaction | ||||||||||||||||||
| Comment by Pratiksha Aggarwal [ 13/Nov/19 ] | ||||||||||||||||||
|
We are using following sequence of commands for upgrading one node: #shutting down mongo node
#starting the mongo process
|