Showing entries 7241 to 7250 of 22245
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: MySQL (reset)
Log Buffer #348, A Carnival of the Vanities for DBAs

With the holiday season fast approaching (or is it slow?), data bloggers have already adopted a festive mood, and this Log Buffer edition jubilantly captures and reflects that, and much more.

Oracle:

On December 4, 2013, Oracle will host a customer webcast to acquaint customers with the Oracle SuperCluster M6-32, Oracle’s most powerful engineered system for in-memory Oracle Database performance, Database-as-a-Service and application consolidation.

The ETL logic in BI Apps uses parameters in packages, interfaces, load plans, and knowledge modules (KM) to control the ETL behaviors.

[Read more]
To be safe or to be fast?

When I designed first version of JSON UDFs which was reviewed only internally, I let all functions to validate input and output JSON. But my colleagues told me to remove this functionality, because it makes such functions, as json_search, json_replace or json_contains_key deadly slow if they find the occurrence in the beginning of the long document. And first published version of JSON UDFs: 0.2.0 has not this functionality. What we expected is that users would call json_valid if they want to be 100% sure the document is valid.

But I was not surprised that some users expect JSON functions to work as it was in the first version: validate first, then process. For example, Ammon Sutherland writes: "json_set - according to the documentation a sort of 'INSERT... ON DUPLICATE KEY UPDATE' function which …

[Read more]
Percona XtraBackup – A workaround to the failed assertion bug

I recently conducted a test backup of my “master-slave” setup in my VirtualBox as I was migrating from Percona Server 5.6.12 to version 5.6.13-rel61.0 with Percona XtraBackup v2.2.0 rev. 4885. However, doing the backup on my slave, I encountered this problem:

[04] Compressing and streaming ./test/checksum.ibd
[01] Compressing and streaming ./mysql/slave_master_info.ibd
Assertion "to_read % cursor->page_size == 0" failed at fil_cur.cc:293
innobackupex: Error: The xtrabackup child process has died at /usr/bin/innobackupex line 2641.

This is related to a bug posted by my colleague George  …

[Read more]
How to Enable MySQL Event Scheduler

You may think that you already know what's the opposite of "DISABLED", but with MySQL Event Scheduler you'll be wrong.

In fact MySQL Event Scheduler may have three different states[1][2]:

DISABLED -  The Event Scheduler thread does not run [1]. In addition, the Event Scheduler state cannot be changed at runtime.
OFF (default) - The Event Scheduler thread does not run [1]. When the Event Scheduler is OFF it can be started by setting the value of event_scheduler to ON.
ON - The Event Scheduler is started; the event scheduler thread runs and executes all scheduled events.

So if you're going to find it in the DISABLED state and instinctively set it to ENABLED you'll end up with a non-starting MySQL daemon.
Be warned and stay safe out there!


[1]: http://dev.mysql.com/doc/refman/5.5/en/events-configuration.html
[2]: When the Event Scheduler is not running does not appear …

[Read more]
how MySQL engineering broke the backups

MySQL has exceptional track of record by introducing minor fixes that cause major breakages. Though usually I could blame naiveté of engineers, who did not really ever have to deal with production implications, but lately I can start sensing various business implications against open-source offerings.

As an original author of mydumper I really cannot get out of my mind that 5.5 and 5.6 metadata locking changes are there to screw with anyone who is building a backup solution using stable snapshot views of MySQL (for example, mysqldump –single-transaction, the golden standard of backing things up in MySQL world).

As seen in a bug #71017 (palindrome!) filed by my esteemed colleague Eric, newly introduced behaviors …

[Read more]
Thanksgiving Offer – 20% off on all products

Thanksgiving is almost here. We would like to take this opportunity to thank all our users, customers, corporate clients and fans of SQLyog, MONyog for all the support over the years.

We thought we’d get the festivities started a little early by offering a 20% flat discount on all Webyog products. Offer expires on November 27, 2013 at 23:59 PST. Grab the offer before it’s gone.

Head right away to the Online Shop and apply the coupon code: tg2013.

Cheers,
Team Webyog

Tweet

The post Thanksgiving Offer – 20% off …

[Read more]
How to store MySQL innobackupex backups at Google Cloud Storage

In general, I chose Google Cloud Storage to store web sites MySQL backups due to its price and speed of upload/download in real time

I used the Google native tool – gsutil , innobackupex and some bash

in short : the /etc and local MySQL  backup

#!/bin/sh
# Barcelona Tue Nov 22 17 16:30:36 CEST 2013

days_to_keep=3
NFS=/home/mysql.backups/
exportDate=`date +%Y-%m-%d.%H.%M.%S`
export_DIR=${NFS}/${HOSTNAME}.${exportDate}
test ! -d "${export_DIR}" && echo "$(date) : creating ${export_DIR}" && mkdir -p "${export_DIR}"
export_MySQL_DIR=${export_DIR}/mysql.bckp
export_ETC_DIR=${export_DIR}/etc.bckp
# backup the /etc directory
rsync -avh …
[Read more]
MySQL Connector/Python v1.1.3 beta

Connector/Python v1.1.3 is available for testing since last week. It is a “beta” release, so it would be great if we even get more feedback. Check out the Change History if you want to keep up with what is being added and changed.

Notable changes for v1.1.3 include a fix for encoding using \x5c or backslashes in multi-byte characters. We also made the code more PEP-8 compliant, which we think is quiet important.

Some useful links:

[Read more]
Yikes! 48 CPU cores needed for mysql 5.6!!!

Now this is really getting to be ridiculous. Finally was able to obtain a machine with 24 cores (48 with HT) and ran benchmarks. My colleague was able to come fairly close to Dmitri’s 500K numbers. I was getting nowhere with a 12 core (24 with HT) machine, as MySQL 5.5 was routinely faster in simple readonly sysbench benchmarks (both point queries and range selects). If I have to go to management and ask for these types of machines, they would be justified in sending me off to the funny farm.

Yikes! 48 CPU cores needed for mysql 5.6!!!

Now this is really getting to be ridiculous. Finally was able to obtain a machine with 24 cores (48 with HT) and ran benchmarks. My colleague was able to come fairly close to Dmitri’s 500K numbers. I was getting nowhere with a 12 core (24 with HT) machine, as MySQL 5.5 was routinely faster in simple readonly sysbench benchmarks (both point queries and range selects). If I have to go to management and ask for these types of machines, they would be justified in sending me off to the funny farm.

Showing entries 7241 to 7250 of 22245
« 10 Newer Entries | 10 Older Entries »