[SERVER-23714] Operation failure due to mmap() failure on primary causes inconsistency on primary and crashes of secondaries Created: 14/Apr/16  Updated: 06/Dec/22  Resolved: 09/Feb/17

Status: Closed
Project: Core Server
Component/s: MMAPv1
Affects Version/s: 2.6.5, 2.6.12
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Issue Links:
Related
related to SERVER-23715 Failure of mmap() call should termina... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Comments   
Comment by Bruce Lucas (Inactive) [ 26/Apr/16 ]

They are different problems, but if SERVER-23715 were fixed then this problem would not need to be fixed because this problem (interpreted narrowly) occurs when the server continues operating after a mongod failure.

However possibly there are other errors that could occur at the same spot, between unindexing a record to move it and reindexing it, that would cause the same problem; it may be worth checking whether that is the case.

Comment by Ian Whalen (Inactive) [ 25/Apr/16 ]

bruce.lucas can you clarify whether this is a dupe or not of SERVER-23715?

Comment by Bruce Lucas (Inactive) [ 14/Apr/16 ]

This issue does not appear to reproduce on 3.0 or 3.2, presumably because they have correct rollback of failed operations.

Generated at Thu Feb 08 04:04:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.