[SERVER-7444] Syncing to behavior is weird Created: 22/Oct/12 Updated: 10/Dec/14 Resolved: 02/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Grégoire Seux | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
In a replicaset with 4 nodes (and 1 arbiter) we had to resync completely 2 servers. The setup is the following : we stopped and clear data of B et D (A is the primary, D is perfectly up to date). D has started to replicate but the syncingTo flag show it uses A Replication is supposed to be selecting near instances, this seems broken. |
| Comments |
| Comment by Grégoire Seux [ 02/Apr/13 ] |
|
We moved to 2.2 since a few months, the issue has not happened any more. |
| Comment by Eliot Horowitz (Inactive) [ 01/Apr/13 ] |
|
There were cases where timing could be off in 2.0 at startup, causing a non-ideal node to be chosen. |
| Comment by Grégoire Seux [ 22/Oct/12 ] |
|
after a few minutes, D started to use C to sync. |