One day on production server I encountered this error message, So I found out a solution for it as:

There are multiple reasons, listed below:

1. You’ve run out of memory available to MySQL.This is the most likely problem you’re facing. Each connection in MySQL’s connection pool requires memory to function, and if this resource is exhausted, no further connections can be made. Of course, the memory footprints and maximum packet sizes of various operations can be tuned in your equivalent to my.cnf if you discover this to be an issue.

You can calculate MySQL memory using this tool – http://www.mysqlcalculator.com/

This shows maximum size a MySQL should use in your environment, in my case it’s a dedicated MYSQL …

This is your very first post. Click the Edit link to modify or delete it, or start a new post. If you like, use this post to tell readers why you started this blog and what you plan to do with it.

Happy blogging!

When a new version of MySQL appears, the first source of information for the brave experimenter is a page in the manual named What is new in MySQL X.X, also known as MySQL in a nutshell. For MySQL 5.7, the in-a-nutshell page lists quite a lot of changes. In that page, the list of removed features is enough to send a chill down the spine of most any DBA. Some of the items in the deprecation section are removals in disguise, as they require immediate, rather than delayed, action to use the new version with existing application (SET …

ScaleDB extends MySQL for high-velocity high-volume data, enabling near real-time analytics across massive streams of data. Like Hadoop, ScaleDB leverages a cluster of commodity machines with low-cost spinning disks for storage, mitigating the typical trade-offs between data fidelity and the volume of data and time analyzed. NoSQL and Hadoop are excellent choices for unstructured data, or data variety challenges. However, if your data is structured time-series data, and generated at high-velocity and high-volume, ScaleDB is the tool for you. On a nine-node cluster, ScaleDB inserts millions of rows per second and queries up to 1000 times faster, more than enough speed for today’s most demanding applications.

ResponsibilitiesLooking for C/C++ experience, ideally with experience with database server internals. You will design and implement a next generation database storage engine. You will have ownership for one or more modules of the …

#DBHangOps 08/06/15 -- Orchestrator and Binlog Servers and more!

Hello everybody!

Join in #DBHangOps this Thursday, August, 06, 2015 at 11:00am pacific (18:00 GMT), to participate in the discussion about:

• Orchestrator and Binlog Servers from Shlomi Noach
• Configuration vs. Orchestration

You can check out the event page at https://plus.google.com/events/ci32euumljnmivfo8kkh9j8kum8 on Thursday to participate.

As always, you can still watch the #DBHangOps twitter search, the @DBHangOps twitter feed, or this blog post to get a link for the google hangout on Thursday!

See all of you on Thursday!

You can catch a …

Baron Schwartz will be speaking on Building Microservices with Go at OSCON EU on October 26th.

Below is an overview;

Go is great for building HTTP and RPC services. VividCortex’s infrastructure is Go-based, and there are a lot of lessons to learn from the experience building it. Here are some of the things we needed to do above and beyond what the standard libraries provide:

• Using net/http effectively
• Building an actually sane REST framework in Go
• Dealing with garbage collection
• Building a build system
• Continuous integration and deployment
• Running services (daemons)
• Runtime inspection of all in-flight requests
• Interacting with databases, caches, and queues
• Building staging and development environments

Baron Schwartz will be speaking on Building Microservices with Go at OSCON EU on October 26th.

Below is an overview;

Go is great for building HTTP and RPC services. VividCortex’s infrastructure is Go-based, and there are a lot of lessons to learn from the experience building it. Here are some of the things we needed to do above and beyond what the standard libraries provide:

• Using net/http effectively
• Building an actually sane REST framework in Go
• Dealing with garbage collection
• Building a build system
• Continuous integration and deployment
• Running services (daemons)
• Runtime inspection of all in-flight requests
• Interacting with databases, caches, and queues
• Building staging and development environments

This is getting more and more common, so I wanted to provide the steps required to get LDAP authentication working with MariaDB PAM plugin.

Unless you’re already familiar with setting up the MariaDB PAM plugin, I’d first recommend getting this to work with a standard Linux user (steps 1-4), then once all is working fine, progress to the LDAP users (steps 5-10). (And if you do not want to test this for the Linux user account, then you may skip steps #2 and #3.)

1. Enable plugin by running the following from the command line client:

   INSTALL SONAME 'auth_pam';

   You should see an entry like this afterward in SHOW PLUGINS:

       | pam | ACTIVE | AUTHENTICATION | auth_pam.so | GPL |

2. Create the mysql user account (note it does not have a password, as it will obtain this from your Linux user, and eventually the LDAP account) and provide it with the GRANTS you want it to …

MySQL 5.7.8-rc2 was released today, and features a new server utility called mysqlpump. This utility contains a number of major improvements over mysqldump including:

• Parallel processing of databases, and of objects within databases, to speed up the dump process
• For dump file reloading, faster secondary index creation for InnoDB tables by adding indexes after rows are inserted
• Better control over which databases and database objects (tables, views, stored programs, user accounts) to dump
• Dumping of user accounts as account-management statements (CREATE USER, GRANT) rather than as inserts into the mysql system database
• Capability of creating compressed output
• Progress indicator

What I wanted to caution however, is that mysqlpump is not currently consistent. …

I’ve had a look at a preview release of MySQL 5.7.8, some time before it became available to the general public (perks and duties of an Oracle ACE) and I found a few interesting things among the release notes and the tarball itself:

• There is a new tool named mysqlpump, which is intended as a replacement for mysqldump, with parallel processing, compression, progress watch, the long awaited ability of excluding databases or tables, and more.
• The json functionality has been fished out from the labs and added to the main distribution.