[SERVER-28151] Authentication database should be synced first during an initial sync Created: 01/Mar/17 Updated: 18/Feb/20 Resolved: 20/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.13, 3.2.7, 3.4.0 |
| Fix Version/s: | 3.4.14, 3.5.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ricardo Lorenzo | Assignee: | Jason Chan |
| Resolution: | Done | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||||||||||||||||||||
| Sprint: | Repl 2017-06-19, Repl 2017-07-10 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
During an initial sync it is not possible to connect and therefore, collect any monitoring data as per authentication issues. Please note that the initial sync for big volumes of data can take many days. It seems like the initial sync process should sync the admin database first. The code change occurred as part of However, at that code, the "fetching and creating collections" stage runs on a list where "admin" has been moved to the first element. But that database name gets inserted into a lexicographically sorted map, which is used to invoke the "initial sync cloning db" stage. "activities" sorts before "admin" so gets cloned first. |
| Comments |
| Comment by Githook User [ 27/Feb/18 ] |
|
Author: {'email': 'jason.chan@mongodb.com', 'name': 'Jason Chan'}Message: (cherry picked from commit 38218c1a0c2a15a05557df36794fe53618ca0db5) |
| Comment by Githook User [ 20/Jun/17 ] |
|
Author: {u'name': u'Jason Chan', u'email': u'jason.chan@mongodb.com'}Message: |