[SERVER-9853] Ghostsyncing does not retry after a network failure Created: 03/Jun/13 Updated: 11/Jul/16 Resolved: 10/Jun/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.3, 2.5.0 |
| Fix Version/s: | 2.4.5, 2.5.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| 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 |
|
It needs to try to reconnect immediately. This logic will be better solved by |
| Comments |
| Comment by auto [ 20/Jun/13 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by auto [ 20/Jun/13 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by auto [ 20/Jun/13 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: Without this fix, depending on exact timing of upstream socket failure, you could lose Note that this only affects chaining; nonchaining updates are already retrying when a socket Conflicts: src/mongo/db/repl/rs_sync.cpp |
| Comment by auto [ 10/Jun/13 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: Without this fix, depending on exact timing of upstream socket failure, you could lose Note that this only affects chaining; nonchaining updates are already retrying when a socket |