[SERVER-5685] Have multiple threads applying oplog ops Created: 23/Apr/12 Updated: 09/Jul/13 Resolved: 21/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.2 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Comments |
| Comment by auto [ 22/Jun/12 ] |
|
Author: {u'date': u'2012-06-22T14:23:44-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: This was causing delays when waiting on writes on the primary since |
| Comment by auto [ 20/Jun/12 ] |
|
Author: {u'date': u'2012-06-20T09:03:54-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: |
| Comment by auto [ 19/Jun/12 ] |
|
Author: {u'date': u'2012-06-19T12:07:58-07:00', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: By not checking the return status, it was possible to have a replcation oplog batch |
| Comment by auto [ 19/Jun/12 ] |
|
Author: {u'date': u'2012-06-19T06:50:18-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: On a secondary, ops are now pulled off the network in one thread and |
| Comment by auto [ 19/Jun/12 ] |
|
Author: {u'date': u'2012-06-19T06:49:05-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: |
| Comment by auto [ 13/Jun/12 ] |
|
Author: {u'date': u'2012-06-13T14:49:53-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: |
| Comment by auto [ 13/Jun/12 ] |
|
Author: {u'date': u'2012-06-13T12:43:37-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: |
| Comment by auto [ 13/Jun/12 ] |
|
Author: {u'date': u'2012-06-13T08:01:37-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message:
|
| Comment by auto [ 13/Jun/12 ] |
|
Author: {u'date': u'2012-06-13T09:57:43-07:00', u'email': u'milkie@10gen.com', u'name': u'Eric Milkie'}Message: |
| Comment by auto [ 06/Jun/12 ] |
|
Author: {u'login': u'dwight', u'name': u'Dwight', u'email': u'dwight@10gen.com'}Message: |
| Comment by auto [ 01/Jun/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: prefetch code for support of |
| Comment by Kristina Chodorow (Inactive) [ 29/May/12 ] |
|
@Scott: the primary is no longer keeping track of sync by where the secondary has getMore'd to. The secondary keeps a second connection open, which it updates whenever lastOpTimeWritten is updated. |
| Comment by Scott Hernandez (Inactive) [ 09/May/12 ] |
|
How will this interact with oplog queries upstream? When do the queries get sent for more, before or during the creation of the batches? These questions of course matter for the replication state from the primaries point of view. |
| Comment by Eric Milkie [ 09/May/12 ] |
|
Summary of implementation plan: |