Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <e176788c0708270615h77269c01r6b5729d1c19e0cd@mail.gmail.com>
Date: Mon, 27 Aug 2007 15:15:49 +0200
From: "Dominique Pfister" <dominique.pfister@day.com>
Sender: dpfister@day.com
To: users@jackrabbit.apache.org
Subject: Re: jackrabbit clustering
In-Reply-To: <12310826.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20070813153251.250840@gmx.net>
	 <e176788c0708140006y6e4cf6ddq25128c15e961b39f@mail.gmail.com>
	 <12310826.post@talk.nabble.com>

Hi Hanno,

On 24/08/07, hjonas <hanno@rastaduck.org> wrote:
> Let's say we don't need transactional behaviour, would it be possible to use
> a shared filesystem folder (NFS) to store BLOBs? If yes, what configuration
> would be needed in such a case?

You're probably referring to the following setup: having a database
persistence manager that stores its blobs in the filesystem
(externalBLOBs=true). In this scenario, blobs are stored in a
directory named "blobs", located in either
${rep.home}/workspaces/${wsp.name} for workspaces or
${rep.home}/version for versioning. Unfortunately, this directory name
and location is not configurable, probably a good candidate for some
enhancement! Anyway, after having started my repository for the first
time, I renamed the BLOBStore's "blobs" directory and created a
symbolic link named "blobs" pointing at some NFS mount. From that
point on, blobs were stored at (retrieved from) that location. Keep in
mind, though, that filesystem operations are not automatically undone
if something goes wrong in a lengthy save operation (as opposed to
operations in a database).

Kind regards
Dominique

>
> thx,
> Hanno
> --
> View this message in context: http://www.nabble.com/jackrabbit-clustering-tf4261939.html#a12310826
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>