[SERVER-25420] Is it safe to replace wiredtiger directory with latest wiredtiger-2.8.1 in mongodb-3.2.3? Created: 03/Aug/16 Updated: 15/Nov/21 Resolved: 03/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Zhang Youdong | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We are using mongodb-3.2.3(wiredtiger-2.7.1) and have modified some code based on our own requirements, now the latest version is 3.2.8 and fix many issues in wiredtiger like I want to know if it's safe to just update wiredtiger to latest 2.8.0 in mongodb 3.2.3? To my knowledge,mongod and wiredtiger are decoupled modules, it's safe to just upgrade wiredtiger version. Thanks for help. |
| Comments |
| Comment by Ramon Fernandez Marina [ 03/Aug/16 ] |
|
Hi zyd_com. The configuration you describe is unsupported and untested, so I would recommend against it. There's extensive customization in WiredTiger for the bits that ship with MongoDB. However, the upcoming MongoDB 3.2.9 release does contain a lot of the improvements scheduled for WiredTiger 2.8.1. MongoDB 3.2.9 is currently scheduled for next week (a 3.2.9-rc0 release candidate was created yesterday, but we had some issues with publishing so we're working on 3.2.9-rc1 to fix those – but you can see the planned changes in the source tree). I'm going to resolve this ticket. If you decide to test a 3.2.9 release candidate an find any issues feel free to open new tickets. Regards, |