[SERVER-27676] Mongod is not able to restart after OOM kill Created: 13/Jan/17  Updated: 21/Feb/17  Resolved: 21/Feb/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dharshan Rangegowda Assignee: Kelsey Schubert
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-25145 During rollback (or w/minvalid invali... Closed
Related
related to SERVER-27149 Sync source selection doesn't conside... Closed
Operating System: ALL
Participants:

 Description   

The primary of a replica set of my shard was killed due to an OOM issue.
After that the server is not able to restart.

Version is 3.2.3 WiredTiger

2017-01-13T16:54:54.263+0000 I NETWORK  [initandlisten] connection accepted from 54.78.134.204:57528 #12 (11 connections now open)
2017-01-13T16:54:54.294+0000 I ASIO     [NetworkInterfaceASIO-BGSync-0] Successfully connected to:27017
2017-01-13T16:54:54.607+0000 I ACCESS   [conn12] Successfully authenticated as principal __system on local
2017-01-13T16:54:54.673+0000 I REPL     [rsBackgroundSync] Starting rollback due to OplogStartMissing: our last op time fetched: (term: 405, timestamp: Jan 13 16:09:01:3). source's GTE: (term: 406, ti
mestamp: Jan 13 16:09:01:3) hashes: (1329492769709081641/-2280498797367626345)
2017-01-13T16:54:54.673+0000 I -        [rsBackgroundSync] Fatal assertion 18750 UnrecoverableRollbackError: need to rollback, but in inconsistent state. minvalid: (term: 406, timestamp: Jan 13 16:13:
31:f) > our last optime: (term: 405, timestamp: Jan 13 16:09:01:3)
2017-01-13T16:54:54.673+0000 I -        [rsBackgroundSync]
 
***aborting after fassert() failure



 Comments   
Comment by Kelsey Schubert [ 21/Feb/17 ]

Hi dharshanr@scalegrid.net,

Thank you for the report. To resolve this issue, I would recommend performing on initial sync on the affected node.

This behavior is appears to be the result of SERVER-25145, therefore I would recommend upgrading to the latest version of MongoDB 3.2 (currently 3.2.12) to take advantage of this fix.

Kind regards,
Thomas

Generated at Thu Feb 08 04:15:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.