- Core Server
- SERVER-980
single server durability
- Agile Board
- More Actions
-
Views
- XML
- Word
- Printable
Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.7.5
-
Component/s: None
-
Labels:None
-
Backport:No
-
# Replies:3
Issue Links
- is depended on by
-
SERVER-999
don't replay operations on network failure
-
- is related to
-
SERVER-1558
Documents should write checksum on write, verify checksum on read
-
- related to
-
SERVER-229
repairDatabase() does not handle infinite chaining loops
-
- Options
- Show All
- Show Open
Progress
|
|
Sub-Tasks
| 1. | check for consistency among durability files and data files | |
Open
|
Unassigned |
Activity
Ascending order - Click to sort in descending order
-
All
Comments
History
Activity
Hide
Permalink
Dwight Merriman
added a comment -
v1.8
Show
Dwight Merriman
added a comment - v1.8
Hide
Permalink
Karoly Negyesi
added a comment -
For those who do not follow https://github.com/mongodb/mongo/commits/master – there is a lot of progress on this even if there is no indication in the ticket.
Show
Karoly Negyesi
added a comment - For those who do not follow https://github.com/mongodb/mongo/commits/master – there is a lot of progress on this even if there is no indication in the ticket.
This is the one issue that prevents us from using MongoDB. Even if we felt safe using replication as a substitute for durability (which we don't), local development instances don't have that luxury. (Based on my past experience with MyIASM this becomes a frequent and recurring nightmare.)
I see that this is in progress, but couldn't find any more useful information than that. Is there an ETA on this?