Rechercher dans le manuel MySQL
15.16.3 InnoDB Standard Monitor and Lock Monitor Output
The Lock Monitor is the same as the Standard Monitor except that it includes additional lock information. Enabling either monitor for periodic output turns on the same output stream, but the stream includes extra information if the Lock Monitor is enabled. For example, if you enable the Standard Monitor and Lock Monitor, that turns on a single output stream. The stream includes extra lock information until you disable the Lock Monitor.
Standard Monitor output is limited to 1MB when produced using the
SHOW ENGINE INNODB
STATUS
statement. This limit does not apply to output
written to server standard error output
(stderr
).
Example Standard Monitor output:
- *************************** 1. row ***************************
- Name:
- =====================================
- =====================================
- -----------------
- BACKGROUND THREAD
- -----------------
- srv_master_thread loops: 15 srv_active, 0 srv_shutdown, 1122 srv_idle
- ----------
- SEMAPHORES
- ----------
- OS WAIT ARRAY INFO: reservation count 24
- OS WAIT ARRAY INFO: signal count 24
- RW-shared spins 4, rounds 8, OS waits 4
- RW-excl spins 2, rounds 60, OS waits 2
- RW-sx spins 0, rounds 0, OS waits 0
- Spin rounds per wait: 2.00 RW-shared, 30.00 RW-excl, 0.00 RW-sx
- ------------------------
- LATEST FOREIGN KEY ERROR
- ------------------------
- ,
- ------------
- ------------
- Trx id counter 7748
- Purge done for trx's n:o < 7747 undo n:o < 0 state: running but idle
- History list length 19
- LIST OF TRANSACTIONS FOR EACH SESSION:
- ---TRANSACTION 421764459790000, not started
- 0 lock struct(s), heap size 1136, 0 row lock(s)
- ---TRANSACTION 7747, ACTIVE 23 sec starting index read
- mysql tables in use 1, locked 1
- LOCK WAIT 2 lock struct(s), heap size 1136, 1 row lock(s)
- MySQL thread id 9, OS thread handle 140286987249408, query id 51 localhost root updating
- DELETE FROM t WHERE i = 1
- ------- TRX HAS BEEN WAITING 23 SEC FOR THIS LOCK TO BE GRANTED:
- RECORD LOCKS space id 4 page no 4 n bits 72 index GEN_CLUST_INDEX of table `test`.`t`
- trx id 7747 lock_mode X waiting
- Record lock, heap no 3 PHYSICAL RECORD: n_fields 4; compact format; info bits 0
- 0: len 6; hex 000000000202; asc ;;
- 1: len 6; hex 000000001e41; asc A;;
- 2: len 7; hex 820000008b0110; asc ;;
- 3: len 4; hex 80000001; asc ;;
- ------------------
- TABLE LOCK table `test`.`t` trx id 7747 lock mode IX
- RECORD LOCKS space id 4 page no 4 n bits 72 index GEN_CLUST_INDEX of table `test`.`t`
- trx id 7747 lock_mode X waiting
- Record lock, heap no 3 PHYSICAL RECORD: n_fields 4; compact format; info bits 0
- 0: len 6; hex 000000000202; asc ;;
- 1: len 6; hex 000000001e41; asc A;;
- 2: len 7; hex 820000008b0110; asc ;;
- 3: len 4; hex 80000001; asc ;;
- --------
- FILE I/O
- --------
- I/O thread 0 state: waiting for i/o request (insert buffer thread)
- I/O thread 1 state: waiting for i/o request (log thread)
- I/O thread 2 state: waiting for i/o request (read thread)
- I/O thread 3 state: waiting for i/o request (read thread)
- I/O thread 4 state: waiting for i/o request (read thread)
- I/O thread 5 state: waiting for i/o request (read thread)
- I/O thread 6 state: waiting for i/o request (write thread)
- I/O thread 7 state: waiting for i/o request (write thread)
- I/O thread 8 state: waiting for i/o request (write thread)
- I/O thread 9 state: waiting for i/o request (write thread)
- Pending normal aio reads: [0, 0, 0, 0] , aio writes: [0, 0, 0, 0] ,
- ibuf aio reads:, log i/o's:, sync i/o's:
- Pending flushes (fsync) log: 0; buffer pool: 0
- 833 OS file reads, 605 OS file writes, 208 OS fsyncs
- 0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s
- -------------------------------------
- INSERT BUFFER AND ADAPTIVE HASH INDEX
- -------------------------------------
- Ibuf: size 1, free list len 0, seg size 2, 0 merges
- merged operations:
- insert 0, delete mark 0, delete 0
- discarded operations:
- insert 0, delete mark 0, delete 0
- Hash table size 553253, node heap has 0 buffer(s)
- Hash table size 553253, node heap has 1 buffer(s)
- Hash table size 553253, node heap has 3 buffer(s)
- Hash table size 553253, node heap has 0 buffer(s)
- Hash table size 553253, node heap has 0 buffer(s)
- Hash table size 553253, node heap has 0 buffer(s)
- Hash table size 553253, node heap has 0 buffer(s)
- Hash table size 553253, node heap has 0 buffer(s)
- 0.00 hash searches/s, 0.00 non-hash searches/s
- ---
- LOG
- ---
- Log sequence number 19643450
- Log buffer assigned up to 19643450
- Log buffer completed up to 19643450
- Log written up to 19643450
- Log flushed up to 19643450
- Added dirty pages up to 19643450
- Pages flushed up to 19643450
- Last checkpoint at 19643450
- ----------------------
- BUFFER POOL AND MEMORY
- ----------------------
- Total large memory allocated 2198863872
- Dictionary memory allocated 409606
- Buffer pool size 131072
- Free buffers 130095
- Database pages 973
- Old database pages 0
- Modified db pages 0
- Pending reads 0
- Pending writes: LRU 0, flush list 0, single page 0
- Pages made young 0, not young 0
- 0.00 youngs/s, 0.00 non-youngs/s
- Pages read 810, created 163, written 404
- 0.00 reads/s, 0.00 creates/s, 0.00 writes/s
- Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
- Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
- LRU len: 973, unzip_LRU len: 0
- I/O sum[0]:cur[0], unzip sum[0]:cur[0]
- ----------------------
- INDIVIDUAL BUFFER POOL INFO
- ----------------------
- ---BUFFER POOL 0
- Buffer pool size 65536
- Free buffers 65043
- Database pages 491
- Old database pages 0
- Modified db pages 0
- Pending reads 0
- Pending writes: LRU 0, flush list 0, single page 0
- Pages made young 0, not young 0
- 0.00 youngs/s, 0.00 non-youngs/s
- Pages read 411, created 80, written 210
- 0.00 reads/s, 0.00 creates/s, 0.00 writes/s
- Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
- Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
- LRU len: 491, unzip_LRU len: 0
- I/O sum[0]:cur[0], unzip sum[0]:cur[0]
- ---BUFFER POOL 1
- Buffer pool size 65536
- Free buffers 65052
- Database pages 482
- Old database pages 0
- Modified db pages 0
- Pending reads 0
- Pending writes: LRU 0, flush list 0, single page 0
- Pages made young 0, not young 0
- 0.00 youngs/s, 0.00 non-youngs/s
- Pages read 399, created 83, written 194
- 0.00 reads/s, 0.00 creates/s, 0.00 writes/s
- No buffer pool page gets since the last printout
- Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
- LRU len: 482, unzip_LRU len: 0
- I/O sum[0]:cur[0], unzip sum[0]:cur[0]
- --------------
- ROW OPERATIONS
- --------------
- 0 queries inside InnoDB, 0 queries in queue
- 0 read views open inside InnoDB
- Process ID=5772, Main thread ID=140286437054208 , state=sleeping
- Number of rows inserted 57, updated 354, deleted 4, read 4421
- 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s
- ----------------------------
- END OF INNODB MONITOR OUTPUT
- ============================
Standard Monitor Output Sections
For a description of each metric reported by the Standard Monitor, refer to the Metrics chapter in the Oracle Enterprise Manager for MySQL Database User's Guide.
Status
This section shows the timestamp, the monitor name, and the number of seconds that per-second averages are based on. The number of seconds is the elapsed time between the current time and the last time
InnoDB
Monitor output was printed.BACKGROUND THREAD
The
srv_master_thread
lines shows work done by the main background thread.SEMAPHORES
This section reports threads waiting for a semaphore and statistics on how many times threads have needed a spin or a wait on a mutex or a rw-lock semaphore. A large number of threads waiting for semaphores may be a result of disk I/O, or contention problems inside
InnoDB
. Contention can be due to heavy parallelism of queries or problems in operating system thread scheduling. Setting theinnodb_thread_concurrency
system variable smaller than the default value might help in such situations. TheSpin rounds per wait
line shows the number of spinlock rounds per OS wait for a mutex.Mutex metrics are reported by
SHOW ENGINE INNODB MUTEX
.LATEST FOREIGN KEY ERROR
This section provides information about the most recent foreign key constraint error. It is not present if no such error has occurred. The contents include the statement that failed as well as information about the constraint that failed and the referenced and referencing tables.
LATEST DETECTED DEADLOCK
This section provides information about the most recent deadlock. It is not present if no deadlock has occurred. The contents show which transactions are involved, the statement each was attempting to execute, the locks they have and need, and which transaction
InnoDB
decided to roll back to break the deadlock. The lock modes reported in this section are explained in Section 15.7.1, “InnoDB Locking”.TRANSACTIONS
If this section reports lock waits, your applications might have lock contention. The output can also help to trace the reasons for transaction deadlocks.
FILE I/O
This section provides information about threads that
InnoDB
uses to perform various types of I/O. The first few of these are dedicated to generalInnoDB
processing. The contents also display information for pending I/O operations and statistics for I/O performance.The number of these threads are controlled by the
innodb_read_io_threads
andinnodb_write_io_threads
parameters. See Section 15.13, “InnoDB Startup Options and System Variables”.INSERT BUFFER AND ADAPTIVE HASH INDEX
This section shows the status of the
InnoDB
insert buffer (also referred to as the change buffer) and the adaptive hash index.For related information, see Section 15.5.2, “Change Buffer”, and Section 15.5.3, “Adaptive Hash Index”.
LOG
This section displays information about the
InnoDB
log. The contents include the current log sequence number, how far the log has been flushed to disk, and the position at whichInnoDB
last took a checkpoint. (See Section 15.11.3, “InnoDB Checkpoints”.) The section also displays information about pending writes and write performance statistics.BUFFER POOL AND MEMORY
This section gives you statistics on pages read and written. You can calculate from these numbers how many data file I/O operations your queries currently are doing.
For buffer pool statistics descriptions, see Monitoring the Buffer Pool Using the InnoDB Standard Monitor. For additional information about the operation of the buffer pool, see Section 15.5.1, “Buffer Pool”.
ROW OPERATIONS
This section shows what the main thread is doing, including the number and performance rate for each type of row operation.
Deutsche Übersetzung
Sie haben gebeten, diese Seite auf Deutsch zu besuchen. Momentan ist nur die Oberfläche übersetzt, aber noch nicht der gesamte Inhalt.Wenn Sie mir bei Übersetzungen helfen wollen, ist Ihr Beitrag willkommen. Alles, was Sie tun müssen, ist, sich auf der Website zu registrieren und mir eine Nachricht zu schicken, in der Sie gebeten werden, Sie der Gruppe der Übersetzer hinzuzufügen, die Ihnen die Möglichkeit gibt, die gewünschten Seiten zu übersetzen. Ein Link am Ende jeder übersetzten Seite zeigt an, dass Sie der Übersetzer sind und einen Link zu Ihrem Profil haben.
Vielen Dank im Voraus.
Dokument erstellt 26/06/2006, zuletzt geändert 26/10/2018
Quelle des gedruckten Dokuments:https://www.gaudry.be/de/mysql-rf-innodb-standard-monitor.html
Die Infobro ist eine persönliche Seite, deren Inhalt in meiner alleinigen Verantwortung liegt. Der Text ist unter der CreativeCommons-Lizenz (BY-NC-SA) verfügbar. Weitere Informationen auf die Nutzungsbedingungen und dem Autor.
Referenzen
Diese Verweise und Links verweisen auf Dokumente, die während des Schreibens dieser Seite konsultiert wurden, oder die zusätzliche Informationen liefern können, aber die Autoren dieser Quellen können nicht für den Inhalt dieser Seite verantwortlich gemacht werden.
Der Autor Diese Website ist allein dafür verantwortlich, wie die verschiedenen Konzepte und Freiheiten, die mit den Nachschlagewerken gemacht werden, hier dargestellt werden. Denken Sie daran, dass Sie mehrere Quellinformationen austauschen müssen, um das Risiko von Fehlern zu reduzieren.