For replica sets the above would need to be done on every replica node, plus on each node every single oplog entry that refers this database would have to be somehow invalidated or rewritten, and then if it's a sharded cluster, one also needs to add these changes to every shard if the DB is sharded, plus the config servers have all the shard metadata in terms of namespaces with their full names. This is just to accomplish a rename of a single database in a standalone mongod instance. contents of system.namespaces and system.indexes (or their equivalents in the future).internal unique names of each collection and index.

every single numbered file for the collection.In MMAPv1 files, the namespace (e.g.: llection) that describes every single collection and index includes the database name, so to rename a set of database files, every single namespace string would have to be rewritten. ns file size for new databases.Unfortunately, this is not an simple feature for us to implement due to the way that database metadata is stored in the original (default) storage engine. Any query that would do a table scan fails. # Enable the HTTP interface (Defaults to port 28017). # Inspect all client data for validity on receipt (useful for # Enables periodic logging of CPU utilization and I/O wait # E.g., if the parent directory isn't mutable by the MongoDB user. # need to create and set permissions for this directory manually. # Note: if you run MongoDB as a non-root user (recommended) you may I commented out bind_ip and uncommented port. I was able to connect using the following nf file. You need to edit your /etc/nf file's bind_ip variable to include the IP of the computer you're using, or eliminate it altogether. It is a better idea to add more IP addresses than to open up your system to everything. Note: Commenting out bind_ip can make your system vulnerable to security flaws.

Mongodb with robomongo tutorial