Podcasts Learning Performance

This episode we start a 2-part series on MaxScale, a scaling proxy for MySQL. Ear Candy is OS Query and At the Movies is about MaxScale.

Relational databases aren’t very well suited to time-series data in some ways, but MySQL is powerful and flexible. At VividCortex, we have found that it’s a good storage engine to support a large-scale, high-velocity time-series database in the AWS cloud.

Join us next Tuesday, December 9, at 2 PM EST (7 PM GMT) as Baron Schwartz, our CEO and Founder discusses our unique time-series data requirements. He will explain the following:

• How we built a solution using MySQL and additional components such as Redis
• Why we needed more than just MySQL to meet the requirements
• The good and bad aspects of our architecture
• Performance statistics
• Thoughts for the future of our time-series data architecture

You will leave the talk with a greater understanding of MySQL’s capabilities related to time-series data. Please register …

Podcasts Learning Performance

This episode we start a 2-part series on MaxScale, a scaling proxy for MySQL. Ear Candy is OS Query and At the Movies is about MaxScale.

Amazon recently announced RDS Aurora a new addition to their database as a service offerings. Here’s Mark Callaghan’s take on what’s happening under the hood and thoughts from Fusheng Han. Amazon is uniquely positioned with RDS to take on offerings like Clustrix. So it’s definitely worth reading Dave Anselmi’s take on Aurora. Join 28,000 others […]

1) Is mysqldump text backup or binary backup
It is a text backup . If you open the backup file you will see all the statements that can be used to recreate databases and objects . It also has the insert statements to populate the tables with data

2) What is the syntax for mysqldump ?
mysqldump -u [uname] -p[pass] –databases [dbname][dbname2] > [backupfile.sql]

3) How to backup all databases using mysqldump ?
mysqldump -u root -p –all-databases > backupfile.sql

4) How to backup specific databases using mysqldump ?
mysqldump -u root -p –databases school hospital > backupfile.sql

5) How to backup specific tables using mysqldump ?
mysqldump –user=root –password=mypassword -h localhost databasename table_name_to_dump table_name_to_dump_2 > dump_only_two_tables_file.sql

The Perfect Server - CentOS 7 x86_64 (nginx, Dovecot, ISPConfig 3)

This tutorial shows how to prepare a CentOS 7 x86_64 server for the installation of ISPConfig 3, and how to install ISPConfig 3 on it. ISPConfig 3 is a webhosting control panel that allows you to configure the following services through a web browser: nginx web server, Postfix mail server, MySQL, BIND nameserver, PureFTPd, SpamAssassin, ClamAV, Mailman, and many more. Since version 3.0.4, ISPConfig comes with full support for the nginx web server in addition to Apache; this tutorial covers the setup of a server that uses nginx, not Apache. The ISPConfig 3 apache perfect server tutorial is available here.

In July, I first wrote that we are currently working on a new data dictionary for MySQL. We have since shipped a labs release where you can try it out for yourself and then send us feedback!

Today, I wanted to write about our upgrade plan from the old data dictionary to the new data dictionary. Or more specifically, explain one of the nuances that we currently have with encoding characters that are not safe on all filesystems.

To quote from the MySQL manual:

For example, if a …

By default in MySQL 5.6, each time MySQL is started (regular start or crash recovery), it iterates through all the binlog files when GTIDs are not enabled. This can take a very long time if you have a large number of binary log files. MySQL and Percona Server 5.6.21+ have a fix with the simplified-binlog-gtid-recovery option. Let’s explore this issue.

Understanding the issue

It was first reported by Yoshinori @ Facebook (bug #69097).

Let’s start by looking at a MySQL 5.6 instance where binary logging is enabled but GTIDs are disabled.

If we restart MySQL with strace, we’ll see:

# strace -e open service mysql start
[...]
open("/var/lib/mysql5621/mysql-bin.000004", O_RDONLY) = 13 …

Many of VividCortex’s customers have strict policies about Internet access from and to their database servers. As a longtime consultant who worked on many servers that lacked a direct connection to the Internet, I anticipated this. Since the beginning, VividCortex has been designed to work in deployment scenarios without requiring direct Internet access, and requiring no inbound access at all.

At the same time, the best way to trust what an agent-based system is sending off your servers is to inspect it. But VividCortex is designed for end-to-end encrypted access; our APIs are 100% JSON over HTTPS, with no non-HTTP access permitted anywhere on any of our web properties. How can a customer inspect the traffic from agents to APIs if it’s encrypted?

It turns out that an HTTP proxy is the solution to both of these situations. You simply configure the agents to talk to the proxy, and the proxy relays traffic from and to the API. …

Hey,

Did you check the mysql.log file for errors ? Its the best place to figure out silly mistakes that we generally make.