[SERVER-4970] Better handling of not-master errors on fire and forget op codes Created: 14/Feb/12 Updated: 10/Dec/14 Resolved: 14/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Should kill the socket if we get a write an we haven't recently been master. Currently those writes are silently blackholed with no client notification. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 14/Jan/14 ] |
|
Those op codes are being deprecated |