Install and Run Apache Roller 4.01 on GlassFish and OpenSolaris
Dave Koelmeyer has posted Detailed Instructions on how to install Apache Roller 4.01 on GlassFish v2.1 using MySQL 5.1 for storage.  He uses OpenSolaris snv_134, the subject of a tea-leaf-reading thread.

Slides and Code Samples on Jersey and JAX-RS
The Slides and code from Paul Sandoz's presentation at Presentation at AlpesJug on Jersey, JAX-RS and Atmosphere are now  …

As I mentioned in my talk An Overview of Flash Storage for Databases I see in the near and middle term future a lot of interest for using Flash storage in Level 2 caching level. The price-capacity trade-off makes Flash as the very good fit for a cache layer.
Actually it is not the new idea, and it was implemented in L2ARC ZFS for two years already.
It is also described in ACM article "Flash storage memory" by Adam Leventhal.

So I am exciting to see it is available for Linux now. Paul Saab and Mohan Srinivasan from Facebook released Flashcache, which allows to use Flash as …

I spent the day today reviewing Dmitry's patch for Bug#46947. When looking at the quick fix, we discovered that MySQL <-> storage engine locking protocol is very weakly defined when it comes to more advanced features, such as subqueries, stored functions, views.
It's badly defined, it's not documented, it's not tested. As a result, some bits of server behaviour flipped back and forth between 4.1, 5.1 and 5.5.

The problem is that when a statement accesses the table via a subquery, view or a function, the lock that the server needs to take on that table is not a function of the SQL in the subquery/view itself, but depends on the context where this view or function is used.
If we use the view in an UPDATE statement, and don't take sufficiently strong locks on its tables or rows, replication may break, or, in some engines, repeatable read consistency get …

The time has come. People keep on asking why there is a practical limit on the number of nodes in multi-master cluster and what is it exactly. So here's some no-nonsense hardcore multi-master math
(hereafter I assume that all nodes in a cluster have the same processing power and load is distributed uniformly between them).

Let's denote the total work that a node can do as W, the work that it doing serving local connections as L and the work that it is doing applying replication events from another node as R. While W is constant, L and R are variable and depend on the number of nodes. Clearly R is an unproductive replication overhead which we don't want to have there, but have no choice.

Then for a single server we have W = L.

For a 2-node cluster we have W = L + R.

For a N-node cluster we have W = L + R×(N − 1).

Let's denote ratio R/L as α. This quantity lies between …

Announcing a new beta 10 release of MySQL Workbench. Version 5.2.20 includes new fixes for 49 bugs (P1 – 1, P2 – 7 , P3 – 39, P4 – 2)

A few new tips you might try. Some have been in the last 2 betas – but in case you haven’t noticed:

1. Once connected in SQL Editor – type control-T or command-T to add a new editor Tab
2. In the SQL Editor run a select. Highlight a cell (one with an image blob preferably) and right click (or command click) and select “Open Value in Viewer” or another option.
3. In a results set — select multiple rows — right click and “copy row content”
4. Click on snippets. Click on the selector and look at DDL and DML lists.
5. Add your own snippets selection drop down option by creating an empty file in the snippets folder and re-opening Workbench.

For example on Windows …

C:\Documents and Settings\<your …

At the most recent MySQL conference many people asked us how we are and planning to scale MySQL. One of the ways we're planning on providing better quality of service to our users is the deployment of our caching module for Linux, Flashcache. Flashcache is a simple write back persistent block cache designed to accelerate reads and writes from slower rotational media by caching data in SSD's.

We built Flashcache to help us scale InnoDB/MySQL, but it was designed as a generic caching module that can be used with any application built on top of any block device. For InnoDB, when the working set does not fit in the InnoDB buffer pool, read latency is significantly improved due to caching more of the working set in faster media, such as SSD's. We also improve write performance by first caching writes in SSD's and lazily flushing the data back to disk.

We hope to share more information about our Flashcache deployment in the future, but …

Recently when talking to someone about PBMS it occurred to me that I had been thinking about BLOBs in the traditional database sense in that they were atomic blocks of data the content of which the server knew nothing about. But with PBMS that need not be the case.

The simplest enhancement would be to allow the client to send a BLOB request to the PBMS daemon with an offset and size to just return a chunk of the BLOB. Depending on the application and the BLOB contents this may make perfectly good sense, why force the client to retrieve the entire BLOB if it only want part of it.

A much more interesting idea would be to enable the user to provide custom server side functions that they could run against the BLOB.

So how would his work?

The PBMS daemon would provide its own "BLOB functions" plugin API. The API would be quite simple where the plugin would register the function names it …

VMware and Salesforce.com launch VMforce. Red Hat provides Cloud Access. And more.

Follow 451 CAOS Links live @caostheory on Twitter and Identi.ca
“Tracking the open source news wires, so you don’t have to.”

# VMware and Salesforce.com launched VMforce, a platform for developing and deploying Java cloud applications.

# Red Hat Cloud Access enables enterprises to use their Red Hat Enterprise Linux subscription on Amazon Web Services.

# Canonical announced Ubuntu 10.04 LTS Server Edition, Desktop Edition and ISV support.

While there is a dizzying array of technologies that have the “NoSQL” label applied to them, I’m looking for one to replace a MySQL cluster. This particular cluster has roughly a billion records in it, uses a few TB of disk space, and is growing all the time. It is currently a MySQL master with several slaves and handles a fairly light query volume. The reasons we’d like to change it are:

• ALTER TABLE takes an unreasonably long time, so we can’t add or removed indexes or columns. Changes take over a month.
• The data footprint is large enough that it requires RAID and we seem to be really good at breaking RAID controllers.
• Queries are not very efficient, due partly to the underlying data organization, and due partly to the sheer amount of it compared to the available RAM.
• The data really isn’t relational anymore, so a document store is more appropriate.  It’s just that when it was set …

SPJ (preview, not production ready) is a new feature allowing some types of JOINs to be pushed down and executed inside the data nodes! This allows for, in many cases, much faster JOIN execution.

Now we would love to get your feedback on this new feature:

• Does what we have right now improve performance for you?
• Are there other types of JOINs we should support in order to improve performance in you application (currently only eq_ref is supported)?
• What application are you using?

There are some limitations currently:

• node failure handling of SPJ is not complete, so if a data node crash, there are side-effects.
• only eq_ref is supported - other JOINs are executed as normal.
• Don't put this in production.
  

Obtaining the MySQL Cluster SPJ preview version:

• You must know how to build MySQL Cluster …