Stupid simple request. I hesitate to call it a bug, but I also hesitate to call it an improvement.

I made a mistake deploying a Mongo node yesterday and it ran out of space while allocating its journal and local databases. Before I had realized it, I tried adding it to a replica set and got this errmsg in the set status:

syncThread: 13257 cmdline oplogsize (5210) different than existing (2046) see: http://dochub.mongodb.org/core/increase-oplog"

That confused the hell out of us. It makes sense once you understand, but it launched us down a red herring hole. It's just this replica set error message that was a little strange at first glance, because we thought we had misconfigured the oplog somehow. Again, I should have realized sooner that I had ran the box out of space, and I'm sure there's something in the log about it, but seeing that in replica set status was just confusing.

Does Mongo consider the local database stable even if it runs out of space while making it? Could it instead say, here, "I couldn't fully populate local, wtf?" or something? That's an old URI, too, which redirects elsewhere ... and the instructions aren't terribly appropriate for the situation at hand.

Like I said, stupidly trivial.