Showing entries 16986 to 16995 of 44076
« 10 Newer Entries | 10 Older Entries »
wsrep patch 23.5 for MySQL 5.5.23 released

This is an important feature and security release.

Bugfixes:

  • merged with upstream MySQL 5.5.23 (security bugs fixed in 5.5.22 and 5.5.23)
  • IO cache was not reset on trx cleanup if the writeset was empty
  • ALTER TABLE RENAME and row deletion could conflict on slave
  • slave applier can fail for exceeded max_allowed_packet size
  • clustered index not included in key set
  • locking session can deadlock multi-master

New experimental features:

  • Runtime consistency check support.
  • Hard crash recovery support (global transaction ID can be recovered by running 'mysqld --wsrep-recover')
  • MyISAM storage engine support (non-deterministic functions unsupported, use wsrep_replicate_myisam to enable)
  • Solaris 11 x86 build support (see …
[Read more]
Designing a HTTP JSON database api

A few weeks ago I blogged about the HTTP JSON api in Drizzle. (See also a small demo app using it.) In this post I want to elaborate a little on the design decisions taken. (One reason to do this is to provide a foundation for future work, especially in the form of a GSoC project.)

Looking around: MongoDB, CouchDB, Metabase

read more

Impressions from Amazon's AWS Summit in NYC

Yesterday (4/19) I attended the AWS Summit in NYC (http://aws.amazon.com/aws-summit-2012/nyc).

I'm a big fan and also a heavy user of AWS especially S3, EC2, and naturally, RDS. In every point in time I have several dozens of AWS machines running for me out there in the East region, and in some cases when we do some special benchmarks and tests, number of EC2 and RDS machines can easily reach 3-digit. As I said, I'm a fan...

A few quotes I was able to catch and document on my laptop, on my laps...:
"When you develop an app for facebook, you must be prepared (and be afraid) that to your party, not noone will show up, but everybody will show up!" So true! Simple and true. We all want to succeed, to have success with our app. We have to think about scaling from day 1.
"Database was bottleneck for building of sophisticated apps. This is …

[Read more]
Dedicated table for counters

There are a few ways to implement counters. Even though it’s not a complex feature, often I see people having problems around it. This post describes how bad implementation can impact both application and MySQL performance and how to improve it.

A customer asked me for help with performance problem they were facing. I logged into their database and found many client connections waiting for table locks. Almost all threads were stuck on one, small table called hits. What was the reason?

The problem was related to the way they developed a very simple system for counting page views they later used in some reporting. The table structure was:

mysql> SHOW CREATE TABLE hits\G
*************************** 1. row ***************************
Table: hits
Create Table: CREATE TABLE `hits` (
`cnt` int(11) NOT NULL
) ENGINE=MyISAM

mysql> SELECT * FROM hits;
+---------+
| cnt     |
+---------+
| 3823273 |
+---------+

[Read more]
How Galera does Rolling Schema Upgrade, really

This post is about a fairly technical detail of how Galera works. I'm writing it down in preparation for testing this feature so that I can agree with Alex whether to file a bug or not. I'm sharing it on my blog just in case someone else might benefit from learning this.

Galera 2.0 introduces rolling schema upgrades. This is a new way to do non-blocking schema changes in MySQL.

As the name suggests, it is done as a rolling upgrade. Having seen clusters doing rolling upgrades before, I assumed this is what happens:

  • Execute alter table on Node 1.
  • Node 1 is removed from the cluster and stops processing transactions.
  • Node 1 completes alter table.
  • Node 1 re-joins cluster and catches up so that it is in sync.

read more

Meet GreenSQL @ Infosecurity Europe 2012

Join GreenSQL at Infosecurity Europe 2012. Visit the GreenSQL booth J83b at the New Exhibitor Zone for live product demos and your chance to win a very cool tech gadget.

Book an appointment: marketing@greensql.com

See live demos and hear from our expert, GreenSQL’s Founder and CTO, David Maman.

For more information please visit our website: http://www.greensql.com/

MySQL – Alter table-change datatype of column with foreign key

Schema alteration is a big headache especially when it has already reached to production and things get worse when the relations are involved.Below is a short example for altering tables…

The post MySQL – Alter table-change datatype of column with foreign key first appeared on Change Is Inevitable.

mysqldiskusage – to see database disk usage by MySQL Workbench

As we know, MySQL workbench is excellent GUI tool for managing MySQL DB servers, creating ERDs (Data Modelling) and for sql development. But with this GUI tool, we are getting some command-line utilities too like mysqldiskusage, mysqlindexcheck, mysqlfailover, mysqldiff, mysqldbcompare etc., Here, I’m describing mysqldiskusage utility, which is not only displays mysql db usage but … Continue Reading

[Read more]
MySQL Connect Call for Papers, 2 Weeks Left

The MySQL Connect Call for Papers opened last Monday. Thanks to all of you who already submitted conference sessions and BOFs.

The CFP is running until May 6; if you have not submitted session proposals yet, you have about 2 weeks left to do so.

Interested in sponsorship and exhibit opportunities? You will find more information here.

We look forward to hearing from you!

Disabling MySQL Enterprise Monitor Graph

We have setup our database servers to log all slow queries > 2 seconds. This can be done by enabling below from your configuration file or via runtime using SET GLOBAL command.

Append to configuration (my.cnf) under [mysqld]

slow_query_log = on
long_query_time = 2

Using query

SET GLOBAL slow_query_log = on;
SET GLOBAL long_query_time = 2

With this current setup, we filtered all queries from our application running more than 2 seconds. This is a good way to identify slow queries and optimise them.

However, there are also queries from the MySQL Enterprise monitor that were also being logged. In this case, i found out a (2) graph metrics checking every minute for the total backup time (total_time) and total lock time (lock_time). It takes about 3-6 seconds with only about 70 records on table.

To …

[Read more]
Showing entries 16986 to 16995 of 44076
« 10 Newer Entries | 10 Older Entries »