MongoDB3 + WiredTiger, Lot's of data loss after insert

pgoncalves

unread,

Apr 25, 2015, 8:28:46 AM4/25/15

to mongod...@googlegroups.com

Hi!

After we updated our mongodb from 2.6 to 3.0.2 with replica set, we noticed that a lot of new data has been loss.

After some debug, the data has been created, but after some time, it disappears. We suspected that has something related when mongo save the data on memory to disk. I could't find anything weird on my log files.

My config is:

Apr 24 11:41:09 mongo1 mongod.27017[26745]: [initandlisten] MongoDB starting : pid=26745 port=27017 dbpath=/dados/database/mongo 64-bit host=mongo1.xxx.com
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [initandlisten] db version v3.0.2
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [initandlisten] git version: 6201872043ecbbc0a4cc169b5482dcf385fc464f
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [initandlisten] OpenSSL version: OpenSSL 1.0.1c 10 May 2012
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [initandlisten] build info: Linux ip-10-111-179-219 3.2.0-36-virtual #57-Ubuntu SMP Tue Jan 8 22:04:49 UTC 2013 x86_64 BOOST_LIB_VERSION
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [initandlisten] allocator: tcmalloc
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [initandlisten] options: { config: "/etc/mongod.conf", net: { maxIncomingConnections: 500 }, replication: { replSet: "rs0" }, storage: {
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [initandlisten] waiting for connections on port 27017
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [ReplicationExecutor] New replica set config in use: { _id: "rs0", version: 6, members: [ { _id: 1, host: "mongo1.xxx.com:27017", ar
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [ReplicationExecutor] This node is mongo1.xxx.com:27017 in the config
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [ReplicationExecutor] transition to STARTUP2
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [ReplicationExecutor] Starting replication applier threads
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [ReplicationExecutor] transition to RECOVERING
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [ReplicationExecutor] Member mongo2.xxx.com:27017 is now in state PRIMARY
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [ReplicationExecutor] Member mongo3.xxx.com:27017 is now in state ARBITE
Apr 24 11:41:09 mongo1 mongod.27017[26745]: [ReplicationExecutor] transition to SECONDARY

Thank's

Pedro

Michael Shvartsman

unread,

Apr 25, 2015, 2:11:58 PM4/25/15

to mongod...@googlegroups.com

did you follow the upgrade procedure when switching to WT ? the old data is missing or newly inserted data ?

Asya Kamsky

unread,

Apr 25, 2015, 9:54:33 PM4/25/15

to mongodb-user

> we noticed that a lot of new data has been loss

How did you determine that?

What does "after some debug, the data has been created" mean?

Without giving us details of exact steps you took and what exactly was present and when it's hard to guess what might be going on in your system...

Asya

--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/5624bb7f-d9da-469d-95d1-c6f58e116def%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.