I'm pleased to announce the release of Spider storage engine
version 2.27(beta) and Vertical Partitioning storage engine
version 0.16(beta).
Spider is a Storage Engine for database sharding.
http://spiderformysql.com/
Vertical Partitioning is a Storage Engine for vertical
partitioning for a table.
http://launchpad.net/vpformysql
Please use the following for downloading binary file.
http://spiderformysql.com/download_spider.html
The main changes in this version are following.
Q4M is bundled for Linux 64bit.
Bundled Q4M supports replication, but please use it
carefully.
Spider
- Support R-Tree index.
- Support direct updating for SQL …
[...] Continuing the review of MySQL Connector/J’s built-in extension points from my recent JavaOne and Silicon Valley Code Camp presentations, this blog posting will focus on the StatementInterceptor extension point. As the name suggests, this allows you to hook into statement execution and alter behavior – without changing application-side code. This corresponds to slide #59 in my slide deck, and there are two Java files we’ll reference: demo.connectorj.StatementInterceptorExample demo.connectork.plugins.ExampleStatementInterceptor To implement a statement interceptor, you need to do the following: Create a Java class which implements com.mysql.jdbc.StatementInterceptorV2 Configure Connector/J to use your statement interceptor by passing the fully-qualified class name as the value for the “statementInterceptors” property. This extension point is stackable – you can create multiple statement interceptors, passing them in as …
[Read more]
Typical MySQL environment involves one Master receiving writes
and multiple slaves to scale the reads. The “slave” term has been
used in MySQL because the Slave servers have to perform every
task in copying from the Master binlog, then updating their relay
logs and finally committing to the Slave databases. The Master
plays no role in replication here other than storing the
replication events in the binlog.
With this kind of Master- Slave set up, there are several
limitations-
- Slave lag
- Stale or old data
- Data loss
- Manual failover which is
error-prone and time consuming
In SchoonerSQL, there is no concept of “Slaves” inside
synchronous cluster. We refer to it as "Read Masters" because of
our synchronous approach and different replication architecture.
It is …
For me, next week’s Percona Live is a lot like other events: I know I will be busy meeting and greeting and helping unpack boxes and so forth, but I’ll also be talking and attending other talks. With five concurrent tracks, it’s tough to decide. This is roughly the equivalent of the MySQL conference every year, which has more tracks, but historically it’s been easy to cross off some talks as sales pitches.
The Caryatids on the south porch of the Erechtheion (420 BC), Athens, Greece
I suppose I should probably say “MariaDB στην Ελλάδα” which, according to Google Translate, is Greek for “MariaDB in Greece”. We’re still finalizing the arrangements, but I’m pleased to announce that the next Monty Program-sponsored MariaDB Developer Meeting will be held in (or near) Athens, Greece. Update: See below for hotel/location information.
Monty Program tries to hold two MariaDB Developer Conferences / Monty Program company meetings each year. The most recent one was held in Portugal this past March and it’s past time for another one. Monty Program is a virtual company with employees scattered all around the world, and these meetings give us a chance to both get together with each other and to …
[Read more]
I will be a speaker at Percona Live - London 2011, and I am looking
forward to the event, which is packed with great content. A
whopping 40 session of MySQL content, plus 3 keynotes and 14
tutorials. It's enough to keep every MySQL enthusiast busy.
Continuent speakers will be particularly busy, as between me
and Robert Hodges, we will be on stage four times
on Tuesday, October 25th.
|
If you’re using MySQL and SSL, you might want to glance over this article and give your setup a quick test.
I’ve uncovered an alarming bug in 5.5 where one could gain access to your MySQL instance just knowing the username and password (not having any SSL certificate, key, etc.)!
Of course, I’ve filed a bug about it here:
http://bugs.mysql.com/bug.php?id=62743
It’s been over 4 days now, and not one comment from the MySQL Bug/Dev Team.
So once again, I feel the need to share this bug with the public, in case you are using SSL with 5.5, and think your connections are secure, or that only users with the certs/key could gain access.
For SSL Users, you’ll already have this set up, but for those who don’t, I’ve simply got mysqld (5.5.15 and 5.5.16 thus far) running with the following options:
ssl-ca = …[Read more]
The MySQL errorlog is an important point of reference when administering a MySQL Server. We can grasp much about the state of our MySQL instance by the informational and error messages written out to it by our MySQL daemon. Our monitoring suite is set up to check the mysqld error log file periodically for any new nasties logged and then it alerts us if there’s anything to know about. Recently I was asked to investigate some replication outage alerts a colleague had received overnight. One of the primary directions I took was the error log file. This is where I would expect find any evidence of replication being stopped or crashes etc – I was looking for anything that could fill me in on the causes of replication alerts. When I ran the command to tail the log I was shocked to see the log was totally empty.Confused with what I didn’t see, I listed the file info and saw that the file was located in the …
[Read more]The information here was adapted from the AskMonty Knowledgebase.
There are two main parts to MariaDB and MySQL: The mysqld server and whatever client you use to interact with the server. The server is absolutely essential and must remain up and running. mysqld is normally very reliable, but there are rare occasions when it will fail. When mysqld fails hard (or core dump) it will, by default, write a stack trace in the 'hostname'.err file in the database directory. However, in some cases this is not enough to find out exactly what happened.
If you ever run into a situation where mysqld crashes and the 'hostname'.err file does not contain enough information for your DBA or support provider to diagnose the problem, you may need to use what is known as a "debug" build to produce a "full stack trace" and a core file. …
[Read more]That’s actually a pretty cool and handy feature. I never knew these Interceptors were available, but I don’t do much Java programming these days.