[SERVER-4758] OplogReader has no socket timeout Created: 24/Jan/12 Updated: 06/Feb/17 Resolved: 06/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.6, 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
It really should to prevent the sync thread from hanging if a server goes down. |
| Comments |
| Comment by Eric Milkie [ 06/Feb/17 ] |
|
Hi michaelbrenden |
| Comment by Michael Brenden [ 06/Feb/17 ] |
|
Now that it's become 6 seconds oplog timeout, a new problem is unwanted oplog timeout when scanning full, huge oplog. https://jira.mongodb.org/browse/SERVER-19605 |
| Comment by Eric Milkie [ 05/Jun/12 ] |
|
Lukas: The situation described in |
| Comment by Lukas Krecan [ 05/Jun/12 ] |
|
Sorry for late reaction, but does it really mean that if I have setup described in |
| Comment by auto [ 16/May/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: backport - fix handling of socket timeouts on Windows |
| Comment by auto [ 15/May/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by auto [ 15/May/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by auto [ 24/Feb/12 ] |
|
Author: {u'login': u'milkie', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: |
| Comment by Eric Milkie [ 23/Feb/12 ] |
|
If you run individual js files (or subsets of the js files) with "smoke --small-oplog", you can't reproduce the failure. Also, if you reorder the rename#.js files by changing their filenames, the failure case seems to go away or change in odd ways. http://buildbot.mongodb.org:8081/builders/Linux%2064-bit%20DEBUG/builds/793/steps/test_1/logs/stdio |
| Comment by Eric Milkie [ 23/Feb/12 ] |
|
I believe this commit broke the smalloplog test suite. |
| Comment by auto [ 21/Feb/12 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: Add oplog reader timeout |