jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seidel. Robert" <Robert.Sei...@aeb.de>
Subject concurrent write access not faster then sequential write access to a clustered repository
Date Mon, 23 Aug 2010 16:02:30 GMT

I've created a clustered repository and want to store data concurrent from different workstations
to improve the storage performance (3 nodes should be faster than 1 was my simple idea).
What happens at the moment is, that one node can access the repository and store data into
it and the other two nodes hang in AbstractJournal line 241 (this.rwLock.writeLock().acquire();).

Is there a way to use multiple nodes to improve the performance when storing data in a content
repository? Or do multiple nodes only improve search performance/stability?

Kindly regards,

Robert Seidel

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message