warning Listener::getElapsedTimeMillis returning 0ms

645 views
Skip to first unread message

Ofer Cohen

unread,
Jul 13, 2014, 6:16:31 PM7/13/14
to mongod...@googlegroups.com
Hey All
After upgrading to 2.6.3 from 2.4.10, we run mongo repair as follow:
sudo -u mongod mongod --dbpath /data/mongo --repair --repairpath /data/mongo/repair

And we get a lot of the next message:
2014-07-14T01:13:40.102+0300 [initandlisten] warning Listener::getElapsedTimeMillis returning 0ms

It seems that the repair process become really slow, probably because of those warnings. 
What are those warnings? How can we handle this?

Thanks, Ofer

Stephen Steneker

unread,
Jul 13, 2014, 10:24:27 PM7/13/14
to mongod...@googlegroups.com
Hi Ofer,

These are benign warnings and should not affect the speed of your repair process.

The warnings here are related to the elapsed timer which is normally started when mongod starts listening for incoming connections.

Since you are running mongod --repair, mongod will run the repair command to completion without starting to listen for incoming connections (so the elapsed time will always be 0ms). You'll see these warnings emitted periodically during the index build stage of the repair process as internal stats are updated; the warnings should ideally be suppressed in this context.

This is related to https://jira.mongodb.org/browse/SERVER-10502, which I see you've also commented on.

Regards,
Stephen

Ofer Cohen

unread,
Jul 14, 2014, 4:27:18 AM7/14/14
to mongod...@googlegroups.com
Stephen,
Thank you for clearing this issue.
Reply all
Reply to author
Forward
0 new messages