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

What are the changes of MYSQL8 packs and the new version in MGR? I believe many inexperienced people are at a loss about this. Therefore, this paper summarizes the causes and solutions of the problems. Through this article, I hope you can solve this problem.

As MYSQL 8 becomes more and more mature, MYSQL will begin to replace MYSQL 5.7X as the main force of the new MYSQL database on the market in the future.

And some changes of MYSQL 8 in packs (performance_schema), and how to better monitor MGR this is a place worth learning.

After MYSQL 8, packs introduced two information: XCOM and GCS, which is mainly to increase the observability and management of MGR.

1 introduced some Xcom GCS information in thread

The main role of these four threads is to start

Gcs_ext_logger_impl::m_consumer handles the logging thread after any trigger point

Gcs_xcom_engine::m_engine_thread handles event threads in GCS

Gcs_xcom_control::m_xcom_thread is responsible for the running thread of xcom

Gcs_xcom_control::m_suspicions_processing_thread handles unexpected threads that expel nodes

2 you can also view the waiting information about these two aspects in the waiting event table.

First of all, we need to turn on the relevant waiting time recording switch.

After opening it, we can find out the details of the problems in the use of MGR by looking at the relevant waiting records, or historical waiting records. Which wait events correspond to which problems can be solved by looking at the official documentation.

And in Replication_group_member_stats

Added some fields to MYSQL 8 in

1 COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE

Transactions from the receiving group are waiting in the queue

2 COUNT_TRANSACTIONS_REMOTE_APPLIED

Transactions that members have applied from the application group

3 COUNT_TRANSACTION_LOCAL_PROPOSED

Number of collaborative transactions in the group

4 COUNT_TRANSACTION_LOCAL_ROLLEDBACK

The number of rollback transactions in the group,

And Large Messages Fragmentation Layer for Group Replication is mentioned in a recent article published by Aricsson, which is a solution to the problem of offline MGR hosts caused by large transactions mentioned in MGR, by clustering large transactions by reassembling them after breaking up transactions.

In addition, MYSQL 8.016 is still there, and instead of binding a static number, XCom's message cache begins to dynamically set up changes according to the size of the message.

The latest version of 8.016 supports Auto-rejoin for Group Replication, and MYSQL that is kicked out in a future version is likely to be rejoined automatically, instead of relying on manual loading.

The speed of development is too fast to keep up with it step by step.

After reading the above, have you mastered the changes of MYSQL8 packs and the new version in MGR? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

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.