[SERVER-3740] Supplying --fastsync with --master silently locks server Created: 01/Sep/11 Updated: 06/Dec/22 Resolved: 08/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Lee Johnson | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux-x86_64 |
||
| Assigned Teams: |
Replication
|
| Operating System: | ALL |
| Participants: |
| Description |
|
mongod will start with --fastsync and --master, despite these options being a contradiction. The server will then silently not accept any connections - the logs show it having stopped at "no journal files present, no recovery needed". Supplying --fastsync and --master should error out with a message that these arguments are mutually exclusive. db version v2.0.0-rc0, pdfile version 4.5 ==== Example ==== /tmp/mongodb-linux-x86_64-2.0.0-rc0/bin > pgrep -lf mongo /tmp/mongodb-linux-x86_64-2.0.0-rc0/bin > cat /tmp/md.log Thu Sep 1 14:59:34 [initandlisten] journal dir=/tmp/journal /tmp/mongodb-linux-x86_64-2.0.0-rc0/bin > ./mongo /tmp/mongodb-linux-x86_64-2.0.0-rc0/bin > pkill mongo /tmp/mongodb-linux-x86_64-2.0.0-rc0/bin > ./mongod --master --dbpath /tmp/ --fork --logpath /tmp/md.log /tmp/mongodb-linux-x86_64-2.0.0-rc0/bin > cat /tmp/md.log Thu Sep 1 15:00:00 [initandlisten] journal dir=/tmp/journal /tmp/mongodb-linux-x86_64-2.0.0-rc0/bin > ./mongo |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 08/Feb/18 ] |
|
As of 3.6, master/slave is deprecated, so we won't be fixing this. |
| Comment by Eliot Horowitz (Inactive) [ 17/Jan/13 ] |
|
We should only allow --fastsync with --slave. |