If you start with the d6 build, you probably have ourdelta.org in your repo files rather than mirror.ourdelta.org. Since we moved to using download mirrors, you need to update your repo config files. There are redirects in place for download users, but yum/apt-get generally don’t like redirects. For details on what your config should now look like, just take a peek at the information for each distro we currently support:

• RHEL/CentOS (4 & 5)
• Debian (4.0 Etch)
• Ubuntu (8.04 LTS Hardy, 8.10 Intrepid)

Once you’ve fixed this up, updates should be painless in the future (i.e., updating to the current d7 …

Understanding the Popularity and Growing Emergence of MySQLFriday, November 14, 2008 8:00 a.m. PSTMySQL is growing at an incredible rate. Daily downloads are 75,000 and growing. More and more organizations are expanding their use of this popular database. This presentation will discuss the growing emergence of MySQL in the database industry. Topics will include:Key factors in MySQL's

FYI, Sun is announcing some sweet new storage stuff on Monday at 3:30pm PT.

I’m reviewing a few of the things they’re announcing, and hope to publish my thoughts here soon (one of them joins my production network tonight if all goes well). However, I’m at Disneyland with my kids (first trip!) from Monday through Thursday, so I don’t know (yet) when I’ll be able to write them up. Bear with me if it takes a few days.

But the gear is exciting, and the direction Sun is headed is even more exciting!

…

I'm definitely looking forward to presenting the MySQL sessions here at the Sun 2008 Customer Engineering Conference (CEC). The conference is at the Paris Hotel here in Las Vegas. The conference starts for me today (Sunday, November 9) with a walk through from 5:00-6:30pm. All the training track managers need to go through the walkthrough. The welcome reception is then at the Paris, Pavilion/

At the European Customer Conference a couple of weeks back, one of the topics was the use of DRBD. DRBD is a kernel-based block device that replicates the data blocks of a device from one machine to another. The documentation I developed for that and MySQL is available here.

Fundamentally, with DRBD, you set up a physical device, configure DRBD on top of that, and write to the DRBD device. In the background, on the primary, the DRBD device writes the data to the physical disk and replicates those changed blocks to the seconday, which in turn writes the data to it’s physical device. The result is a block level copy of the source data. In an HA solution, which means that you can switch over from your primary host to your secondary host in the event of system failure and be sure pretty certain that the data on the primary and seconday are the same.

…

We'll talk about MySQL Sandbox, and about any relevant MySQL topic.

I am currently tasked with writing Software Requirements Specification (SRS) document for a project. Effective sharding (based on specific criterion) and Scalability are key requirements of the project.

Scalability is traditionally classified as a non-functional requirement. My question to the community is that if scalability is crucial to a project, would it still be classified as a non-functional requirement? Are their cases when scalability requirements would be best classified as functional requirements?

<!-- http://4.bp.blogspot.com/_aUgNMQ2wQTE/SUs_eaEFKSI/AAAAAAAAAoQ/FUG8BLpXtF0/s1600-h/Speed_Highway.jpg -->I've just finished taking the (EM-based) Performance Tuning course and the SQL Tuning course. It's always a strange feeling taking a course where I already have hands-on experience, or I was around in the early days when standards were being hammered out. Sometimes that odd feeling (I know

I had an interesting tuning case few days ago. The system serving high traffic using Innodb tables would be stalling every so often causing even very simple queries both reads and writes taking long time to complete, with progress almost paused (dropping from thousands to tens of queries per second).

On the surface the problem looked simple - in the processlist every so often you would see a lot of queries, mostly selects taking 10+ seconds while at the same time there was no significant iowait, neither high CPU usage. Closer examination showed there were hundreds of queries stuck in the innodb queue, with innodb_thread_concurrency set to 8

Happily enough innodb_thread_concurrency is the variable which can be set online so it is easy to try a few different values and see what works best. In this case we decided to try removing restriction on runnable queries all together by setting it to 0.