Reputation
366
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 5
Newest
 Yearling
Impact
~2k people reached

  • 0 posts edited
  • 0 helpful flags
  • 4 votes cast
Mar
15
comment Is there any simple way to see which mongodb indexes are being used?
What version of MongoDB are you using?
Mar
6
comment MongoDB high page faults every 15 minutes, delayed readers
What specific version of MongoDB are you using, and what sort of deployment do you have (standalone, replica set, sharded cluster)? I would review the mongod logs around the time you are seeing increased page faults. If there isn't anything obvious at the default log level I would increase the logging for query components if there isn't anything obvious). If slowdown is recurring every 15 minutes I'd suspect some sort of scheduled process running in your environment (eg. data ingestion or backup).
Mar
5
answered MongoDB sharding: mongos and config servers together?
Feb
19
awarded  Yearling
Feb
19
answered Taring mongodump database produce different checksum
Jan
26
comment Mistakenly upgraded MongoDB 2.6 straight to 3.2
You didn't confirm whether your dev server was a standalone without auth, which is a case where I can't think of any obvious errors in skipping 3.0 in the upgrade path to 3.2. If you have a more complex configuration (existing authentication data, replica set, or sharded cluster) you should follow the proper upgrade path as you will run into issues due to unexpected schema/metadata. The issues will likely manifest as invariant failures or assertions, so you could also check the logs on your dev server to see if anything appears to be amiss.
Jan
23
comment Mistakenly upgraded MongoDB 2.6 straight to 3.2
What sort of deployment did you upgrade, and what was your specific version of MongoDB 2.6.x? If you upgraded a standalone 2.6 server without authentication you might be OK (although this is not a tested upgrade path). Any more complex configuration (auth enabled, replica set, or sharded cluster) is likely to run into compatibility issues if you skip major version upgrade steps. Upgrade steps between major versions typically include updating authentication, oplog, and/or config server metadata so you definitely don't want to skip intermediate upgrades for a production deployment.
Nov
26
answered MongoDB replica set: Why the last remaining server becomes secondary?
Nov
26
awarded  Commentator
Nov
26
comment Edit edit /etc/mongo.conf and uncomment “auth=true”
Assuming a recent version of MongoDB installed via the official packages, the path to the config file should actually be /etc/mongod.conf (not /etc/mongo.conf. What version of MongoDB are you running? Is this a standalone server or part of a replica set? Note that authentication is enabled at the instance level, so disabling for localhost is also disabling auth for remote users. As at MongoDB 3.0, auth is disabled by default so if you haven't enabled it there should be no extra config required.
Nov
25
comment Edit edit /etc/mongo.conf and uncomment “auth=true”
What O/S are you using, and how are you starting/stopping MongoDB?
Nov
13
comment Enabling WiredTiger engine in MongoDB 3
What is your version of MongoDB as reported by: mongod --version?
Nov
11
awarded  Revival
Nov
11
comment Failed to authenticate with mechanism MONGODB-CR AuthenticationFailed MONGODB-CR credentials missing in the user document
This is a known issue. Robomongo 0.8.x is not fully compatible with MongoDB 3.0 and does not support the new default SCRAM-SHA-1 authentication: github.com/paralect/robomongo/issues/766. You may want to look for an alternative admin GUI: see mongodb-tools.com, "GUI" purpose category.
Nov
11
answered How to make mongodb database size bigger?
Apr
2
comment mongod: symbol lookup error: mongod: undefined symbol: _ZN5boost6detail13once_epoch_cvE
mongod --version should return a version number and git hash. If you installed a packaged version I think you shouldn't have to worry about libboost versions because should be part of the package deps. For supported Debian package see: Install MongoDB on Debian.
Aug
29
comment Recovering data from MongoDB raw files
You can't mix & match database files from different instances of MongoDB; doing so will almost certainly guarantee instability and potential data loss. What state are your data files in now? Were you able to recover from this issue?
Aug
22
comment How to check mongodb metadata's integrity?
The balancer will not run without all config servers available, so the sharded cluster metadata is implicitly read-only if one or more servers are unavailable. The error message is expected: you can stop of your remaining config servers, do the file copy, and then start up the config servers to resume normal operation. If you were doing planned maintenance you could stop the balancer before taking down a config server, which would try to complete any migration in progress before stopping the balancer.
Aug
21
awarded  Teacher
Aug
21
answered How to check mongodb metadata's integrity?