Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates
 64.233.166.183 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=BXg3CR2WTLfuuER0TO70ZcdiaAztOuJcr6/zAGzBTqhuLaLomDMsCcArdyhp5farngNu2quR2eI8QeVgSR8sC2WgvheYx4KpXG8hedmBIieH8B4uRI9OfXbgBd/uesVVWwcGHnkcjLkHDK2z5Uwwd05a8w9ppPKJU1ZzfexdvMo=
Message-ID: <c68e39170609211313t336e916cn188b044de788682d@mail.gmail.com>
Date: Thu, 21 Sep 2006 16:13:37 -0400
From: "Yonik Seeley" <yonik@apache.org>
Sender: yseeley@gmail.com
To: java-dev@lucene.apache.org
Subject: Re: Re: Re: Clustering IndexWriter?
In-Reply-To: <8fcbd19a0609211250m44434bbap6b87fbac429dcda5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <8fcbd19a0609201740u921f99ejb1603a9efab09f20@mail.gmail.com>
	 <c68e39170609210748g11a0662dq265951c83001e876@mail.gmail.com>
	 <8fcbd19a0609210818p78d9cfdao29ca648620fae6e5@mail.gmail.com>
	 <Pine.LNX.4.58.0609211219180.5074@hal.rescomp.berkeley.edu>
	 <8fcbd19a0609211250m44434bbap6b87fbac429dcda5@mail.gmail.com>

While automatically clustering java objects sure sounds cool, I have
to wonder what the performance ends up being.  Every small change to
the clustered objects is broadcast to all the nodes, correct?

Have you done any performance comparisons to see if this is a
practical approach for Lucene?

-Yonik
http://incubator.apache.org/solr Solr, the open-source Lucene search server


On 9/21/06, Steve Harris <sharrissf@gmail.com> wrote:
> Fair question.
>
> All I did/need was take SegmentInfos and instead of subclassing Vector
> I made it contain a Vector. Went from subclassing to aggregation. As
> far as I could
> tell from reading the code it would make no difference to anyone and
> should have no performance impact (good or bad). It just allowed me to
> cluster the IndexWriter with a RAMDirectory.
>
> Maybe a little background would help. Our clustering product doesn't
> use java serialization and has no API. We just use a little config
> where one points us to what you want clustered and what java
> synchronization needs to be shared. One of the limitations that
> currently exists is that we don't support clustering subclasses of
> java collections.
>
> At this point I'm just experimenting to see if our product can cluster
> lucene in a useful/performant way. When my experimenting is complete,
> if everything is positive, I am going to write a blog on clustering
> lucene indexes but it would be awkward to do that if the people who
> run through the example have to change lucene code.
>
> Does this help?
>
> Cheers,
> Steve

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