-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: Storage, WiredTiger
-
None
-
Fully Compatible
-
ALL
2015-03-23T20:41:02.102Z I CONTROL [serviceShutdown] got SERVICE_CONTROL_STOP request from Windows Service Control Manager, will terminate after current cmd ends 2015-03-23T20:41:02.106Z I STORAGE [conn398] got request after shutdown() ... 2015-03-23T20:41:59.157Z I STORAGE [conn223] got request after shutdown() 2015-03-23T20:42:12.065Z I CONTROL ***** SERVER RESTARTED ***** 2015-03-23T20:42:12.071Z I CONTROL Trying to start Windows service 'MongoDB' 2015-03-23T20:42:12.071Z I STORAGE Service running 2015-03-23T20:42:12.072Z W - [initandlisten] Detected unclean shutdown - D:\Mongo\data\db\mongod.lock is not empty. 2015-03-23T20:42:12.072Z W STORAGE [initandlisten] Recovering data from the last clean checkpoint. 2015-03-23T20:42:12.072Z I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=63G,session_max=20000,eviction=(threads_max=4),statistics=(fast),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0), 2015-03-23T20:42:12.094Z I - [initandlisten] Fatal assertion 28548 NoSuchKey Unable to find metadata for table:survey/collection-9-5755622992935745294 2015-03-23T20:42:12.094Z I - [initandlisten] ***aborting after fassert() failure
- mongod received SERVICE_CONTROL_STOP request
- it takes a while to shut down (maybe doing a lengthy checkpoint?)
- Windows gets impatient after 60 seconds and abruptly terminates mongod
- recovery fails on subsequent startup
- is related to
-
SERVER-17152 WiredTiger file corrupted during power cycle test
- Closed
- related to
-
SERVER-17820 Windows service stop can lead to mongod abrupt termination due to long shutdown time
- Closed