[SERVER-2562] monogod --oplogSize flag is ignored on Windows Created: 16/Feb/11 Updated: 12/Jul/16 Resolved: 22/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 1.6.5 |
| Fix Version/s: | 1.7.6 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Ed Rooth | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 64-bit |
||
| Operating System: | Windows |
| Participants: |
| Description |
|
Tried starting up mongo with: mongod --oplogSize 5000 However the oplog never grows beyond about 1GB. Sun Feb 13 18:45:13 MongoDB starting : pid=824 port=27017 dbpath=d:\DB\Mongo\data 64-bit |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 22/Feb/11 ] |
|
This has been fixed in 1.7.x. |
| Comment by Scott Hernandez (Inactive) [ 22/Feb/11 ] |
|
I have been able to reproduce this, and others on the list have reported this for 1.6.5 as well; it is not reproducible in 1.7.5 (with rs.initiate()). I get various error using different --oplogSize values: Mon Feb 21 17:38:53 [initandlisten] cmdline oplogsize (1120) different than existing (1024) see: http://dochub.mongodb.org/core/increase-oplog Mon Feb 21 17:42:07 [initandlisten] creating replication oplog of size: 1024MB... (use --oplogSize to change) |
| Comment by Adrian Hills [ 21/Feb/11 ] |
|
I've hit the same problem, with 1.6.5 on Windows 7 64 Bit. Full args: Log file shows: If i use --oplogSize 6144 mongod crashes and log file shows: |
| Comment by Ed Rooth [ 16/Feb/11 ] |
|
Hi, we are using Windows 2008 Server. This is the config file as we had it when starting up the server: dbpath = d:\DB\Mongo\data |
| Comment by Customer Support rpc-user [ 16/Feb/11 ] |
|
Ed, What other options are set in the config file or command line? Also, what flavor of Win7 are you using? |