Shulou(Shulou.com)06/01 Report--

1. Db.serverStatus () to see the sharding performance information.

Db.serverStatus (). Connections; shard to check the number of client connections. The connection between mongod and mongos is a persistent connection.

"connections": {

"current": 737,-current number of active connections. Current number of active connections to the server

"available": 82-remaining idle connections. Number of connections remaining available

}

Db.serverStatus (). Mem to view sharded memory

"mem": {

"bits": 64,-64-bit machine

"resident": 18363-- takes up the amount of physical memory.

"virtual": 478810-- amount of virtual memory occupied

"supported": true,-- whether extended memory is supported

"mapped": 233311,-the size of the data file mapped to memory is very close to the size of all your databases.

"mappedWithJournal": 466622

Note: "virtual minus mapped is large. Could indicate a memory leak"

}

2. Mongod and mongos login methods. Pay attention to the mongo client login management to manage the database.

/ usr/local/bin/mongo localhost:port

/ usr/local/bin/mongo 10.20.25.48:10001

/ usr/local/bin/mongo 10.20.25.48:27017/admin-uroot-p123456

3. Check the average distribution of each shard in the cluster

Sh.status ()

The results are as follows

Dbname.tablename

Shard key: {"_ id": "hashed"}

Chunks:

S2 16

S1 13

S3 14

Too many chunks to print, use verbose if you want to force print

4. View the performance of sharded mongo

Mongostat-h 10.20.25.48-- port 27017-uroot-p123456-n 100 20

Mongostat is a status detection tool that comes with mongdb and is used on the command line. It gets the current running state of mongodb at regular intervals and outputs it. If you find that the database suddenly slows down or has other problems, your first-hand operation should consider using mongostat to check the status of mongo.

Mongostat command format, of course, you can also add parameters:

In the first example, mongostat will return every second of the data for 20 seconds. The local host interface port 27017 running on the mongod instance where mongostat collects data. All of the following calls produce the same behavior:

Mongostat-rowcount 20 1

Mongostat-rowcount 20

Mongostat-N 20 1

Mongostat-N 20

In the following example, mongostat returns data every 5 minutes (300s) as long as the program is running. The local host interface port 27017 running on the mongod instance where mongostat collects data. The following two calls produce the same behavior.

Mongostat-rowcount 0 300

Mongostat-N 0 300

Mongostat 300

In the following example, mongostat returns data for an hour (12 times) every 5 minutes. The local host interface port 27017 running on the mongod instance where mongostat collects data. The following two calls produce the same behavior.

Mongostat-rowcount 12 300

Mongostat-N 12 300

In many cases, using-discover will help the state of the entire set of machines, providing a more complete snapshot. If you connect to port 27017 running on the local machine on a chip cluster during Mongos, you can return statistics from all members of the cluster in the following form:

Mongostat-discover

The above reference document: http://cn.docs.mongodb.org/manual/reference/mongostat/

Mainly explain the significance of each column in detail (you can also refer to. / mongostat-- help)

Insert: number of inserts in a second

Query: the number of queries in a second

Update: number of updates in a second

Delete: number of deletions in a second

Ten simple queries may be faster than one complex query, so the size of the number doesn't make much sense.

But at least you can know if the query is being processed and whether it is being inserted.

If it is slave, the value is usually preceded by a *, which represents a replicate operation.

Getmore: getmore operation of cursor when querying

It is of little use

Www.2cto.com

Command: the number of commands executed in a second

For example, bulk insertion is only considered to be a command. It doesn't mean much.

If it is slave, two values, local | replicated, will be displayed. By comparing these two values, you may be able to see some problems.

Flushes: the number of flush in a second

It's usually 0, or 1, and by calculating the interval between two 1s, you can get a rough idea of how long it takes to flush.

Flush costs a lot, and if you have frequent flush, you may have to find out why.

Mapped:

Vsize:

Res:

This is the same as what you can see with top, mapped, vsize generally will not change much, res will rise slowly, if res often suddenly drop, check to see if there are other programs eating memory.

Faults:

Don't be frightened by the name. Under great pressure, the value is often not zero. If it is often not 0, it is time to add memory.

Locked:

MongoDB is a read-write lock, which refers to the percentage of time that the write lock resides. If this number is too large (often more than 10%), something is wrong.

Idx miss:

Very important parameters, normally, all queries should pass the index, that is, idx miss is 0. If the value here is large, is there a lack of index?

Qr | qw: queue lengths for clients waiting (read | write)

Ar | aw: active clients (read | write)

If these two values are large, then DB is blocked and DB is not as fast as the request.

See if there are expensive slow queries. If everything is normal and the load is really heavy, you need to add the machine.

NetIn: network traffic in-bits

NetOut: network traffic out-bits

Network bandwidth pressure, general MongoDB, the network will not become a bottleneck

Conn: number of open connections

MongoDB creates a thread for each connection, and thread creation and release also have overhead. Try not to let this number be too large.

Repl: current status of the server

M-master

SEC-secondary

REC-recovering

UNK-unknown

SLV-slave

Time: current Tim

If you execute the mongostat command in the cmd window under windows, it may be because the window is too narrow, and the monitoring data are arranged in disorder and hinder vision, you can output the results to a txt file, and then go to view this file, the method is some twists and turns .

E:\ mongodb-win32-x86_64-2.2.1\ bin\ mongostat-n 2 > E:\ test.txt

Print 2 lines of results to test.txt in the follower directory of the E disk.

5. View the IP sorting of mongo TCP connections

Netstat-ant | awk'{print $5}'| awk-F:'{print $1}'| sort | uniq-c | sort-rn

6. Mongo simple multipart backup

/ home/mongodb/bin/mongodump-h292.168.0.15 authenticationDatabase admin 50001-u username-p 123456-- authenticationDatabase admin-d dbname-o / home/data/dbbackup/

7. Db.status () to view the sharding cluster status

8. To be continued

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.