Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Tue, 12 Jul 2005 08:34:18 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
Sender: hossman@hal.rescomp.berkeley.edu
To: java-user@lucene.apache.org
Subject: Re: Index Partitioning ( was Re: Search deadlocking under load)
In-Reply-To: <1017F4C8-CB8C-4CA7-8953-0BBFDE0667BD@aconex.com>
Message-ID: <Pine.LNX.4.58.0507120831510.28329@hal.rescomp.berkeley.edu>
References: <20050708193944.61757.qmail@web31112.mail.mud.yahoo.com>
 <73809823-CE46-406E-A142-6C4C0EA1E0E4@aconex.com>
 <Pine.LNX.4.58.0507101605250.22002@hal.rescomp.berkeley.edu>
 <0E62ADC4-D7FC-4CF1-B691-A464567BAEC4@aconex.com>
 <Pine.LNX.4.58.0507101727420.31070@hal.rescomp.berkeley.edu>
 <1017F4C8-CB8C-4CA7-8953-0BBFDE0667BD@aconex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: Since this isn't in production yet, I'd rather be proven wrong now
: rather than later! :)

it sounds like what you're doing makes a lot of sense given your
situation, and the nature of your data.

the one thing you might not have concidered yet, which doesn't have to
make a big difference in your overall architecture, but might influence
the specifics of your design, is the idea that eventually you might want
to seperate Projects on onto different physical servers, letting you put
"important" projects on their own server, so they are alllways available
(even if they are the LRU).


-Hoss


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