MySQL Cluster Manager 1.4.2 has been released
Dear MySQL Users, MySQL Cluster Manager 1.4.2 has been released and can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the next monthly update MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/ A brief summary of changes in MySQL Cluster Manager version 1.4.2 is listed below: Changes in MySQL Cluster Manager 1.4.2 (2017-03-07) This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.4.2 since the release of MySQL Cluster Manager version 1.4.1. Functionality Added or Changed * Agent: To allow easy detection of an incomplete agent backup, an empty file named INCOMPLETE is created in the folder in which the backup is created when the backup agents command begins, and is deleted after the backup is finished. The continuous existence of the file after the backup process is over indicates that the backup is incomplete. (Bug #25126866) * Agent: MySQL Cluster Manager can now recover automatically a failed mysqld node, as long as the data directory of the node is empty when recovery is attempted; if that is not the case, after cleaning up the data directory manually, users can now manually run the start process --initial to rebuild the mysqld node's data directory. (Bug #18415446) * Agent: A new command, update process, imports a process back into the control of mcmd after mcmd has lost track of the process' status due to different reasons (for example, it has been restarted manually outside of MySQL Cluster Manager). For more details, see the description of the command. * Agent: The show status command now reports progress when the new --progress or --progressbar options is used. Bugs Fixed * Agent: When a custom FileSystemPath value was used for a data node, the list backups and restore cluster commands failed, as the backup directory could not be found. (Bug #25549903) * Agent: In some situations, a certain mcmd agent took too long to process event messages that a synchronization timeout occurred among the agents. This was because the agent went into a mutex contention for file access, which this fix removes. (Bug #25462861) * Agent: The collect logs command reported success even if file transfers were incomplete. This fix adds checks for file transfer completion and reports any errors. (Bug #25436057) * Agent: An ndbmtd node sometimes (for example, at a rolling restart of the cluster) sent out a large amount of event messages, and it might take too long for an mcmd agent to process them that the agent lagged behind on its readiness for the next command, resulting in a synchronization timeout among the mcmd agents. This fix drastically reduced the amount of event messages sent by an ndbmtd node, thus reducing the chance of a synchronization timeout under the situation. (Bug #25358050) * Agent: A management node failure might trigger mcmd to quit unexpectedly on Windows platforms. (Bug #25336594) * Agent: Multiple errors thrown by the backup agents, rotate logs, and change log-level commands could potentially overwrite each other, causing a lost of error information. (Bug #25134452) * Agent: The collect logs command hung when TCP connections could not be established between the agent that initiated the command and the other agents. This fix makes the command timeout after the situation persists for more than 30s. Also, a new mcmd option, --copy-port, has been added, by which users can specify the TCP port number to be used for log copying. (Bug #25064313) * Agent: The .mcm file created by the import config --dryrun command sometimes have certain configuration settings missing from it. (Bug #24962848) * Agent: A restore cluster command would fail if MySQL Cluster Manager did not have write access to the BackupDataDir of each data node. The unnecessary requirement has now been removed. (Bug #24763936) * Agent: If a stop cluster or a stop process command had failed, a restart on some of the processes might fail with
MySQL Router 2.1.2 RC has been released
Dear MySQL users, MySQL Router 2.1.2 RC is a release candidate for MySQL Router 2.1. The MySQL Router is a new building block for high availability solutions based on MySQL InnoDB clusters. By taking advantage of the new Group Replication technology, and combined with the MySQL Shell, InnoDB clusters provide an integrated solution for high availability and scalability for InnoDB based MySQL databases, that does not require advanced MySQL expertise. The deployment of applications with high availability requirements is greatly simplified by MySQL Router. MySQL client connections are transparently routed to online members of a InnoDB cluster, with MySQL server outages and cluster reconfigurations being automatically handled by the Router. MySQL Router 2.1 also introduces the following additions: * Automatic setup/bootstrap with a MySQL InnoDB cluster * Support for the new X protocol * Support for deployments inside self-contained directories * Easy and secure password management using a built-in keyring You can download MySQL Router from http://dev.mysql.com/downloads/router. Package binaries are available for several platforms and also as a source code download. Documentation for MySQL Router can be found at http://dev.mysql.com/doc/mysql-router/en Enjoy! Changes in MySQL Router 2.1.2 (2017-03-06, Release Candidate) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Windows: downloads now require Visual C++ Redistributable for Visual Studio 2015, when before the 2013 version was required. * MySQL Fabric support was removed. * mysqlrouter --help output was improved to include the current default folder locations for the system, and also usage examples. * X Protocol support was added. The new protocol configuration option was added to support the X Protocol. Setting protocol to x enables the X Protocol for connections, otherwise the default classic protocol is used. * New SSL command line options: --ssl-mode, --ssl-ca, --ssl-capath, --ssl-cipher, --ssl-crl, --ssl-crlpath, and --tls-version. * Keyring key management was added to securely manage passwords. With this, the new master_key_path and keyring_path configuration options were added. * Bootstrapping support was added. New bootstrapping command line options: --bootstrap, --conf-base-port, --conf-bind-address, --conf-use-sockets, --conf-skip-tcp, --directory, --force, and --name Bugs Fixed * While bootstrapping router, the process to discover local interfaces had a memory leak. (Bug #25456674) * Fixed "use of uninitialized bytes" issues as discovered by valgrind. (Bug #25455825) * After bootstrapping router with the --conf-use-sockets and --directory options, the socket path configuration value defined in the generated configuration file was invalid. This was because it used the socketsdir value in the socket path, but the directory was not created as part of the bootstrap process or when router was started. (Bug #25391460) * On Windows, immediately starting a bootstrapped Router installation would fail to load the generated configuration file. In addition, the generated text for missing configuration files was improved to also include the paths that were checked. (Bug #25343904) On behalf of Oracle MySQL Release Team Balasubramanian Kandasamy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Router 2.1.2 RC has been released
Dear MySQL users, MySQL Router 2.1.2 RC is a release candidate for MySQL Router 2.1. The MySQL Router is a new building block for high availability solutions based on MySQL InnoDB clusters. By taking advantage of the new Group Replication technology, and combined with the MySQL Shell, InnoDB clusters provide an integrated solution for high availability and scalability for InnoDB based MySQL databases, that does not require advanced MySQL expertise. The deployment of applications with high availability requirements is greatly simplified by MySQL Router. MySQL client connections are transparently routed to online members of a InnoDB cluster, with MySQL server outages and cluster reconfigurations being automatically handled by the Router. MySQL Router 2.1 also introduces the following additions: * Automatic setup/bootstrap with a MySQL InnoDB cluster * Support for the new X protocol * Support for deployments inside self-contained directories * Easy and secure password management using a built-in keyring You can download MySQL Router from http://dev.mysql.com/downloads/router. Package binaries are available for several platforms and also as a source code download. Documentation for MySQL Router can be found at http://dev.mysql.com/doc/mysql-router/en Enjoy! Changes in MySQL Router 2.1.2 (2017-03-06, Release Candidate) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Windows: downloads now require Visual C++ Redistributable for Visual Studio 2015, when before the 2013 version was required. * MySQL Fabric support was removed. * mysqlrouter --help output was improved to include the current default folder locations for the system, and also usage examples. * X Protocol support was added. The new protocol configuration option was added to support the X Protocol. Setting protocol to x enables the X Protocol for connections, otherwise the default classic protocol is used. * New SSL command line options: --ssl-mode, --ssl-ca, --ssl-capath, --ssl-cipher, --ssl-crl, --ssl-crlpath, and --tls-version. * Keyring key management was added to securely manage passwords. With this, the new master_key_path and keyring_path configuration options were added. * Bootstrapping support was added. New bootstrapping command line options: --bootstrap, --conf-base-port, --conf-bind-address, --conf-use-sockets, --conf-skip-tcp, --directory, --force, and --name Bugs Fixed * While bootstrapping router, the process to discover local interfaces had a memory leak. (Bug #25456674) * Fixed "use of uninitialized bytes" issues as discovered by valgrind. (Bug #25455825) * After bootstrapping router with the --conf-use-sockets and --directory options, the socket path configuration value defined in the generated configuration file was invalid. This was because it used the socketsdir value in the socket path, but the directory was not created as part of the bootstrap process or when router was started. (Bug #25391460) * On Windows, immediately starting a bootstrapped Router installation would fail to load the generated configuration file. In addition, the generated text for missing configuration files was improved to also include the paths that were checked. (Bug #25343904) On behalf of Oracle MySQL Release Team Balasubramanian Kandasamy
MySQL Shell 1.0.8 RC has been released
Dear MySQL users, MySQL Shell 1.0.8 RC is the first release candidate of the MySQL for MySQL Shell 1.0 series. The MySQL Shell is an interactive JavaScript, Python and SQL command-line interface, supporting development and administration for the MySQL Server. The MySQL Shell includes the X DevAPI that enables developers to use a new Create Read Update Delete (CRUD) API. MySQL Shell is a component of the MySQL Server. This release introduces support for the creation and management of MySQL InnoDB clusters from MySQL servers with the AdminAPI. By taking advantage of the new Group Replication technology, InnoDB clusters provide an integrated solution for high availability and scalability for InnoDB based MySQL databases, without requiring advanced MySQL expertise. And with MySQL Router 2.1, applications can take advantage of a highly available and scalable MySQL InnoDB cluster with minimal or no changes in their code. This is a Developer Release, so we are looking forward to getting your feedback on the MySQL Shell as well as the new API and all the other new features. The MySQL Shell provides * MySQL High Availability and Scaling API: AdminAPI * Both Interactive and Batch operations * JavaScript, Python, and SQL language modes * Document and Relational Models * CRUD Document and Relational API: DevAPI * Output results in Traditional Table, JSON, and Tab Separated formats * And much more To download the MySQL Shell http://dev.mysql.com/downloads/shell To learn more about MySQL Shell, a component of the MySQL Server, see http://dev.mysql.com/doc/refman/5.7/en/mysql-shell.html To learn more about using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html For MySQL Shell Tutorials JavaScript - http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-javascript.html Python - http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-python.html User documentation for the X DevAPI http://dev.mysql.com/doc/x-devapi-userguide/en/index.html For more information about how the X DevAPI is implemented in MySQL Shell, and its usage, see http://dev.mysql.com/doc/dev/mysqlsh-devapi/ User documentation for InnoDB cluster which can be administered using the AdminAPI included with MySQL Shell: https://dev.mysql.com/doc/mysql-innodb-cluster/en/ == Changes in MySQL Shell 1.0.8 (2017-03-06) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * The URI is now a positional argument when starting MySQL Shell at the command line. (Bug #25077429) * In the MySQL Shell Python X DevAPI implementation the mysqlx and mysql modules have been moved into the new mysqlsh module. This changes the way you import the modules, now you should issue: mysql-py> from mysqlsh import mysql mysql-py> from mysqlsh import mysqlx (Bug #25030138) * XSessions have been removed, which means the --x command option is deprecated. The default session is now a NodeSession. (Bug #24958348, Bug #83553) * The stored sessions functionality has been removed. (Bug #24949016, Bug #83530) * MySQL Shell version 1.0.8 includes the newly released AdminAPI available in JavaScript and Python which enables you to set up and manage InnoDB clusters. It provides a modern fluent API which wraps the complexity associated with configuring, provisioning and managing an InnoDB cluster, without sacrificing power, flexibility or security. Bugs Fixed * When using Python mode, assigning a key element that was identified as a type could cause an unexpected halt. The fix ensures that keys which are strings are correctly identified as such as are interpreted as keys. (Bug #25191539) * Attempting to create a connection with the wrong user or password on Linux resulted in an Error Unknown option trace_protocol message being displayed. The fix ensures that the correct ERROR: 1045 (28000): Access denied for user error is displayed. (Bug #25071433, Bug #83759) * Statements that were not executed, for example due to a syntax error, were not being added to the command history. This has been improved so that any statement is added to the command history and can be accessed using the up and down cursor keys. Additionally the internal MySQL Shell are now added to the command history. (Bug #24967864) References: See also: Bug #24669771. * When MySQL Shell had an open connection and was in SQL mode, pressing Control-C caused an unexpected halt. (Bug #24812731) References: See also: Bug #24663772, Bug #23065126. * The output of the \help command has been updated to
