• No se han encontrado resultados

Emisiones evitadas por la hidroenergía

In document Manual de entrenamiento (página 161-173)

This section describes the prerequisites for a successful MySQL Enterprise Monitor installation.

3.2.1 System Requirements

This section describes the minimum and recommended system requirements for a successful MySQL Enterprise Monitor installation.

Minimum Hardware Requirements

This section describes the minimum hardware requirements for the Enterprise Service Monitor. • 2 CPU Cores

• 2 GB RAM

• Disk I/O subsystem applicable to a write-intensive database

Recommended Hardware Requirements

This section describes the recommended hardware requirements for the Enterprise Service Manager. • 4 CPU Cores or more

• 8 GB RAM or more

• RAID10 or RAID 0+1 disk setup

MySQL Enterprise Monitor Disk space Requirements

The following table lists the minimum disk space required to install the Enterprise Service Manager and Monitoring Agent for each platform.

Table 3.1 Disk space Required

Platform Minimum Disk space Required by Service Manager

Minimum Disk space Required by Monitoring Agent Linux x86 32-bit 1.1 GB 600 MB Linux x86 64-bit 1.3 GB 800 MB Mac OS X 1.2 GB 700 MB Solaris x86 32-bit 1.5 GB 600 MB Solaris x86 64-bit 1.8 GB 800 MB Solaris Sparc 64- bit 1.7 GB 600 MB

Free BSD N/A 300 MB (the FreeBSD installation

does not include a JRE. It is assumed a compatible JRE is present on the system.)

Supported Platforms

Platform Minimum Disk space Required by Service Manager

Minimum Disk space Required by Monitoring Agent Windows x86 32- bit 800 MB 500 MB Windows x86 64- bit 800 MB 500 MB Important

The minimum disk space values for the Monitoring Agent include the disk space required by the backlog. The backlog is used if the agent loses contact with the Service Manager and cannot transmit the collected data. The collected data is stored on the agent's local file system until communication with the Service Manager resumes. Once normal communication is resumed, the entire backlog is transmitted, then deleted from the agent's local file system.

If you choose to install the bundled MySQL Server with the Enterprise Service Manager, you must also consider the amount of disk space required by the database. This value cannot be predicted as it depends on load, number of monitored instances, and so on.

Important

If you are upgrading from a previous version of MySQL Enterprise Monitor, the upgrade process can create a full backup of all settings, including the local MySQL database used for the repository. This can result in a very large backup directory, several gigabytes in size, depending on the number of monitoring agents, and server load. Before upgrading, check the size of your existing installation and ensure you have enough disk space to run the upgrade. The upgrade also requires enough disk space for temporary files created by the upgrade process.

3.2.2 Supported Platforms

The supported platforms for MySQL Enterprise Service Manager and MySQL Enterprise Monitor Agent are listed at the following locations:

• MySQL Enterprise Service Manager Supported Platforms

• MySQL Enterprise Monitor Agent Supported Platforms

For platform support updates, see MySQL Product Support Announcements.

General Platform Recommendations

The following are recommended:

• Ensure that your Service Manager and Agent hosts are synchronized to the same time server. It is important that all times are properly synchronized.

• Ensure that your Service Manager and Agent hosts use different SSH host keys before installing.

MySQL Requirements

This section describes the MySQL Server requirements for MySQL Enterprise Monitor installation. • The Enterprise Server Manager repository requires MySQL Server 5.6.14 or higher. The MySQL

Enterprise Service Manager installation includes the latest version of MySQL Server. If you intend to use a MySQL repository other than the one bundled in the MySQL Enterprise Service Manager installation, it is recommended that you use the latest MySQL 5.6.x version.

MySQL Enterprise Monitor Repository

• If you have previously configured a default login path on the same machine on which you are installing MySQL Enterprise Service Manager with the bundled repository, you must delete the cnf

in which the default login details are defined before installing. If a default login path is defined, the installation fails to complete. It is recommended to install MySQL Enterprise Service Manager on a dedicated server.

• The Monitoring Agent can monitor any version of MySQL Server from version 5.0 onwards. See

Section 5.2, “Creating MySQL User Accounts for the Monitor Agent” for more information on monitoring older versions.

• The monitoring Agent always uses PERFORMANCE_SCHEMA.GLOBAL_STATUS on MySQL 5.7 versions, and supports both modes of show_compatibility_56 from MySQL 5.7.9 onwards.

Note

To monitor versions of MySQL 5.7.8, show_compatibility_56 must be set to OFF.

3.2.3 MySQL Enterprise Monitor Repository

The Enterprise Service Manager requires a repository to store its data. The installer optionally installs a local, clean repository for this purpose. However, you can choose not to install the bundled MySQL Server and use another repository instead. This repository can be on the same machine as the Enterprise Service Manager, or on a remote machine.

The repository instance must be present before starting the MySQL Enterprise Monitor installation.

Important

It is strongly recommended you use a clean installation of MySQL Server as the Enterprise Service Manager repository and do not use this server for any other purpose.

You must make several configuration changes to enable it for use as the repository.

Ensure the following:

• The MySQL Server version is 5.6.14 or higher.

Note

It is possible to use MySQL 5.5.8, or 5.6.10, or higher, but 5.6.14 is the recommended minimum version for the MySQL Enterprise Monitor repository. • The InnoDB storage engine is available.

• SSL is enabled. For more information on configuring SSL for MySQL Enterprise Monitor, see

Section 6.2, “Installing SSL Certificates”.

You must ensure the following in the MySQL Server configuration: • Query Cache must not be enabled.

• Set innodb_file_per_table=1. • Set innodb_file_format=Barracuda.

• On Linux/Unix hosts, ensure innodb_flush_method=O_Direct, except on Solaris if ZFS is used. If using ZFS, comment out this parameter.

Credentials Needed for Installation

• Define a Service Manager user to enable the MySQL Enterprise Service Manager to connect to, and modify, the repository. This user must have the following privileges:

• CREATE

• ALTER

• DROP

• INDEX

• CREATE TEMPORARY TABLES

• CREATE USER • DELETE • INSERT • PROCESS • REPLICATION CLIENT • SELECT • SHOW DATABASES • UPDATE

The Service Manager user's credentials are required by the MySQL Enterprise Service Manager installation process.

In document Manual de entrenamiento (página 161-173)