Out of Sync: Maddy's Blog

Once the OSes became open source, it is quite natural that other applications sitting on top of it will follow suit. And what better place to start than one of the most expensive of them all - Databases!

http://www.theregister.co.uk/2008/07/18/facebook_cassandra_microsoft/

Since the pioneers among the web 2.0 companies realized that those oh-so-prohibitively-expensive  proprietary DBs don't scale up nor can they waste precious $s on licenses, they have/are building their own database products. It is obvious that releasing them as products serves a much larger purpose and are in the race to open their code for others to adapt!

The perfect way to start the race would be a (for Tamil movie buffs) a P.S. Veerappa style "Sabash! Sariyana potti!".

Peter Eisentraut, a core contributor to PostgreSQL is joining Sun!  To quote from his blog post:

"Sun has been a valuable contributor to the PostgreSQL project for a number of years now, and I am looking forward to joining them in this effort. I am glad that I will be able to continue my personal role in the PostgreSQL project with the support of the great resources that Sun provides."

Beat that for choice - even with our acquisition of MySQL, you still have a choice, as always!

If you are the kind of datacenter customer whose database and application server deployments are limited by the license fees based on core count, then you have the perfect solution from Sun that frees your data centre from core count and your mind from license worries by going for the unlimited Glassfish + MySQL deployment for a flat fee based on the number of employees.

For a comparison of the TCO, check the details here.

Of course for additional HA capabilities including DR, you can use Solaris Cluster with its robust monitoring, low costs and excellent stability.

I am encountering data corruption every time MySQL is restarted.  The restart is done through scripts and I encounter the following error:

 myisamchk: MyISAM file /global/mysql/mysql/db.MYI

myisamchk: warning: 1 client is using or hasn't closed the table
properly

MyISAM-table '/global/mysql/mysql/db.MYI' is usable but should be fixed

 After  I googled, I found that running myisamchk  on the table was the most commonly provided solution and tried it:

bash-2.05#  /opt/mysql/mysql/bin/myisamchk -r /global/mysql/mysql/db.MYI

- recovering (with sort) MyISAM-table '/global/mysql/mysql/db.MYI'

Data records: 6

- Fixing index 1

- Fixing index 2

bash-2.05# echo $?

0

 but the  problem resurfaces every time the DB is restarted!!

 Got ideas?