jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Klimetschek <aklim...@adobe.com>
Subject Re: AW: Functionality to store indexes in database with jackrabbit 2.1.2 or upcoming releases.........
Date Mon, 29 Nov 2010 11:57:35 GMT
On 29.11.10 12:47, "Seidel. Robert" <Robert.Seidel@aeb.de> wrote:

>I think, the use-case is the same, that we have::
>Multi cluster environment - only one single Lucene index within the
>database for all nodes would
>    -> takes less disk space (if you have more than one node)
>    -> make backups easier (you only have to backup the database, not the
>db and some folders on three nodes)
>    -> makes it easier to add nodes (you don't have to wait, until the
>index is built up)
>    -> make the index more stable (because the database is transactional)

Ok, makes sense, but this would be an optimization purely for writes. I
would expect that the benefits are completely offset by the much worse
read performance of this setup.


Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel

View raw message