[SERVER-25210] Deadlock in Master/Slave Startup on Windows 2008 R2 Created: 22/Jul/16 Updated: 18/Apr/17 Resolved: 25/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.3.10 |
| Fix Version/s: | 3.2.13, 3.3.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Platforms 18 (08/05/16) |
| Participants: |
| Description |
|
Due to changes in FTDC, if time until the listener is started increases too much, master/slave replication will deadlock. The replication thread owns the database lock and waits for the listener to start. The main thread waits on the database thread before trying to start the listener. I have only seen this on Windows 2008R2+ Debug builds. Main Thread
Replication Thread
|
| Comments |
| Comment by Githook User [ 17/Apr/17 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: (cherry picked from commit 34aca01d24361e1a71c0888ba5bbce451df7ce05) |
| Comment by Githook User [ 25/Jul/16 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |