2017-08-18T03:06:22.147+0800 E STORAGE [initandlisten] WiredTiger (-31802) [1502996782:147192][11674:0x7f081e961cc0], file:sizeStorer.wt, WT_SESSION.open_cursor: unable to read root page from file:sizeStorer.wt: WT_ERROR: non-specific WiredTiger error2017-08-18T03:06:22.147+0800 I - [initandlisten] Invariant failure: ret resulted in status UnknownError: -31802: WT_ERROR: non-specific WiredTiger error at src/mongo/db/storage/wiredtiger/wiredtiger_size_storer.cpp 672017-08-18T03:06:22.152+0800 I CONTROL [initandlisten]
Hi
unable to read root page from file:sizeStorer.wt
That error could mean either:
sizeStorer.wt
file is corrupt, orWiredTiger.wt
file is corrupt, ordbpath
of MongoDB.At this point, the quickest way to get your deployment in working order is to restore from a recent backup. Please also ensure that the recommendations in the Production Notes are followed to minimize any potential issues in the future.
You mentioned that power was cut in your deployment. However, this alone is usually not sufficient to corrupt WiredTiger files. Could you elaborate further on what happened? This corruption is typically caused by failures in the storage hardware (e.g. corrupt disk, hardware issues, etc.)
Best regards,
Kevin