[SERVER-4619] Relinquishing primary should be done in write lock Created: 04/Jan/12 Updated: 11/Jul/16 Resolved: 07/Mar/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.5, 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Becoming primary is syncronized with a write lock, but there's a race condition in relinquish where you could change state to secondary, write ops could happen, then sockets were closed. |
| Comments |
| Comment by auto [ 17/Apr/12 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: Extend writelock during stepdown to include socket close |
| Comment by Richard Kreuter (Inactive) [ 07/Mar/12 ] |
|
Reopening because I'd like to ask for a backport to 2.0. |
| Comment by auto [ 13/Feb/12 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: Extend writelock during stepdown to include socket close |