diff options
author | Kaloian Manassiev <kaloian.manassiev@mongodb.com> | 2014-10-27 16:25:02 -0400 |
---|---|---|
committer | Kaloian Manassiev <kaloian.manassiev@mongodb.com> | 2014-10-28 12:02:49 -0400 |
commit | b9ebf15a7afa4f8db780b6ba06fc796c1ee2816e (patch) | |
tree | 0489dbc53d8ed858ce580490893443391a2bc7ba /src/mongo/db/storage/README.md | |
parent | ca1338ccef5375923da9938e84dc0f7fe393af2c (diff) | |
download | mongo-b9ebf15a7afa4f8db780b6ba06fc796c1ee2816e.tar.gz |
SERVER-15262 Remove syncDataAndTruncateJournal from the public interface
Diffstat (limited to 'src/mongo/db/storage/README.md')
-rw-r--r-- | src/mongo/db/storage/README.md | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/src/mongo/db/storage/README.md b/src/mongo/db/storage/README.md index f256e23a104..ceab8e8b4d8 100644 --- a/src/mongo/db/storage/README.md +++ b/src/mongo/db/storage/README.md @@ -137,20 +137,6 @@ acts on that information. RecoveryUnit ------------ -**Q**: Should RecoveryUnit::syncDataAndTruncateJournal be static or in a different class? I am not -sure why they need to effect the instance of RecoveryUnit? -**A**: These methods are effectively static in that they will only modify global -state. However, these methods are virtual, which is why we aren’t declaring them -as static. That being said, we will likely remove this methods from the public -API and move them into our mmapv1 storage engine implementation in the near -future. - -**Q**: RecoveryUnit::syncDataAndTruncateJournal sounds like a checkpoint. That can -take a long time, is this expected to block until that is done? -**A**: Yes. Note that this is only called externally when we drop a database or when -the user explicitly requests a sync via the fsync command. We may rename this -method as part of a naming sweep. - **Q**: As documented I don’t understand the point of the RecoverUnit::endUnitOfWork nesting behavior. Can you explain where it is used or will be used? **A**: The RecoveryUnit interface and the mmapv1 (current mongodb storage engine) |