[SERVER-3899] Initial sync should check occaisonally if it can stop and become secondary Created: 19/Sep/11 Updated: 11/Jul/16 Resolved: 19/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | 2.0.2, 2.1.0 |
| 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 |
|
It used to run out of cursor before, but now does not. |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 07/Aug/12 ] |
|
It won't become a secondary until the data is properly synced. It is unlikely that you saw this same issue in 2.0.6. |
| Comment by Vinaykr [ 07/Aug/12 ] |
|
I had the same issue in 2.0.6 but when I restarted the server, it became secondary immediately. How do I know the data is properly synced? Also, is this supposed to be still happening on 2.0.6? |
| Comment by Kristina Chodorow (Inactive) [ 24/Oct/11 ] |
|
Backported. |
| Comment by auto [ 24/Oct/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: stop initial sync once minvalid is reached |
| Comment by Kristina Chodorow (Inactive) [ 18/Oct/11 ] |
|
This is mostly a cosmetic problem, although slaveOkay queries will not be routed to recovering nodes. Ways to get a recovering node into SECONDARY state:
|
| Comment by auto [ 19/Sep/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: stop initial sync once minvalid is reached |