[SERVER-19024] WT_NOTFOUND exception when start mongodb from a snapshot Created: 18/Jun/15  Updated: 03/Aug/15  Resolved: 03/Aug/15

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

Type: Bug Priority: Major - P3
Reporter: Damon Assignee: Sam Kleinman (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi,
I start my mongodb server (version 3.0.4) with the snapshot data created by version 3.0.2.
I got this error log when I start:

2015-06-18T08:42:52.890+0000 I CONTROL ***** SERVER RESTARTED *****
2015-06-18T08:42:52.928+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3G,session_max=20000,eviction=(threads_max=4),statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2015-06-18T08:42:53.043+0000 I - [initandlisten] Assertion: 28595:-31803: WT_NOTFOUND: item not found
2015-06-18T08:42:53.043+0000 I STORAGE [initandlisten] exception in initAndListen: 28595 -31803: WT_NOTFOUND: item not found, terminating
2015-06-18T08:42:53.043+0000 I CONTROL [initandlisten] dbexit: rc: 100

I run the 3.0.2 with replication on EC2 Ubuntu 14.04, the snapshot was created daily.



 Comments   
Comment by Sam Kleinman (Inactive) [ 22/Jun/15 ]

Could you also provide the the output of ls -l for the database path?

Thank you,
Sam

Comment by Sam Kleinman (Inactive) [ 19/Jun/15 ]

Thanks for the upload, Just to clarify:

  • What kind of snapshot are you starting MongoDB from?
  • How did you produce these snapshots?

Cheers,
sam

Comment by Damon [ 19/Jun/15 ]

Hi, Sam
The WiredTiger.wt and WiredTiger.turtle had been uploaded.
I don't have the journal enabled on this instance.
And I got the same error when I run the mongod repair.


Regards,
Damon

Comment by Sam Kleinman (Inactive) [ 18/Jun/15 ]

Based on your report of this issue, we think that this may be a case of WT-1944. To help us confirm this diagnosis, could you please upload, using this upload portal a copy of your the WiredTiger.wt, and WiredTiger.turtle files from this instance, as well as the output of ls -l of the journal directory.

Sorry that you hit this issue, and thanks for your cooperation and patience.

Regards,
sam

Generated at Thu Feb 08 03:49:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.