[SERVER-47617] On Sharding, WiredTiger error : calculated block checksum doesn't match expected checksum Created: 17/Apr/20 Updated: 23/Apr/20 Resolved: 23/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 4.2.0, 4.2.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | jongsun moon | Assignee: | Carl Champain (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | repair, repairDatabase | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||
| Operating System: | ALL | ||
| Steps To Reproduce: |
|
||
| Participants: |
| Description |
|
For the service, we make database at once. The build database process is When shard collections, we met log message below. We used mongoDB 4.2.0 and 4.2.5. and got simular error message. Servers are one mongos, three mongo config servers for one replication set and three shard servers each for the first replication set. Could you give us an advice what we should check for it. |
| Comments |
| Comment by Carl Champain (Inactive) [ 23/Apr/20 ] |
|
I'm sorry to hear that --repair didn't work! I'm going to close this ticket now. Kind regards, |
| Comment by jongsun moon [ 23/Apr/20 ] |
|
Oh... I see. We ran --repair on the server that contains corrupted data. But it gave us same error message. Anyway, as you pointed out, it seems to be happened because of physical problem. With new physical server, it works well until now. Thank you for your help. |
| Comment by Carl Champain (Inactive) [ 22/Apr/20 ] |
|
Then you should run --repair on the server that contains corrupted data. |
| Comment by jongsun moon [ 22/Apr/20 ] |
|
We have three shard cluster. Each shard cluster has only one server as primary server of replication set.(no slave server.) |
| Comment by Carl Champain (Inactive) [ 21/Apr/20 ] |
|
Are the shard servers part of the same replica set? If so, we recommend a clean resync from an unaffected node. |
| Comment by jongsun moon [ 21/Apr/20 ] |
|
Hi Carl Champain, Thank you for your kindly comment. I have a question. Below is what we did. I will let you know the #3 result. Regards, |
| Comment by Carl Champain (Inactive) [ 20/Apr/20 ] |
|
This error message leads us to suspect some form of physical corruption. Please make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. The ideal resolution is to perform a clean resync from an unaffected node. You can also try mongod --repair using the latest version of MongoDB. In the event that a --repair operation is unsuccessful, then please also provide:
Kind regards, |