Home News Feeds Planet MySQL
Newsfeeds
Planet MySQL
Planet MySQL - https://planet.mysql.com

  • MariaDB 5.5.59 now available
    The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.59. This is a stable (GA) release. See the release notes and changelog for details. Download MariaDB 5.5.59 Release Notes Changelog What is MariaDB 5.5? MariaDB APT and YUM Repository Configuration Generator Thanks, and enjoy MariaDB! The post MariaDB 5.5.59 now available appeared first on MariaDB.org.

  • MariaDB Server 5.5.59 now available
    MariaDB Server 5.5.59 now available dbart Fri, 01/19/2018 - 11:07 The MariaDB project is pleased to announce the immediate availability of MariaDB Server 5.5.59. See the release notes and changelog for details and visit mariadb.com/downloads to download. Download MariaDB Server 5.5.59 Release Notes Changelog What is MariaDB 5.5? Community MariaDB Releases MySQL The MariaDB project is pleased to announce the immediate availability of MariaDB Server 5.5.59. See the release notes and changelog for details. Login or Register to post comments

  • Shinguz: Short term notice: Percona XtraDB Cluster training in English 7/8 February 2018 in Germany
    FromDual offers short term a Percona XtraDB Cluster and MySQL Galera Cluster training (2 days) in English. The training will take place in the Linuxhotel in Essen/Germany on February 7/8 2018. There are already enough registrations so it is certain the training will take place. But there are still free places for some additional participants. You can book online at the Linuxhotel. Important: The Linuxhotel is nearly fully booked out. So accommodation is in nearby locations. The Linuxhotel will recommend you some locations. The training is in English. You can find the contents of this 2-day Percona XtraDB Cluster training here. If you have any question please do not hesitate to contact us. Taxonomy upgrade extras:  galera Percona XtraDB Cluster training linuxhotel

  • Enhanced replication monitoring in ProxySQL 1.4.4
    ProxySQL and pt-heartbeat The Percona toolkit provides a very useful script for more accurate replication lag monitoring called pt-heartbeat. The pt-heartbeat script provides replication lag metrics based on actual data that has been replicated and is more accurate than the Seconds_Behind_Master metrics gathered from the output of SHOW SLAVE STATUS. Seconds_Behind_Master relies purely on system time (i.e. current time - time the event executed on the master server). By default ProxySQL relies on the output of the SHOW SLAVE STATUS command in order to identify replicas that should be excluded from the backend connection pool when max_replication_lag has been configured for a server in the mysql_servers table. Starting from ProxySQL version 1.4.4 a new feature has been introduced in order to leverage the data provided by pt-heartbeat and in turn much more precise replication lag monitoring, all that is required is to configure mysql-monitor_replication_lag_use_percona_heartbeat with the database and table name which pt-heartbeat is writing to. This tutorial aims to provide a simple how-to article in order to setup pt-heartbeat and use the data provided for ProxySQL's replication lag monitoring. In order to proceed you'll need to make sure the Percona toolkit is installed on your system. Instructions can be found here. After Percona toolkit has been installed (either on a monitoring server or your master server) you can proceed with the following steps: Create a percona database (on the master) to store the heartbeat data: $ mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 7653 Server version: 5.7.19-17-log Percona Server (GPL), Release '17', Revision 'e19a6b7b73f' Copyright (c) 2009-2017 Percona LLC and/or its affiliates Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> CREATE DATABASE IF NOT EXISTS percona; Query OK, 1 row affected, 1 warning (0.54 sec) mysql> exit; Bye Now we're ready to kick off the pt-heartbeat process: $ pt-heartbeat -D percona --update -h localhost --create-table --daemonize Lets go ahead and verify pt-heartbeat is running properly on the slave: $ mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 7653 Server version: 5.7.19-17-log Percona Server (GPL), Release '17', Revision 'e19a6b7b73f' Copyright (c) 2009-2017 Percona LLC and/or its affiliates Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> select * from percona.heartbeat; +----------------------------+-----------+------------------+----------+-----------------------+---------------------+ | ts | server_id | file | position | relay_master_log_file | exec_master_log_pos | +----------------------------+-----------+------------------+----------+-----------------------+---------------------+ | 2018-01-18T17:13:42.000790 | 192168111 | mysql-bin.000020 | 51025284 | mysql-bin.000012 | 40774236 | +----------------------------+-----------+------------------+----------+-----------------------+---------------------+ 1 row in set (0.00 sec) mysql> select * from percona.heartbeat; +----------------------------+-----------+------------------+----------+-----------------------+---------------------+ | ts | server_id | file | position | relay_master_log_file | exec_master_log_pos | +----------------------------+-----------+------------------+----------+-----------------------+---------------------+ | 2018-01-18T17:13:44.001590 | 192168111 | mysql-bin.000020 | 51026250 | mysql-bin.000012 | 51026250 | +----------------------------+-----------+------------------+----------+-----------------------+---------------------+ 1 row in set (0.00 sec) We can see from the above output that the pt-heartbeat data is being written on the master and is replicating to the slave as well so now we're ready to configure the ProxySQL host. Connect to the ProxySQL Admin interface: $ mysql -uadmin -padmin -h127.0.0.1 -P6032 --prompt 'Admin> ' mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 4 Server version: 5.5.30 (ProxySQL Admin Module) Copyright (c) 2009-2017 Percona LLC and/or its affiliates Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. Admin> The next step is to enable the replication lag check on all or sum of the servers as desired: Admin> SELECT * FROM mysql_servers; +--------------+---------------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ | hostgroup_id | hostname | port | status | weight | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment | +--------------+---------------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ | 10 | ubuntu-vm-nv1 | 3306 | ONLINE | 1 | 0 | 1000 | 0 | 0 | 0 | | | 20 | ubuntu-vm-nv2 | 3306 | ONLINE | 1 | 0 | 1000 | 0 | 0 | 0 | | +--------------+---------------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ 2 rows in set (0.03 sec) Admin> update mysql_servers set max_replication_lag = 30; Query OK, 2 rows affected (0.00 sec) Admin> save mysql servers to disk; load mysql servers to runtime; Query OK, 0 rows affected (0.40 sec) Query OK, 0 rows affected (0.00 sec) Here the threshold has been set to 30(s) on all servers, feel free to adjust to whatever granularity your checks require. Remember that the frequency of the check is controlled by the mysql-monitor_replication_lag_interval variable. Make sure that max_replication_lag is not smaller than mysql-monitor_replication_lag_interval. Finally configure ProxySQL to use pt-heartbeat data: Admin> select @@mysql-monitor_replication_lag_use_percona_heartbeat; +-------------------------------------------------------+ | @@mysql-monitor_replication_lag_use_percona_heartbeat | +-------------------------------------------------------+ | | +-------------------------------------------------------+ 1 row in set (0.00 sec) Admin> set mysql-monitor_replication_lag_use_percona_heartbeat = 'percona.heartbeat'; Query OK, 1 row affected (0.00 sec) Admin> save mysql variables to disk; load mysql variables to runtime; Query OK, 93 rows affected (0.30 sec) Query OK, 0 rows affected (0.00 sec) ProxySQL is now monitoring replication lag using Percona's pt-heartbeat! Authored by: Nick Vyzas

  • Percona Monitoring and Management (PMM) 1.6.0 Is Now Available
    Percona announces the release of Percona Monitoring and Management (PMM) 1.6.0. In this release, Percona Monitoring and Management Grafana metrics are available in the Advanced Data Exploration dashboard. We’ve improved the integration with MyRocks, and its data is now collected from SHOW GLOBAL STATUS. The MongoDB Exporter now features two new metrics: mongodb_up to inform if the MongoDB Server is running and mongodb_scrape_errors_total reporting the total number of errors when scaping MongoDB. In this release, we’ve greatly improved the performance of the mongodb:metrics monitoring service. Percona Monitoring and Management (PMM) 1.6.0 also includes version 4.6.3 of Grafana which includes fixes to bugs in the alert list and the alerting rules. More information is available in the Grafana’s change log. New Features PMM-1773: PMM Grafana specific metrics have been added to the Advanced Data Exploration dashboard. Improvements PMM-1485: Updated MyRocks integration: MyRocks data is now collected entirely from SHOW GLOBAL STATUS, and we have eliminated SHOW ENGINE ROCKSDB STATUS as a data source in mysqld_exporter. PMM-1895: Update Grafana to version 4.6.3: Alert list: Now shows alert state changes even after adding manual annotations on dashboard #9951 Alerting: Fixes bug where rules evaluated as firing when all conditions were false and using OR operator. #9318 PMM-1586: The mongodb_exporter exporter exposes two new metrics: mongodb_up informing if the MongoDB Server is running and mongodb_scrape_errors_total informing the total number of times an error occurred when scraping MongoDB. PMM-1764: Various small mongodb_exporter improvement PMM-1942: Improved the consistency of using labels in all Prometheus related dashboards. PMM-1936: Updated the Prometheus dashboard in Metrics Monitor PMM-1937 Added the CPU Utilization Details (Cores) dashboard to Metrics Monitor. Bug fixes PMM-1549: Broken default auth db for mongodb:queries PMM-1631: In some cases, percentage values were displayed incorrectly for MongoDB hosts. PMM-1640: RDS exporter: simplify configuration PMM-1760: After the mongodb:metrics monitoring service was added, the usage of CPU considerably increased in QAN versions 1.4.1 through 1.5.3. 1.5.0 – CPU usage 95% 1.5.3 – CPU usage 85% 1.6.0 – CPU usage 1% PMM-1815: QAN could show data for a MySQL host when a MongoDB host was selected. PMM-1888: In QAN, query metrics were not loaded when the QAN page was refreshed. PMM-1898: In QAN, the Per Query Stats graph displayed incorrect values for MongoDB PMM-1796: In Metrics Monitor, the Top Process States Hourly graph from the MySQL Overview dashboard showed incorrect data. PMM-1777: In QAN, the Load column could display incorrect data. PMM-1744: The error Please provide AWS access credentials error appeared although the provided credentials could be processed successfully. PMM-1676: In preparation for migration to Prometheus 2.0 we have updated the System Overview dashboard for compatibility. PMM-1920: Some standard MySQL metrics were missing from the mysqld_exporter  Prometheus exporter. PMM-1932: The Response Length metric was not displayed for MongoDB hosts in QAN.

Banner
Copyright © 2018 Energy Himalaya. All Rights Reserved.
Joomla! is Free Software released under the GNU/GPL License.