[SERVER-8412] repairDatabase: no Cloner, and use multi index builder Created: 30/Jan/13  Updated: 24/May/21  Resolved: 19/Feb/14

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 2.2.2, 2.3.2
Fix Version/s: 2.6.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Andre de Frere Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-12217 repairDatabase() floods the log with ... Closed
Related
related to SERVER-4726 Spurious warning: ClientCursor::yield... Closed
related to SERVER-13144 Size value is ignored when creating n... Closed
related to SERVER-13146 An _id index is built on the local.st... Closed
related to SERVER-4846 Rate limit ClientCursor::yield recurs... Closed
related to SERVER-56424 improve index build invariant message... Closed
Participants:

 Description   

The case of running the server with --repair causing spurious warnings of ClientCursor::yield appearing in the logs was resolved in SERVER-4726. The same warnings appear when using db.runCommand(

{ repairDatabase : 1 }

) from the shell (or it's helper db.repairDatabase()).

While the warnings are informational only, and the repairDatabase appears to be working correctly, they do cause excessive log size. Even rotated logs of this message could be filled with mostly useless information for a large enough database.



 Comments   
Comment by Githook User [ 21/Feb/14 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-8412 remove millis from explain reports before comparing
Branch: master
https://github.com/mongodb/mongo/commit/7729ff2bd1b14defafb22ad872af4d2ca3cf41db

Comment by Githook User [ 19/Feb/14 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-8412 clean up intmax_t
Branch: master
https://github.com/mongodb/mongo/commit/3269a5e07acfadd8788294a29a45c9aa4963213c

Comment by Githook User [ 19/Feb/14 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-8412: fix repair database failure cleanup
Branch: master
https://github.com/mongodb/mongo/commit/63ba64be33b2c0dab6fb9bbfbbd265f0afa7e788

Comment by Githook User [ 19/Feb/14 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-8412: fix ~IndexBuildBlock, make sure Context is correct
Branch: master
https://github.com/mongodb/mongo/commit/681c74b3f2de1e3665f953dfb07bcb25f48ecd2c

Comment by Chad Kreimendahl [ 14/Nov/13 ]

We're getting significant quantities of these while running a threaded process than does findAndModify. We're indexed properly and still seeing the issue create about 15M of logs per second. We have the logs currently set to quiet, which is apparently not enough. I find the logs useful and don't want to have to redirect them to devnull.

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