MySQL event scheduler Event Scheduler detailed explanation
The event scheduler is another new feature added in MySQL 5.1. It can be used as a scheduled task scheduler, replacing some of the scheduled functions that could only be completed by the operating system task scheduler. For example, the crontabe in Linux can only be executed accurately once per minute, while the MySQL event scheduler can execute one task per second, which is very practical in some environments with high real-time requirements. .
The event scheduler is triggered and executed regularly. From this perspective, it can also be called a "temporary trigger". Triggers only execute some statements for events generated by a certain table, while event schedulers execute some statements at a certain (interval) time. Events are managed by a specific thread, the so-called "event scheduler". After enabling the event scheduler, an account with SUPER permissions can see this thread by executing SHOW PROCESSLIST. By setting the value of the global variable event_scheduler, you can dynamically control whether the event scheduler is enabled.
(root:localhost:)test> SET GLOBAL event_scheduler = ON;(root:localhost:)test> show processlistG****************************** **** 4. row ***************************Id: 46147User: event_schedulerHost: localhostdb: NULLCommand: DaemonTime: 1State: Waiting on empty queueInfo: NULL
As above, the owner of this thread is event_scheduler.
Application Case
This case uses the characteristics of the event scheduler to call a stored procedure every second to determine whether SLAVE is running normally. If it is found that SLAVE is closed, ignore 0 errors and then restart SLAVE.
First create a stored procedure
delimiter //create procedure `Slave_Monitor`()beginSELECT VARIABLE_VALUE INTO @SLAVE_STATUS FROM information_schema.GLOBAL_STATUS WHERE VARIABLE_NAME='SLAVE_RUNNING';IF ('ON' != @SLAVE_STATUS) THENSET GLOBAL SQL_SL AVE_SKip_COUNTER= 0;SLAVE START;END IF;end; //delimiter ;
Since statements like SHOW SLAVE STATUS cannot be called in the stored procedure, the exact copy error information and error code cannot be obtained, and SLAVE cannot be processed further. Stop various situations.
Next, create the task
CREATE EVENT IF NOT EXISTS `Slave_Monitor`
ON SCHEDULE EVERY 5 SECOND
ON COMPLETION PRESERVE
DO
CALL Slave_Monitor();
Created a task every 5 Executed once every second, the task will still be retained after the task is completed, rather than deleted. Of course, the task in this example will not end unless it is manually disabled.
If you want to temporarily close a task during operation, execute the ALTER EVENT statement:
(root:localhost:)test> alter event `Slave_Monitor` ON
COMPLETION PRESERVE DISABLE;
(root :localhost:)test> alter event `Slave_Monitor` ON
COMPLETION PRESERVE ENABLE;
The above is the detailed explanation of the MySQL event scheduler Event Scheduler. For more related articles, please pay attention to the PHP Chinese website (www.php.cn)!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

Data Integration Simplification: AmazonRDSMySQL and Redshift's zero ETL integration Efficient data integration is at the heart of a data-driven organization. Traditional ETL (extract, convert, load) processes are complex and time-consuming, especially when integrating databases (such as AmazonRDSMySQL) with data warehouses (such as Redshift). However, AWS provides zero ETL integration solutions that have completely changed this situation, providing a simplified, near-real-time solution for data migration from RDSMySQL to Redshift. This article will dive into RDSMySQL zero ETL integration with Redshift, explaining how it works and the advantages it brings to data engineers and developers.
