A new version of Kontrollkit is available. Changes are listed here: http://code.google.com/p/kontrollkit/source/list
I have a problem with an easy way to install MySQL via rpm without resorting to specifying the exact point release of MySQL. Presently my local yum repository has versions of 5.0, 5.1,5.4 and 5.5.
If I want to install MySQL Sever, I can just run:
$ sudo yum install -y MySQL-server Setting up Install Process Package MySQL-server-community-5.5.0-1.rhel5.x86_64 already installed and latest version Nothing to do
The issue here is the most current version is installed. If I want to install the most current version of 5.1 for example, I have found no way to specify MySQL-server-5.1, or MySQL-server-community-5.1, I have to specify the point release MySQL-server-community-5.1.40
I suspect there is some internal aliasing that may be possible within rpm’s to support this. I’m seeking help from any rpm experts and would appreciate any feedback.
My current products include:
$ sudo yum list …[Read more]
Last week Tokutek released version 3.0.0 of TokuDB, adding ACID transactions to its list of features. This post discusses an experiment we ran to measure recovery time following a system crash.
In summary, while actively inserting records into a MySQL database using iiBench, we compared the time to recover from a power-cord pull for both InnoDB and TokuDB.
| Storage Engine | Recovery Time |
| TokuDB | 501s (8 min, 21 sec) |
| InnoDB | 18505s (5 hours, 8 min, 25 sec) |
This is by no means an exhaustive look at recovery performance, but does illustrate the benefits of …
[Read more]The bottom line: As both a community member of MySQL, and a service provider, I am not worried about Oracle buying Sun and acquiring MySQL in the process. There is no validity to the argument that Oracle will slow down or stop MySQL development — it is not possible, with various forks already in heavy development, and it is not probable, because Oracle has owned the InnoDB codebase for 4 years and has not slowed that development down.
My bias
I use MySQL, and want to see it continue to be developed. I work for The Pythian Group, providing DBA services to clients running MySQL. Together with my MySQL colleagues at The Pythian Group, the services provided run the gamut from rotating logs, monitoring, performance tuning, designing and implementing and optimizing database architectures and schemas and queries and debugging problems throughout the full stack. The only service we do …
[Read more]I've just finished my benchmark report about InnoDB current hottest internal contentions on the dbSTRESS workload. Since InnoDB-plugin-1.0.4 there is an excellent feature was added by Innobase team to monitor internal mutex lock waits: a compact output of "SHOW MUTEX STATUS" become much more useful then before! and helps greatly to understand InnoDB limits!
I've integrated innodbMUTEX stats within dim_STAT monitoring and was able to see performance limits from completely different axes!
Initial results
Initially I've retested again:
- MySQL Perf-build5
- MySQL 5.4
- InnoDB-plugin-1.0.4
- XtraDB-8
on the same workload and using X4450 server (Intel CPU, 16cores, 16GB RAM (unfortunately all more powerful servers were busy :-)) as well it was sad for me that I've not used the updated XtraDB-8 code during my …
[Read more]There was much rejoicing recently as Google announced a change of heart and decided to release the source code to EtherPad, which it had previously acquired along with AppJet and had planned to shut down.
Krishnan Subramanian at Cloud Ave was certainly happy as it supported his theory that SaaS vendors should offer their software under an open source license or at least open source their app before they shut down.
I’m not going to argue with Krishnan’s first point – in fact I agree that there is a lot of value in SaaS vendors reducing risk and encouraging adoption by making an open source version of their software available. However I am less convinced by the latter argument. There is a fine line between life …
[Read more]The source version for MySQL Cluster 7.0.10 has now been made available at ftp://ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.39-ndb-7.0.10//
This replaces MySQL Cluster 7.0.9.
You can either wait for the binaries to be released or if you’re in a rush then you can find instructions on building the binaries for yourself in the earlier article: “MySQL Cluster 7.0.7 source released“.
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.0.10 (compared to 7.0.9) can be found in the MySQL_Cluster_7_0_10_ChangeLog.
The save-mysql-campaign is a success thanks to
you. Oracle have had to come out with some public promises.. This is an encouraging
start, which shows that we are on the right track, but we have to
keep the pressure up! Thanks for the help so far, but please
continue contacting companies to send emails to the European
Commission (EC). The battle is not over yet!
In this blog I will analyse point by point what Oracle is really
offering.
Before we go into details, what one has to understand is that
Oracle can afford to employ the best lawyers on the planet and,
as the Oracle/Sun/MySQL deal is a big and important deal, we can
safely assume many professionals have worked on those MySQL
promises. We can safely assume that …
You're not scared of writing clusterious code and eavesdropping is your favorite pastime at work? You want to know what's going on in your MySQL Cluster but were afraid asking? The MySQL Cluster Management API can help you!
Below you'll find example C-code that will get you started with MGM API. It's rather dull at first, but imagine you, instead of printing the event information, taking action. Imagine you starting another thread where you run some procedure which tells a monitoring system: "Hey! Some error happend!". Imagine you spending countless hours of clusterious fun with this API!
The example listens for events in 4 categories (Statistic, Info, Error and Checkpoint) with the greatest level of 15. The code only …
[Read more]
We are pleased to announce the availability of the 0.9.5.3 beta
release of InfiniDB Community Edition. This is our initial
beta release and is not recommended for production work.
This release delivers the final content for our GA release, thus
we have moved from an Alpha designation to a Beta designation.
Contents of this release include HAVING clause support and
bug fixes that you can see at http://bugs.launchpad.net/Read
More...