Details
-
Bug
-
Resolution: Fixed
-
Major
-
4.5.1, 4.6.2
-
None
-
Triaged
-
Unknown
Description
As seen in CBSE-3977, after indexer restart memdb was unable to open the db and load the snapshot.
2017-07-13T09:34:03.603-04:00 [Error] MemDBSlice::loadSnapshot Slice Id 0, IndexInstId 14566572925156851741 failed to load snapshot /mnt/local/couchbase/index/@2i/2F_14566572925156851741_0.index/snapshot.2017-06-29.182124.192 error(open /mnt/local/couchbase/index/@2i/2F_14566572925156851741_0.index/snapshot.2017-06-29.182124.192/data/files.json: no such file or directory).
|
The system had run out of file descriptors and most likely this resulted in some of the persisted snapshots to be in inconsistent state.
This leads to the following issue:
memdb.loadSnapshot is able to identify the error but doesn't take any action leading to database being open in inconsistent manner and further db operations resulting in panic.
A better option would be to try to open the database from previous on disk snapshots and if it doesn't work out, reset to 0 so that there is no inconsistent state.
Attachments
Issue Links
- relates to
-
MB-25256 MOI - improve dealing with inconsistent disk snapshot
- Closed