[SERVER-42050] problem upgrading from 3.6.10 to 4.0.9 Created: 02/Jul/19 Updated: 29/Jul/19 Resolved: 29/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lior Altarescu | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
centos 7.4 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
I was trying to upgrade a mongo replica set from version 3.2.12 to 4.0.9. i managed to upgrade all the server one at a time to 3.6.10 and had problems upgrading most of them to 4.0.9 . 2019-07-02T13:46:15.104+0000 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'. i though that the problem was in syncing so I downgraded it to 3.6.10 and made sure that there was no replication lag but when I tried to reinstall 4.0.9 i got the same error. I tried to start the mongo with --repair but it failed twice so my only option is to run inital sync on those problematic servers, one at a time . I would for some help |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 29/Jul/19 ] |
|
Closing due to lack of response. |
| Comment by Eric Sedor [ 16/Jul/19 ] |
|
Hi, We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide:
Thanks, |
| Comment by Eric Sedor [ 03/Jul/19 ] |
|
Hi lioral, Can you please get the deployment to MongoDB 3.6 and provide the exact steps taken from the start of the upgrade process until the first error? If there is a bug in the upgrade process, we will need to reproduce it. Importantly, please provide the output of commands run as part of the process. Thanks in advance, |