[SERVER-28054] WiredTiger data corruption in 3.4.x Created: 18/Feb/17 Updated: 27/Oct/23 Resolved: 29/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.0, 3.4.1, 3.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Rostyslav Mykhajliw | Assignee: | David Hows |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
|||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | |||||||||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||||||||
| Steps To Reproduce: |
then restart instance. |
|||||||||||||||||||||||||||||
| Participants: |
| Description |
|
MongoDB with WiredTiger corrupts storage in case of instance restart I'm running mongo db m4.large instances on AWS, region: us-west-2 (Oregon) |
| Comments |
| Comment by David Hows [ 29/Mar/17 ] | ||||||||||||
|
Thanks Rostyslav, I'm marking this issue as resolved. | ||||||||||||
| Comment by Rostyslav Mykhajliw [ 28/Mar/17 ] | ||||||||||||
|
issue is resolved. trouble was on my side in deploy script commands order - in some cases mount of filesystem was executed after mongodb install and run. That led to copying working mongodb files and data corruption. | ||||||||||||
| Comment by David Hows [ 27/Mar/17 ] | ||||||||||||
|
necromant2005@gmail.com, can you elaborate on the problem you have seen/solved? If there is still an underlying issue with MongoDB or WiredTiger, it is definitely something I would want to get to the bottom of. Thanks | ||||||||||||
| Comment by Rostyslav Mykhajliw [ 27/Mar/17 ] | ||||||||||||
|
Trouble was in setup receipt - solved with update. | ||||||||||||
| Comment by David Hows [ 27/Mar/17 ] | ||||||||||||
|
necromant2005@gmail.com, can you review my process and confirm if any of the steps I have taken differ from yours? At this stage I have been unable to reproduce the issue as you have described. | ||||||||||||
| Comment by David Hows [ 27/Mar/17 ] | ||||||||||||
|
I've attempted to reproduce this and was not able to make MongoDB fail in the same manner. Process I used:
Blob
I don't have the config used by Rostyslav Mykhajliw for his MongoDB instance, I have just used the default found in the MongoDB d | ||||||||||||
| Comment by Alexander Gorrod [ 23/Mar/17 ] | ||||||||||||
|
david.hows Please try reproducing this failure using exactly the steps outlined by the user. | ||||||||||||
| Comment by Rostyslav Mykhajliw [ 28/Feb/17 ] | ||||||||||||
|
There's no issues on Ubuntu 16.04. I suppose the issue somehow related to system.d, because that's native replacement for init.d | ||||||||||||
| Comment by Rostyslav Mykhajliw [ 28/Feb/17 ] | ||||||||||||
|
1. ami-a49b1bc4 (ubuntu 16.10) 4. Go to AWS console and click on "restart instance" link | ||||||||||||
| Comment by Alexander Gorrod [ 22/Feb/17 ] | ||||||||||||
|
necromant2005@gmail.com We are having difficulty reproducing the behavior you report, and it is not obvious how the symptoms could occur from inspecting and reasoning about the code. Could you please let us know:
| ||||||||||||
| Comment by Rostyslav Mykhajliw [ 21/Feb/17 ] | ||||||||||||
|
Hi Michael, It may be because I'm using ubuntu 16.10 Cheers, | ||||||||||||
| Comment by Michael Cahill (Inactive) [ 21/Feb/17 ] | ||||||||||||
|
necromant2005@gmail.com, thanks for this report, the WiredTiger metadata file you uploaded has been truncated. Can you create a tarball of the dbpath before restarting the instance (i.e., while it is running)? It would be good to compare that to the files after restart to narrow down when the truncation happens. One further question: if you run with journal enabled (the default setting), do you still see this issue? | ||||||||||||
| Comment by Rostyslav Mykhajliw [ 18/Feb/17 ] | ||||||||||||
|
syslog |