[SERVER-19073] MongoDB WiredTiger 3.0.2 is not backward compatible with data files created with 3.0.4 Created: 22/Jun/15 Updated: 24/Jun/15 Resolved: 23/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Steve Briskin (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | To reproduce:
|
||||||||
| Participants: | |||||||||
| Description |
|
Starting a wiredTiger mongod <=3.0.2 against data files files created with 3.0.4 results in a fatal assertion.
|
| Comments |
| Comment by Daniel Pasette (Inactive) [ 23/Jun/15 ] |
|
We can't automatically fix this after the fact. Users who create their WiredTiger deployment with server versions >=3.0.3 will not be able to downgrade to 3.0.2 or below. If users must downgrade, it should be possible to work around the presence of the unknown configuration setting by editing the WiredTiger.basecfg found in the dbpath and removing the line with file_manager=(close_idle_time=100000). |
| Comment by Daniel Pasette (Inactive) [ 23/Jun/15 ] |
|
This was inadvertently broken with the backport of |