MongoDB 命令（二）

删除一个集合我们有下面2中方式
1.db.test.drop()
2.db.runCommamd({"drop":"test"})
那runCommamd究竟有多少命令可以执行呢？
使用db.listCommands()可以查看到所有可执行的命令。
如：
distinct: read-lock
  { distinct : 'collection name' , key : 'a.b' , query : {} }

driverOIDTest: no-lock
  no help defined

drop: write-lock
  drop a collection
  {drop : <collectionName>}

dropDatabase: write-lock
  drop (delete) this database

dropIndexes: write-lock
  drop indexes for a collection

emptycapped: write-lock
  no help defined

eval: no-lock
  Evaluate javascript at the server.
  http://www.mongodb.org/display/DOCS/Server-side+Code+Execution

features: no-lock
  return build level feature settings

filemd5: read-lock
   example: { filemd5 : ObjectId(aaaaaaa) , root : "fs" }

findAndModify: write-lock
  { findAndModify: "collection", query: {processed:false}, update: {$set: {proce
ssed:true}}, new: true}
  { findAndModify: "collection", query: {processed:false}, remove: true, sort: {
priority:-1}}
  Either update or remove is required, all other fields have default values.
  Output is in the "value" field


forcedead: write-lock adminOnly  slaveOk
  internal

forceerror: no-lock
  for testing purposes only.  forces a user assertion exception

fsync: write-lock adminOnly  slaveOk
  http://www.mongodb.org/display/DOCS/fsync+Command

geoNear: read-lock
  http://www.mongodb.org/display/DOCS/Geospatial+Indexing#GeospatialIndexing-geo
NearCommand

geoSearch: read-lock
  no help defined

geoWalk: read-lock
  no help defined

getCmdLineOpts: no-lock adminOnly  slaveOk
  get argv

getLastError: no-lock
  return error status of the last operation on this connection
  options:
    { fsync:true } - fsync before returning, or wait for journal commit if runni
ng with --journal
    { j:true } - wait for journal commit if running with --journal
    { w:n } - await replication to n servers (including self) before returning
    { wtimeout:m} - timeout for w in m milliseconds

getParameter: no-lock adminOnly  slaveOk
  get administrative option(s)
  example:
  { getParameter:1, notablescan:1 }
  supported so far:
    quiet
    notablescan
    logLevel
    syncdelay
  { getParameter:'*' } to get everything


getPrevError: no-lock
  check for errors since last reseterror commandcal

getShardMap: no-lock adminOnly  slaveOk
  internal

getShardVersion: no-lock adminOnly  slaveOk
   example: { getShardVersion : 'alleyinsider.foo'  }

getnonce: no-lock
  internal

getoptime: no-lock
  internal

godinsert: write-lock
  internal. for testing only.

group: read-lock
  http://www.mongodb.org/display/DOCS/Aggregation

handshake: no-lock
  internal

isMaster: no-lock
  Check if this server is primary for a replica pair/set; also if it is --master
or --slave in simple master/slave setups.
  { isMaster : 1 }

isinitialsynccomplete: no-lock
  no help defined

journalLatencyTest: no-lock adminOnly  slaveOk
  test how long to write and fsync to a test file in the journal/ directory

listCommands: no-lock
  get a list of all db commands

listDatabases: read-lock adminOnly  slaveOk
  list databases on this server

logRotate: no-lock adminOnly  slaveOk
  no help defined

logout: no-lock
  de-authenticate

mapReduce: no-lock
  Run a map/reduce operation on the server.
  Note this is used for aggregation, not querying, in MongoDB.
  http://www.mongodb.org/display/DOCS/MapReduce

mapreduce.shardedfinish: no-lock
  no help defined

medianKey: read-lock
  Internal command.
  example: { medianKey:"blog.posts", keyPattern:{x:1}, min:{x:10}, max:{x:55} }
  NOTE: This command may take a while to run

moveChunk: no-lock adminOnly  slaveOk
  should not be calling this directly


negotiatemaster: write-lock adminOnly  slaveOk
  no help defined

ping: no-lock
  a way to check that the server is alive. responds immediately even if server i
s in a db lock.

profile: write-lock
  enable or disable performance profiling
  { profile : <n> }
  0=off 1=log slow ops 2=log all
  -1 to get current values
  http://www.mongodb.org/display/DOCS/Database+Profiler

reIndex: write-lock
  re-index a collection

renameCollection: write-lock adminOnly  slaveOk
   example: { renameCollection: foo.a, to: bar.b }

repairDatabase: write-lock
  repair database.  also compacts. note: slow.

replSetElect: no-lock adminOnly  slaveOk
  internal

replSetFreeze: no-lock adminOnly  slaveOk
  { replSetFreeze : <seconds> }'freeze' state of member to the extent we can do
that.  What this really means is that
  this node will not attempt to become primary until the time period specified e
xpires.
  You can call again with {replSetFreeze:0} to unfreeze sooner.
  A process restart unfreezes the member also.

  http://www.mongodb.org/display/DOCS/Replica+Set+Commands

replSetFresh: no-lock adminOnly  slaveOk
  internal

replSetGetRBID: no-lock adminOnly  slaveOk
  internal

replSetGetStatus: no-lock adminOnly  slaveOk
  Report status of a replica set from the POV of this server
  { replSetGetStatus : 1 }
  http://www.mongodb.org/display/DOCS/Replica+Set+Commands

replSetHeartbeat: no-lock
  internal

replSetInitiate: no-lock adminOnly  slaveOk
  Initiate/christen a replica set.
  http://www.mongodb.org/display/DOCS/Replica+Set+Commands

replSetReconfig: no-lock adminOnly  slaveOk
  Adjust configuration of a replica set
  { replSetReconfig : config_object }
  http://www.mongodb.org/display/DOCS/Replica+Set+Commands

replSetStepDown: no-lock adminOnly  slaveOk
  { replSetStepDown : <seconds> }
  Step down as primary.  Will not try to reelect self for the specified time per
iod (1 minute if no numeric secs value specified).
  (If another member with same priority takes over in the meantime, it will stay
primary.)
  http://www.mongodb.org/display/DOCS/Replica+Set+Commands

replSetTest: no-lock adminOnly  slaveOk
  Just for regression tests.


replacePeer: write-lock adminOnly  slaveOk
  replace a node in a replica pair

resetError: no-lock
  reset error state (used with getpreverror)

resync: write-lock adminOnly  slaveOk
  resync (from scratch) an out of date replica slave.
  http://www.mongodb.org/display/DOCS/Master+Slave

serverStatus: no-lock
  returns lots of administrative server statistics

setParameter: no-lock adminOnly  slaveOk
  set administrative option(s)
说几个最常用的命令。
buildInfo  {"buildInfo":1}
返回MongoDB服务器的版本号和主机的操作系统
collStats {"collStats":collection}
返回指定集合的统计信息，包括数据大小，已分配的存储空间和索引的大小。
distinct
{"distinct":collection,"key":key,"query":query}
列出指定集合中满足查询条件的文档的指定键的所有不同值
drop {"drop":collection}
删除集合的所有数据
dropDatabase {"dropDatabase":1}
删除当前数据库的所有数据。
dropIndexes {"dropIndexes":collection,"index":name}
删除集合里面名称为name的索引，如果名称为"*"，则删除全部索引。
getLastError
查看对本集合执行的最后一次操作的错误信息或者其他状态信息。在W台服务器复制集合的最后操作之前，这个命令会阻塞（超时的毫秒数到了）。
isMaster
检查本服务器是主服务器还是从服务器
listCommands {"listCommands":1}
返回所有可以再服务器上运行的命令及相关信息。
listDatabases {"listDatabases":1}
列出服务器上所有的数据库
ping {"ping":1}
检查服务器链接是否正常
renameCollection  {"renameCollections":a,"to":b}
将集合a重命名为b，其中a和b都必须是完整的集合命名空间
repairDatebase {"repairDatabase":1}
修复并压缩当前数据库。
serverStatus {"serverStatus":1}
返回这台服务器的管理统计信息