Dear MySQL users,

MySQL Connector/J Version 8.0.15 is the GA release of the 8.0
branch of MySQL Connector/J. It is suitable for use with MySQL Server
versions 8.0, 5.7, 5.6, and 5.5. It supports the Java Database
Connectivity (JDBC) 4.2 API, and implements the X DevAPI.

This release includes the following new features and changes, also
described in more detail on

https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-15.html

As always, we recommend that you check the “CHANGES” file in the
download archive to be aware of changes in behavior that might affect
your application.

To download MySQL Connector/J 8.0.15 GA, see the “Generally Available
(GA) Releases” tab at …

Dear MySQL users,

The MySQL developer tools team announces 8.0.15 as our general available (GA) for
MySQL Workbench 8.0.

For the full list of changes in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-8-0.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?152

The release is now available in source and binary form for a number of
platforms from our download pages at:

http://dev.mysql.com/downloads/tools/workbench/

Enjoy!

A covering index is a fantastic query performance optimization. An index covers a query when the index has all the data needed to execute the query, so the server can retrieve the query’s data without reading any rows or documents. Covered queries are usually SELECT queries, but in addition to reads, indexes can cover portions of what a write query needs to do its work.

In this article I’ll explain what a covering index is in a bit more detail; the technical implementation and caveats in MySQL, PostgreSQL, and MongoDB; and how to check that a query is using a covering index.

What’s a Covering Index?

A covering index, or index-covered query, doesn’t refer just to an index. Instead, it’s the combination of a query and an index: the index covers the query. An index that covers one query might not cover another query, so “covering” doesn’t solely describe the index, …

Dear MySQL users,

MySQL Connector/NET 8.0.15 is the third version to support
Entity Framework Core 2.1 and the fifth general availability release
of MySQL Connector/NET to add support for the new X DevAPI, which
enables application developers to write code that combines the
strengths of the relational and document models using a modern,
NoSQL-like syntax that does not assume previous experience writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more information about how the X DevAPI is implemented in Connector/NET, see
http://dev.mysql.com/doc/dev/connector-net. NuGet packages provide functionality at a project …

Dear MySQL users,

MySQL Connector/ODBC 8.0.15 is a new version in the MySQL Connector/ODBC 8.0 series,
the ODBC driver for the MySQL Server.

The available downloads include both a Unicode driver and an ANSI driver based on the
same modern codebase. Please select the driver type you need based on the type of your
application – Unicode or ANSI. Server-side prepared statements are enabled by default.
It is suitable for use with any MySQL server version from 5.5.

This release of the MySQL ODBC driver is conforming to the ODBC 3.8 specification.
It contains implementations of key 3.8 features, including self-identification
as a ODBC 3.8 driver, streaming of output parameters (supported for binary types
only), and support of the SQL_ATTR_RESET_CONNECTION connection attribute (for the
Unicode driver only).

The release is now available in source and binary form …

Dear MySQL users,

MySQL Shell 8.0.15 is a maintenance release of MySQL Shell 8.0 Series
(a component of the MySQL Server). The MySQL Shell is provided under
Oracle’s dual-license.

MySQL Shell 8.0 is highly recommended for use with MySQL Server 8.0
and 5.7. Please upgrade to MySQL Shell 8.0.15.

MySQL Shell is an interactive JavaScript, Python and SQL console
interface, supporting development and administration for the MySQL
Server. It provides APIs implemented in JavaScript and Python that
enable you to work with MySQL InnoDB cluster and use MySQL as a
document store.

The AdminAPI enables you to work with MySQL InnoDB cluster, providing
an integrated solution for high availability and scalability using
InnoDB based MySQL databases, without requiring advanced MySQL
expertise. For more information about how to configure and work with …

We are happy to invite you to the upcoming MySQL Meetup in Dubai. Please find details below:

• Date: Wednesday, February 13, 2019
• Time: 7:30-9:30 pm
• Place: Oracle Office Building 6 Internet City, Room Jumeirah (map)
• Agenda: MySQL Clustering and how to make the database "High Available" -> with focusing on MySQL InnoDB Cluster (8.0) and MySQL NDB Cluster (7.6), speaker: Ted Wennmark, the MySQL Cluster Specialist
• More information

We are looking forward to seeing you all there!

The MariaDB Foundation is pleased to announce the availability of MariaDB 10.0.38, the latest stable release in the MariaDB 10.0 series, and also the final in the maintenance window, as well as MariaDB Connector/J 2.4.0, the latest stable MariaDB Connector/J release, and MariaDB Connector/Node.js 2.0.3, the first stable release of the 100% JavaScript non-blocking MariaDB […]

The post MariaDB 10.0.38, MariaDB Connector/J 2.4.0 and MariaDB Connector/Node.js 2.0.3 now available appeared first on MariaDB.org.

We continue with announcing the upcoming shows & conferences where you can find MySQL Community or MySQL Experts at. Please find the list of events with details below. 

February 2019:

• FOSDEM 2019, Brussels, Belgium, February 1& 2-3, 2019

  • MySQL is again part of FOSDEM. Again this year with a MySQL booth & the whole day of MySQL dedicated talks in the MySQL track, see schedule here. There is also MySQL Pre-Fosdem Day followed by MySQL Pre-Fosdem Dinner, both planned for February 1, 2019. See more details in Fred Descamps' blog.
  • We are really looking to meeting you at this biggest OS show …

Introduction –

Recently i worked on a production issue for one of our client under support .They have a architecture of a three node Galera cluster with one asynchronous slave .

• Node1 – 172.10.2.11
• Node2 – 172.10.2.12
• Node3 – 172.10.2.13
• Replica – 172.10.2.14

Architecture –

The slave(replica) was configured with node3 as replica master. Unfortunately the node 3 was crashed with an OOM killer ,also server has a low gcache size, so when i am trying to start the node 3 , it went to SST . Here the data size was around 2.6 TB , in general for completion of whole SST and joining the node back to cluster will take around  approximately 12 hours.

As i told earlier, the replication slave was under …