-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.1.0
-
Component/s: Performance, Storage
-
None
-
Fully Compatible
-
ALL
from SERVER-4880..
log message is:
Mon Feb 06 10:47:57 [journal] info journal _rotate called insider dbMutex - ok but should be somewhat rare
dwight says:
not sure why it is being called so much inside the lock. rotating in the lock would be a little bad as the world would be stopped while we unlink a 2GB file which might take a little time. but it's a rare event. the logging is happening before the if statement that checks if we are due to rotate - it's good it's before the rotate as rotates are so rare we'd never notice it otherwise. so we should analyze and see what is up but severity is not high
This may have caused a couple recent unit test breaks, in particular if it happens to occur while we are in an assert.soon(), since the default is that it only waits 30 seconds and the journal rotating can take a while as Dwight mentions above.
- is related to
-
SERVER-5072 Journal rotate with paranoid journaling caused abort
- Closed
-
SERVER-5076 Replication tests failing on drop_dups.js
- Closed
-
SERVER-4880 frequent journal warnings with Win2008
- Closed
-
SERVER-6229 not so rare verbose log message: info journal _rotate called inside dbMutex - ok but should be somewhat rare
- Closed