[SERVER-18751] "Fatal Assertion" Crashed 1 Members In 3 Replica Set Shard Environment Created: 30/May/15 Updated: 14/Apr/16 Resolved: 19/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Replication |
| Affects Version/s: | 2.6.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ovidiu Tatar | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Linux | |||||||||||||||||||||
| Steps To Reproduce: | I tried to fix issue by using different repair path and start replica for synchronisation in this case get the next message:
finally after allocating a part of the datafile the recovery process start from begins again and again |
|||||||||||||||||||||
| Participants: |
| Description |
|
I'm facing the following issue after MongoDB does not shutdown cleanly. I tried to run --repair parameter but recovery process exit with the same error message.
|
| Comments |
| Comment by Ramon Fernandez Marina [ 19/Jun/15 ] |
|
ovidiu.tatar@3ziele.de, it is highly unlikely that clock synchronization was the source of the issue here, and I'd still encourage you to check for file corruption and storage health on your deployment to avoid future issues in this area. I'm going to close this for now, let us know if the issue reappears. Regards, |
| Comment by Ramon Fernandez Marina [ 18/Jun/15 ] |
|
ovidiu.tatar@3ziele.de, glad to hear you worked around the issue. I'm investigating whether clock skew could be responsible for this and whether there's room for improvement if it is. Regards, |
| Comment by Ovidiu Tatar [ 04/Jun/15 ] |
|
Solved issue by synchronise time an all instances via $ sudo ntpdate pool.ntp.org |
| Comment by Ovidiu Tatar [ 30/May/15 ] |
|
unfortunately after recover some data I got the next error message for this command I used a new --dbpath /home/shard1-tmp/ but the sync failed 015-05-30T10:25:26.598-0700 [FileAllocator] done allocating datafile /home/shard1-tmp/test.1, size: 2047MB, took 0.046 secs , name: "id", ns: "test.oplog.rs" } any ideas how to fix issue ? |
| Comment by Ramon Fernandez Marina [ 30/May/15 ] |
|
Looks like the unclean shutdown may have corrupted the data files for the local database. I would suggest you resync this member from the primary, which should solve your problem. Can you please try the resync procedure and report back? Thanks, |