[SERVER-1122] Starting slave with --fastsync doesn't seem to work Created: 14/May/10 Updated: 12/Jul/16 Resolved: 14/May/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Erik Jones | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Running 1.4.0 |
||
| Participants: |
| Description |
|
So, I'm not totally sure this is a bug, I just know this doesn't seem to be working. I created a snapshot of a master with ~250G of data and rsync'd that to the slave host. When starting the slave with --auth --slave --source 10.6.64.206 --fastsync I get this in the log after the normal startup stuff: Fri May 14 12:28:28 repl: from host:10.6.64.206 but then no notices about objects being replicated and db.printSlaveReplicationInfo() from the console gives: > db.printSlaveReplicationInfo(); At Kristina's recommendation in #mongodb I removed --auth from both the master and slave and retried, same results. Can one of you guys ping me in either #mongodb or #ey-weshop with perhaps looking to take a direct look at this with me? This is fairly time critical. |
| Comments |
| Comment by Erik Jones [ 14/May/10 ] |
|
Okay, scratch this. After leaving the slave up and running for a few it eventually started replicating. Restarted both servers with --auth and the slave without --fastsync and all looks good. |
| Comment by Eliot Horowitz (Inactive) [ 14/May/10 ] |
|
Can you try with 1.4.2 and -vvv |