[SERVER-10768] add proper support for SIGSTOP and SIGCONT (currently, on replica set primary can cause data loss) Created: 13/Sep/13 Updated: 10/Dec/14 Resolved: 25/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Yandong Mao | Assignee: | Matt Dannenberg |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | replication | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Distributor ID: Ubuntu |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Operating System: | Linux | ||||||||||||||||
| Steps To Reproduce: | Untar and put all files under MONGDB. Then execute MONGODB/my.py can
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
I am not sure if the following "problem" is assumed to be non-realistic, or is it a bug of MongoDB. The problem is that MongoDB may discard data that is replicated at a majority of servers. This is actually a terrible semantic (note that nothing crashes!). |
| Comments |
| Comment by Eric Milkie [ 25/Feb/14 ] |
|
Solved by |
| Comment by Eric Milkie [ 02/Dec/13 ] |
|
This issue can also affect nodes that pause for other reasons besides active process suspension. For example, if the machine is so busy that scheduling threads becomes very slow, this same situation can occur. |
| Comment by Matt Dannenberg [ 16/Sep/13 ] |
|
We were able to reproduce the issue thanks to your scripts. The issue pertains only to the use of SIGSTOP and SIGCONT, which is not supported. We believe we can add support for them for the next major release. |