Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <8065033.post@talk.nabble.com>
Date: Wed, 27 Dec 2006 09:19:39 -0800 (PST)
From: Biggy <biggy97@web.de>
To: java-user@lucene.apache.org
Subject: RE: Clustering Lucene with 40 Servers
In-Reply-To: 
 <F7CE0FFA3A30084B9AD03275B9F4CFC894C3DB@LA-EXCLUST01.corp.valueclick.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <8064135.post@talk.nabble.com>
 <F7CE0FFA3A30084B9AD03275B9F4CFC894C3DB@LA-EXCLUST01.corp.valueclick.com>


Well try having say 30 servers try to write in the index at the same time a=
nd
10 others=20
to read. You'll get enough locks to make a grown man cry. :)


Scott Sellman wrote:
>=20
> Sorry if this seems na=C3=AFve (I am new to Lucene), but why not keep one=
 copy
> of the Lucene index on a NAS and have it shared by all servers? =20
>=20
> -----Original Message-----
> From: Biggy [mailto:biggy97@web.de]=20
> Sent: Wednesday, December 27, 2006 7:57 AM
> To: java-user@lucene.apache.org
> Subject: Clustering Lucene with 40 Servers
>=20
>=20
> I'm currently investigating the best ways of clustering Lucene.
> I've heard of both Solr, Terracotta but do not know how well they scale.
> Their examples talk of a 4 node cluster. This is way too small for my
> needs.
>=20
> I have 30x JVMs each handling 3 requests/sec and each having their own
> Lucene index. The index changes are propagated to the cluster members
> using
> JGroups messages. This solution has more than reached its limit as JGroup=
s
> has become unstable and a source of many JVMs crashes. Based on current
> traffic trends I anticipate needing to upgrade to 40x + JVMS very soon.
>=20
> Can anybody suggest a way to effectivily cluster / replicate document
> changes ?
>=20
> P.S.:=20
> JMS is not a possible solution as this was the prior JGroups solution. We
> had too many memory problems/queue full etc crashing the servers
> thereafter.
>=20
> --=20
> View this message in context:
> http://www.nabble.com/Clustering-Lucene-with-40-Servers-tf2886546.html#a8=
064135
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>=20
>=20
>=20

--=20
View this message in context: http://www.nabble.com/Clustering-Lucene-with-=
40-Servers-tf2886546.html#a8065033
Sent from the Lucene - Java Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org