MySQL 5.1集群DBA认证学习指南摘录

4星 · 超过85%的资源需积分: 10 133 浏览量更新于2024-08-02 收藏 1.13MB PDF 举报

"MySQL5.1 Cluster DBA Certification Study Guide 是一本官方的MySQL DBA教材，涵盖了集群管理等关键主题。" 在MySQL数据库管理员(DBA)的学习路径中，掌握集群管理至关重要，尤其是对于那些寻求MySQL 5.1 Cluster DBA认证的专业人士而言。此教材摘录了官方的MySQL 5.1 Cluster DBA认证学习指南，提供了全面深入的知识内容。以下是对该教材中部分关键知识点的详细说明： ### 集群管理(Chapter 6 - Cluster Management) #### 基本概念与目的 - **MySQL集群管理客户端(ndb_mgm)**：这是用于管理MySQL集群的主要工具，能执行各种操作，如监控集群状态、启动、停止或重启节点。 #### 集群的启动、停止与重启 - **启动、停止和重启集群及单个节点**：了解如何正确地启动整个集群以及单独的节点，这对故障恢复和维护非常重要。 - **滚动重启(Rolling Restart)**：这是一种无需停机即可更新或修复集群的方法，教材将指导如何在不影响服务的情况下进行操作。 #### 监控集群状态 - **监控基础**：学习如何实时查看集群的健康状况，包括性能指标、连接状态等，这对于预防和解决问题至关重要。 #### 日志记录与事件级别 - **日志事件和级别**：理解如何控制记录在集群日志中的信息，包括设置不同级别的日志记录，以适应不同的监控需求。 #### 单用户模式 - **进入和退出单用户模式**：在特定情况下，如执行紧急维护或配置更改时，需要使用单用户模式。教材会解释何时以及如何使用这一模式。 ### 管理客户端基础知识(6.1 - Management Client Basics) - **启动和退出管理客户端**：学习启动ndb_mgm客户端的命令，以及在完成任务后正确关闭客户端的方法。 - **START, STOP, REST**：这些命令是集群管理的基本操作，教材会详细介绍它们的功能和使用场景，包括启动集群、停止集群和恢复集群的操作。除此之外，教材可能还会涵盖其他的高级主题，如数据节点的添加和移除、配置参数调整、故障检测和恢复策略、备份与恢复策略等。通过深入学习这些内容，读者将能够有效地管理和优化MySQL集群，以确保高可用性和性能。建议对MySQL集群感兴趣的DBA和系统管理员购买完整版的教材，以获取最全面的信息和深入的实践指导。

ndb_mgm> 5 START

Database node 5 is being started.

Node 5: Start initiated (version 5.1.24-ndb-6.2.16)

Node 5: Started (version 5.1.24-ndb-6.2.16)

ndb_mgm> 3 START

Database node 3 is being started.

Node 3: Start initiated (version 5.1.24-ndb-6.2.16)

Node 3: Started (version 5.1.24-ndb-6.2.16)

This is often required to perform a partial start of the cluster. (See Section 6.2.1.3, “Partial

Starts”.)

4. Once all data nodes have been started in this way, you can proceed to start the cluster's SQL

nodes exactly as described previously, in Section 6.2.1.1, “Starting the Cluster without the Man-

agement Client”.

6.2.1.3. Partial Starts

Sometimes it is desirable to perform a partial start of the cluster. For example, you may need to start

the cluster even though one or more data node hosts are unavailable due to hardware or software is-

sues. It is possible to start the cluster when one or more data nodes are not running. However, there

must be at least one “live” data node from each node group in order to form a viable cluster, even

when performing a partial start. As discussed in Section 2.2.3, “Nodes and Node Groups”, unless all

node groups are represented, the cluster does not have a complete copy of all its data, and so is not vi-

able.

Normally, the management server waits until all data nodes have been started before bringing the

cluster online. You can override this behavior by starting each data node with the --nowait-nodes

option, which is used to start the cluster without all data nodes being available. This option takes a

comma-separated list of data nodes which for which the cluster does not wait before starting:

--nowait-nodes=node_id_1[, node_id_2[, ...]]

For example, suppose your cluster has 4 data nodes in 2 node groups, the data nodes having node IDs 2

through 5, and you wish to perform a partial start omitting node 3. Assuming that each data node is

running on a different host, you could perform a partial start of the cluster by starting ndb_mgmd as

normal, then invoking ndbd on each data node host as shown here:

# On the machine hosting node 2:

shell> ndbd --no-wait-nodes=3

# On the machine hosting node 4:

shell> ndbd --no-wait-nodes=3

# On the machine hosting node 5:

shell> ndbd --no-wait-nodes=3

6.2.1. Methods for Starting a MySQL Cluster

129

Different Cluster configuration parameters may require individual nodes, all data nodes, or

the entire cluster to be restarted before taking effect. In some cases, you may need to stop,

then start nodes again; in others, it may be possible to update the appropriate configuration

file and then restart the node.

You can find out which parameters require which restart types by consulting Section 4.3.4,

“config.ini Parameters”.

• Upgrading the cluster to a newer version of the MySQL Cluster software (or downgrading it to an

older version).

• To make changes in the hardware or operating system of the hosts on which one or more cluster

nodes are running.

• Resetting the cluster because it has reached an undesirable state.

• Freeing memory allocated to a specific table by successive INSERT and DELETE operations on

that table for re-use by other MySQL Cluster tables.

Restarting a data node can be accomplished using the management client node_id RESTART com-

mand, where node_id is the node ID. This can also be used to restart a management node. In this

case, the management client loses the connection, but the next command (such as CONNECT or SHOW)

automatically reconnects it. Alternatively, you can stop the management server using either the man-

agement client STOP command or an operating system command such as kill, then start it again

from the command line. To restart an SQL node, you can use any of the standard methods for restart-

ing a MySQL server.

Generally, the steps in performing a rolling restart of a MySQL Cluster are as follows:

1. Stop all cluster management nodes (ndb_mgmd processes), reconfigure them, then restart them

2. Stop, reconfigure, then restart each cluster data node (ndbd process) in turn

3. Stop, reconfigure, then restart each cluster SQL node (mysqld process) in turn

The exact steps for implementing a particular rolling upgrade depend upon the actual changes being

made. As previously mentioned, a restart requires completely stopping then starting the node again, or

you may need only to update the appropriate configuration file and then restart the node (using the

management client RESTART command). The following diagram shows more specific information for

different restart scenarios:

6.2.2. Rolling Restarts

131

can find out when this is necessary by consulting the MySQL Manual's Overview of Cluster Configur-

ation Parameters

[http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-config-params-overview.html].

6.3. Monitoring and Logging

Description: This section covers the use of the Cluster management client, the ndb_config utility,

and the MySQL SHOW ENGINE NDB STATUS statement for monitoring node status, cluster status,

and cluster configuration. It also discusses Cluster log files, their purposes and locations, and how to

understand their contents.

6.3.1. Monitoring the Cluster

This section covers available methods for obtaining information about the current status of the cluster

and cluster nodes, including the following topics:

• The management client commands SHOW, STATUS, and DUMP commands.

• The MySQL Server's SHOW ENGINE NDB STATUS statement

In addition, the ndb_config utility can be used to obtain cluster configuration data from the con-

fig.ini file. For more information about ndb_config, see Section 4.4, “Utility Programs”.

6.3.1.1. The SHOW, STATUS, and DUMP Commands

The MySQL Cluster management client provides two commands — SHOW and STATUS — that can be

used to monitor the status of the cluster. In addition, the DUMP command writes the values of node

parameters to the cluster log.

The SHOW command. This command displays the status of each cluster node for which a node ID has

been allocated in the global cluster configuration (config.ini) file.

The information provided by SHOW is organized by node ID, and includes:

• The IP address or hostname and the port number of the management server to which the current in-

stance of ndb_mgm is connected.

• Data nodes. For all data nodes as a group the total number of data nodes in the cluster is shown.

In addition, SHOW displays the IP address or hostname to which each data node is assigned, wheth-

er or not the node is connected to the cluster.

For each data node that is connected to the cluster, the SHOW command displays:

• The node ID

• The hostname or IP address of the host to which that node ID is assigned

• The MySQL Cluster software version

• The node group to which the node belongs

6.3. Monitoring and Logging

133

剩余128页未读，继续阅读

conish

粉丝: 0
资源: 25

MySQL 5.1集群DBA认证学习指南摘录

MySQL基础PDF版

mysql dba认证题库

mysql dba 高级 视频

如何学习mysqldba

mysql dba 工作笔记 pdf

mysqldba网盘

mysql dba 必备脚本

mysql dba手册

mysqldba工作笔记

mysqldba运维笔记超详细 pdf

最新资源

mysql dba 高级视频