{"id":12286,"date":"2023-11-11T18:30:18","date_gmt":"2023-11-12T01:30:18","guid":{"rendered":"https:\/\/www.mysqltutorial.org\/?page_id=12286"},"modified":"2023-11-12T06:54:11","modified_gmt":"2023-11-12T13:54:11","slug":"mysql-blackhole-storage-engine","status":"publish","type":"page","link":"https:\/\/www.mysqltutorial.org\/mysql-administration\/mysql-blackhole-storage-engine\/","title":{"rendered":"MySQL BLACKHOLE Storage Engine"},"content":{"rendered":"\n

Summary<\/strong>: in this tutorial, you will learn about MySQL BLACKHOLE storage engine and its application in a replication setup.<\/p>\n\n\n\n

Introduction to MySQL BLACKHOLE storage engine<\/h2>\n\n\n\n

Unlike other storage engines, the BLACKHOLE storage engine doesn’t store table data. This means that when you send data to the BLACKHOLE tables, they immediately discard the data.<\/p>\n\n\n\n

To check if the current MySQL server supports the BLACKHOLE storage engine or not, you use the following query:<\/p>\n\n\n

SELECT<\/span> \n  engine<\/span>, \n  support \nFROM<\/span> \n  information_schema.engines \nORDER<\/span> BY<\/span> \n  engine<\/span>;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
Output:<\/p>\n\n\n
+--------------------+---------+\n| engine             | support |\n+--------------------+---------+\n| ARCHIVE            | YES     |\n| BLACKHOLE          | YES     |\n| CSV                | YES     |\n| FEDERATED          | NO      |\n| InnoDB             | DEFAULT |\n| MEMORY             | YES     |\n| MRG_MYISAM         | YES     |\n| MyISAM             | YES     |\n| ndbcluster         | NO      |\n| ndbinfo            | NO      |\n| PERFORMANCE_SCHEMA | YES     |\n+--------------------+---------+\n11 rows in set (0.00 sec)<\/code><\/span>Code language:<\/span> plaintext<\/span> (<\/span>plaintext<\/span>)<\/span><\/small><\/pre>\n\n\n
If your MySQL server supports the BLACKHOLE storage engine, you can start using it.<\/p>\n\n\n\n
First, create a new table<\/a> that uses the BLACKHOLE storage engine:<\/p>\n\n\n
CREATE<\/span> TABLE<\/span> products(\n    id<\/span> INT<\/span> AUTO_INCREMENT PRIMARY KEY<\/span>,\n    name<\/span> VARCHAR<\/span>(255<\/span>) NOT<\/span> NULL<\/span>\n) ENGINE<\/span> = 'BLACKHOLE'<\/span>;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
INSERT<\/span> INTO<\/span> products(name<\/span>)\nVALUES<\/span>('Flagship product'<\/span>);<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
Third, query data from the products<\/code> table:<\/p>\n\n\n
SELECT<\/span> * FROM<\/span> products;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
Output:<\/p>\n\n\n
Empty set<\/span> (0.00 sec)<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
It returns no rows because the blackhole tables do not store the data. <\/p>\n\n\n\n
The question is, why does the BLACKHOLE storage engine exist in the first place, and when can you use it?<\/p>\n\n\n\n
The BLACKHOLE storage engine can be useful in some scenarios such as replication.<\/p>\n\n\n\n
Using the BLACKHOLE storage engine in a replication setup<\/h2>\n\n\n\n
In MySQL, replication is a mechanism that allows you to replicate data changes from one MySQL server (the “master”) to one or more other MySQL servers (the “slaves”). <\/p>\n\n\n\n
Typically, you use replication for various purposes, including load balancing, high availability, and data backup. <\/p>\n\n\n\n
When you use replication, you want the data on the slave servers to be consistent with the data on the master server.<\/p>\n\n\n\n
The BLACKHOLE storage engine can be useful in replication setups, specifically when you want to capture data changes on the master server without storing that data on the local server.<\/p>\n\n\n\n
On the master server, you create a table using the BLACKHOLE storage engine. This table doesn’t store any data and simply discards any data inserted into it.<\/p>\n\n\n
CREATE<\/span> TABLE<\/span> sample_tables (\n  id<\/span> INT<\/span> AUTO_INCREMENT PRIMARY KEY<\/span>, \n  data_column VARCHAR<\/span>(255<\/span>)\n) ENGINE<\/span> = BLACKHOLE;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
Whenever you insert, update, or delete data the sample_tables<\/code> on the master server, MySQL captures these operations in the binary log. The binary log is a record of all data modifications, and it’s a fundamental component of MySQL replication.<\/p>\n\n\n\n
The key point here is that the slave servers use a different storage engine (e.g., InnoDB or MyISAM) to store the replicated data. The BLACKHOLE storage engine on the master server doesn’t store the data locally, so there is no unnecessary storage overhead on the master.<\/p>\n\n\n\n
This setup allows you to capture and replicate data changes without keeping the data locally on the master server. It can be useful when you want to maintain data consistency across multiple servers while minimizing the storage requirements on the master. <\/p>\n\n\n\n
Summary<\/h2>\n\n\n\n
    \n
  • In MySQL, the BLACKHOLE storage engine does not store table data.<\/li>\n\n\n\n
  • Use the BLACKHOLE storage engine in a replication without keeping data locally on the master server.<\/li>\n<\/ul>\n
    \n\t
    \n\t\t
    Was this tutorial helpful? <\/div>\n\t\t
    \n\t\t\t\n\t\t\t\t\n\t\t\t\t\t<\/path>\n\t\t\t\t<\/svg>\n\t\t\t\t Yes <\/span>\n\t\t\t<\/button>\n\n\t\t\t\n\t\t\t\t\n\t\t\t\t\t<\/path>\n\t\t\t\t<\/svg>\n\t\t\t\t No <\/span>\n\t\t\t<\/button>\n\t\t<\/div>\n\t<\/header>\n\n\t
    \n\t\t
    \n\t\t\t
    <\/div>\n\t\t\t\n\t\t\t
MySQL then replicates the binary log to one or more slave servers. On the slave servers, you can use a different storage engine (e.g., InnoDB<\/a> or MyISAM<\/a>) to create a table with the same structure as the sample_tables<\/code>. MySQL will relay the data changes from the binary log on the slave, effectively making the data on the slave server consistent with the master.<\/p>\n\n\n\n
Second, insert a row into<\/a> the products<\/code> table:<\/p>\n\n\n