[SERVER-33611] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361 Created: 02/Mar/18 Updated: 02/Apr/18 Resolved: 02/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Storage |
| Affects Version/s: | 3.4.9 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Karthick [X] | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux RHEL |
||
| Participants: |
| Description |
|
Hi Team, We are facing an problem and would request your help to resolve the issue: Requirement : We have an replica set with three members in Prodcution and Net file back up snap shots are taken at regular intervals. We wanted this net files backed up for the entire db folders in the db path and wanted to copy it across to a stand alone machine where mongo is set up, to be used for Please note that We had taken these net file back ups from Secondary nodes while its up and running. The replica set is configured to be journal enabled. Problem : Tried the following steps : 1. Copied the backed up Net file Back Up as is to the – db path folder to the Standalone machine when the mongod instance is down. MONGO SHELL LOG: about to fork child process, waiting until server is ready for connections. 4. Remove the mongod.lock and started once again and it says the error MONGO SHELL LOG : [ppoker@in1cod2vir235 db]$ mongod --config "/home/release/release_independent/dbdata/coredfs/conf/coredfs.conf" 5. Could see the following lines from the log files : MONGO SHELL LOG:
6. The config details used for start up in the stand alone Mongo instance are as follows :
7. Repair of the mongod was not possible as it was journal enabled .. Tried with --no journal during start up but resulted in the same Check Point Error as mentioned above. I have the following questions : 1. How do we resolve this . Is this approach of net file back up from a secondary in a replica to a stand alone is fine. Am i missing any thing here. Humbly request your kind inputs here. Thanks in advance. |
| Comments |
| Comment by Ramon Fernandez Marina [ 02/Mar/18 ] |
|
Thanks for your report Karthick. This is expected behavior: copying the files from dbpath while mongod is running doesn't guarantee you'll get a consistent dataset. Please take a look at backup methods you can use; for example, you can shut down the secondary you want to copy the files from. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Regards, |