'stop')

echo -n 'Are you sure? (y|N)';
read SANITYCHECK;
if [ $SANITYCHECK != 'y' ]; then
echo "EXITING INPUT NOT y";
exit 1;
fi



Why? Well imagine you have 20 servers running mysql for the site. You spent 100K to get these servers redundant, automatically failover if a few go down-which gets the company a High Availability score of 99.999% in the database backend and then someone runs

dsh -N ALL_MY_DB_SERVERS /etc/init.d/mysql restart

when the intention was to restart another process like say the monitoring process.



DOH!!

Back in January I posted a simple MySQL duplicate index finder tool. Because I read requests for such a tool on the MySQL Performance Blog I decided to open a new project on Google's code hosting service as well as a new blog to track it.

So if you are interested and maybe even want to contribute to it, go have a look.

After a successful training (teaching) week, I'm on my way back home.
I also had a chat at AuckLUG (facilitated by the Auckland Novell
offices) and got invited to an "NZ 2.0" meeting at Galbraith's
brewhouse by Nat Torkington. That was particularly interesting.

Airports are always good fun, lots of computers and other signs at
work. On the way in the main arrivals/departures displays were low on
virtual memory (photo attached), one the way out I saw a shop
advertising LCD tell that its Norton Antivirus subscription had
almost expired and that it had protected against 78000 viruses
already (how can that box possibly be so exposed?) and another screen
in the departure lounge displayed a blue screen of death. Not picking
on Auckland, this is pretty typical. Sigh.

There was also a sign on a garbage bin saying "no spitting, please
use …

After a successful training (teaching) week, I'm on my way back home.
I also had a chat at AuckLUG (facilitated by the Auckland Novell offices) and got invited to an "NZ 2.0" meeting at Galbraith's brewhouse by Nat Torkington. That was particularly interesting.

Airports are always good fun, lots of computers and other signs at work. On the way in the main arrivals/departures displays were low on virtual memory (photo attached), one the way out I saw a shop advertising LCD tell that its Norton Antivirus subscription had almost expired and that it had protected against 78000 viruses already (how can that box possibly be so exposed?) and another screen in the departure lounge displayed a blue screen of death. Not picking on Auckland, this is pretty typical. Sigh.



There was also a sign on a garbage bin saying "no …

In my experience there has been a driving factor, a mindset of those who make the purchasing decisions and are not necessarily technically knowledgeable, that the value of an item somehow equates to the money spent acquiring it. A company I worked for years ago catered to this mindset by way of pricing their product according to factors such as speed, capacity, and price of the target computer. The same software was delivered to all customers, but the understanding was that owners of computers would somehow expect software to be valued in relation to their computer. Owners of expensive computers would expect to have to purchase expensive software for it, and distrust something viewed as too cheap, whereas owners of lower priced systems would not want to pay as much for the software by the same token.

Times have changed but the value/price mindset continues. One place I was at a few years ago seemed caught up in the mindset. They hired …

After I mentioned in this blog posting a week ago that I’d make an announcement on August 28 concerning my future priorities, I received different reactions. Mostly there seems to be a lot of understanding and appreciation for what I’ve contributed to the fight for balanced patent policy, and that’s great. But some people misunderstood my remark: the decision hasn’t been taken yet, and it’s not an appropriate point in time to say which outcome is more likely because a lot can still happen in one week. Come August 28, I’ll decide and announce.

What transpired from of the responses isn’t really a surprise: to many people I’m simply “Mr. NoSoftwarePatents” because that’s the context in which they first came to know me. My backgrounder …

Looking at the list of referrers for this blog, I found one coming from Mike Kruckenberg. First of all it is a nice post to read for anyone who (has to) work with databases, so be sure you take a look.

Moreover I learned about LogBuffer which I did not know before. So if anyone else dealing with databases does not know it yet, maybe you will it as interesting as I did.

I've released version 0.1.146 of the innotop MySQL and InnoDB monitor. You can download innotop from the original article.

I re-arranged some information to be more compact and readable in this version, but there isn't really much new functionality. This is mostly a bug-fix release to prevent crashes when innotop encounters unexpected information, or doesn't find some information it expects to exist. It's still very much beta software, so it may die unexpectedly. See this article about what information I need to debug and fix crashes.

Crashes should not cause any loss of information or other problems, by the way. It's completely safe to run, because it doesn't modify anything, it just reads status information. Up till now I've preferred …

There are whole books on the subject about building a great design that is scalable and portable among developers and or administrators.

Then there are whole books on the subject of capacity and scalability for the database layer.

Then there are novels from developers that in many cases really don't know the tricks of the DBMS they are working with, and create elaborate abstraction layers that automatically generate SQL for the DB in question from objects and such.

But, with all these people who tell you how to do it, actually can they prove that it works under a constant high workload for many people all at the same time.

I can boast this. Flickr does over 4 BILLION+ queries per day, 2 BILLION of which are SELECTS. Most of our data is REAL TIME queries from the database layer. We don't do any fancy tricks to dedicate resources to API calls to certain servers; they hit the SAME servers …